The main part of any application is its database selection. In this section, we will look at how to design our database for microservices, whether to keep it separate, to keep it shared, and which database to go to—SQL or NoSQL? We will look at how to categorize data stores based on data types and business capabilities. There are lots of options available. Microservices support polyglot persistence. The approach of selecting a particular data store based on business capabilities and needs is termed polyglot persistence. The following points discuss which database to refer to based on use cases:
- We can leverage Apache Cassandra to support tabular data, such as inventory data. It has options such as distributed consistency and lightweight transactions to support ACID transactions.
- We can leverage Redis to support cache data where the data model is simply a key-value pair. Read operations in Redis are super fast.
- We can leverage MongoDB to support product...