![]() ![]() ![]() Regardless, you'd certainly only keep high-level records, meta data in Database, and the actual files, most-likely in S3, so that you can keep all options open in terms of what you'll do with them. Other database services exist, I'd recommend you also explore Dynamo DB. I personally would recommend MySQL (latest version available), as the official tooling for it (MySQL Workbench) is great, stable, and moreover free. As far as which database to chose, you'll have the choice between Postgresql, MySQL, Maria DB, SQL Server. Doing this on your own would either be risky, inefficient, or you might just give up. Such managed services easily allow you to apply new security patches and upgrades, set up backups, replication. Aurora would be my preferred choice given the benefits it offers, storage optimizations it comes with. If you are on AWS, thet have different offerings for database services. Don't spin up your own MySQL installation on your own Linux box. Hi Erin! First of all, you'd probably want to go with a managed service. PostgreSQL is also pretty universally supported in terms of language libraries and frameworks, without having to make compromises on how we want to store and layout our data. PostgreSQL is kind of a happy middle ground here, with the ability to start PostgreSQL servers via docker or docker-compose making the actual day-to-day management pretty easy, while still giving you experience of the kinds of considerations I have listed above.Īt Vital Beats we make use of PostgreSQL, largely because it offers us a happy balance between good management and backup of data, and good standard command line tools, which is essential for us where we are deploying our solutions within Kubernetes / docker, and so more graphical tools are not always appropriate for us. MySQL has a few "quirks" to how it manages things like multiple databases, which may lead you to making less good decisions if you tried to take your experience over to different DBMS, especially in bigger enterprise roles. SQLite's simplicity actually avoids most of these experiences, which is not helpful to you if that is what you hope to learn. If your aim is actually to have a bit of "operational" experience, in terms of things like what command line tools might be available as standard for the DBMS, understanding how the DBMS handles multiple databases, when to use multiple schemas vs multiple databases, some basic privilege management etc. ![]() As others have said, SQLite would offer you the ability to very easily get started, and would give you a reasonably standard (if a little basic) SQL dialect to work with. If your aim is to have experience with SQL and any related libraries and frameworks for your language of choice (python, I think?), then it kind of doesn't matter too much which you pick so much. A question you might want to think about is "What kind of experience do I want to gain, by using a DBMS?". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |