About db separation(2)

This is a post about Db separation.

In this post, I’ll explain why companies use two different DB services (AWS S3, MongoDB, etc.) and why they use DB from different services.

Is it common to use different services when splitting a DB into two?

In fact, many companies and services use this combination. This choice can be appropriate because each database has different purposes and requirements.

So how do you separate the purposes and requirements?

Let’s look at AWS S3 and MongoDB to see.

• AWS S3 is a large file store and is mainly used to store static files (images, videos, etc.) or unstructured data like log files. S3 is highly scalable and durable, and you can have as much storage space as you want. Because of these benefits, log data can be stored in S3 and read when needed.
• MongoDB is a document-oriented NoSQL database, which is perfect for storing unstructured data like logs. MongoDB specializes in storing and retrieving documents in JSON format and can efficiently handle large amounts of log data.

Conclusion

Using AWS S3 to store log data and MongoDB to store unstructured log data is generally a good approach. It allows you to choose the appropriate storage and manage your data based on the purpose and nature of the data.