I wrote down the following lines in a note because it is so important to build a plan for any engineering project. Oh, you used Go embed to stuff the package.īoth: We went down the street to stuff our stomachs first. I just wrote a 36-line unit test to simulate what I just talked about and it seems to work! The compressed PostgreSQL package for Linux is about 13MB (Darwin 27MB), however, the MySQL package is 200+MB. Hey, I found another reason to use PostgreSQL instead of MySQL. I prefer the former because not all users will use Docker. By the way, I want to provide the same one-click installation user experience today without requiring users to install and connect to PostgreSQL themselves.ĭanny: We can either package PostgreSQL into our binary or build it into our Docker image. Tianzhou: It will be difficult to migrate existing customers later.ĭanny: Yes, let's do this! How about PostgreSQL? I know we both like it. This makes it difficult to upgrade Bytebase version with schema changes later. For example, altering column constraints isn't supported, and many other things. Tianzhou: Right, and some features in the plan require time-series which isn't supported by SQLite.ĭanny: SQLite schema update has limitations too. Some users want to run Bytebase container on Heroku, Render, and Google Cloud Serverless with persistent storage but they cannot do it today with SQLite. I'm not seeing it in the architecture picture of Bytebase as a Cloud product. ![]() ![]() ![]() I'm with you, SQLite is charming but it's a database for localhost only. I started with it because it is easy to use for local development.ĭanny: We're launching Bytebase public in a couple of weeks. Tianzhou: Hey Danny, I don't think SQLite is good for our long-term game.
0 Comments
Leave a Reply. |