/1 How do you decide which type of database to use?
There are hundreds or even thousands of databases available today, such as Oracle, MySQL, MariaDB, SQLite, PostgreSQL, Redis, ClickHouse, MongoDB, S3, Ceph, etc. How do you select the architecture for your system?
There are hundreds or even thousands of databases available today, such as Oracle, MySQL, MariaDB, SQLite, PostgreSQL, Redis, ClickHouse, MongoDB, S3, Ceph, etc. How do you select the architecture for your system?
/2 My short summary is as follows:
🔹Relational database. Almost anything could be solved by them.
🔹In-memory store. Their speed and limited data size make them ideal for fast operations.
🔹Time-series database. Store and manage time-stamped data.
🔹Relational database. Almost anything could be solved by them.
🔹In-memory store. Their speed and limited data size make them ideal for fast operations.
🔹Time-series database. Store and manage time-stamped data.
/3 🔹Graph database. It is suitable for complex relationships between unstructured objects.
🔹Document store. They are good for large immutable data.
🔹Wide column store. They are usually used for big data, analytics, reporting, etc., which needs denormalized data.
🔹Document store. They are good for large immutable data.
🔹Wide column store. They are usually used for big data, analytics, reporting, etc., which needs denormalized data.
/4 👉 Over to you: Obviously, I did not cover every type of database. Is there anything else you often use, and why do you choose it?
/5 Subscribe to my weekly system design newsletter (10-min read): lnkd.in/gqFQ49AV
/6 I hope you've found this thread helpful.
Follow me @alexxubyte for more.
Like/Retweet the first tweet below if you can:
Follow me @alexxubyte for more.
Like/Retweet the first tweet below if you can:
https://twitter.com/alexxubyte/status/1600528222390669315
Edit: Change "Document store" to "Object store"
• • •
Missing some Tweet in this thread? You can try to
force a refresh
