Cheat sheet on how to choose database

The effectiveness and scalability of your design depends greatly on the choice of database. It is possible to use multiple databases within a single system for different purposes.
 
DB cheet sheet (you can click on image to expand it)

Caching solutions such as Redis and Memcached are key-value storage systems that can be used to improve the performance of a system by temporarily storing frequently accessed data in memory. 

For storing large files such as images and videos, it is often useful to use a file storage service such as S3 or Google Cloud Storage. These are known as blob storage systems and can be used in conjunction with a content delivery network (CDN) to improve the performance and reliability of file access.

To support full text search you could to use Elastic search or Solar.

To support monitoring system InfluxDB or Prometheus may be good options to consider.

For analytics on extremely large datasets and where transactions are not a requirement, Hadoop may be a good option to consider.

For structured data, a relational database such as PostgreSQL or MySQL may be suitable. These types of databases support ACID (Atomicity, Consistency, Isolation, Durability) properties.

For non-structured data, such as store catalog data, a NoSQL database like MongoDB or CouchDB may be suitable. MongoDB is a document-oriented database that allows for eventual consistency.

For data that is constantly increasing in size, such as records of purchases from a company like Amazon and where the number of queries is finite but relatively simple, Cassandra or HBase may be good options to consider.

For representing relationships, such as friendships, Neo4J may be a good choice.

[Таблица БД (вы можете щелкнуть изображение, чтобы развернуть его)]
Таблица БД (вы можете нажать на изображение, чтобы развернуть его)

Comments

Post a Comment

Popular posts from this blog

How to conduct code reviews?

Image
     Based on my experience, having a solid code review plan can make a huge difference in the quality of the software we develop. Over time, I've learned that focusing on different aspects at different stages can really streamline the process and catch potential issues early. Let me break down the approach I use, which has proven to be pretty effective.     API Semantics: The Foundation      I always start with the API Semantics, the foundation of our code review plan. Here, it's all about the big picture—making sure the API is minimal yet sufficient, without any unnecessary duplication. We want it to be intuitive and easy to use, sticking to the principle of least surprise. It’s also crucial to check the cleanliness of the API and ensure any new dependencies come with acceptable licenses. By focusing on these aspects first, we can build a solid base for the rest of the code.   Implementation Semantics: Ensuring Correctness and Efficiency ...
Read more

Why I Decided to Open Source?

Image
       It all started with a simple realization: some of the best things in my coding journey came from the open-source community. As a budding developer, I often found myself scouring GitHub, marveling at the vast array of projects and the generosity of people who shared their work with the world. It was through this open exchange of ideas and code that I learned, grew, and became the developer I am today. A Sense of Belonging      I remember the first time I contributed to an open-source project. I was nervous, unsure if my code would be good enough, but I went for it anyway. To my surprise, my contribution was welcomed warmly. The feeling of being part of something bigger than myself was exhilarating. This sense of belonging and collaboration was a key reason I decided to open source my projects. I wanted to recreate that welcoming environment for others, providing a platform where they could contribute, learn, and feel valued. The Joy of Learning a...
Read more

POP3 protocol summary

Image
POP - post office protocol. Versions: POP1 - 1984 POP2 - 1985 POP3 - 1988 Updated version of POP3 with additional authentication mechanisms and extensions - 1996 POP3 communication schema The approach "download and delete": The message storage on the server is a temporary storage for messages. All messages must be transferred to the mail client. After uploading to the client, the messages are deleted from the server. Advantages: Simple protocol. Letters are available when there is no network connection. Disadvantages: Only 1 client. Single mail storage (no folders, filters, flags, etc.). POP3 is an application layer protocol (port 110), it uses TCP transport protocol. Session states: Authorization - the client introduces himself and confirms that he is who he says he is. Transaction - the client downloads the mail and marks the downloaded message for deletion. Update - the server deletes the marked message and closes the connection. POP3 works in text mode, interacting in a ...
Read more