we are going to design the architecture step by step. Iterate the arch design one by one as per requirements. If we apply these Database Sharding pattern into our e-commerce microservices architecture, you can find the below design of that.

So this will illustrates scaling databases different servers with using database sharding pattern.

Main features are;

Peer-to-Peer Distributed Wide Column Database

Master-Master (Master-less) architecture

It is highly scalable and designed to manage very large amounts of structured data.

It provides high availability with no single point of failure.

Lets choose the databases. Now, of course Cassandra is the best option for our database as per high scalability and high availability.

Elastic scalability — It is scalable, fault-tolerant, and consistent.

Easy data distribution — Cassandra provides the flexibility to distribute data

And of course according to CAP Theorem, we sacrificed to strict consistency in here, and its good to follow eventually consistent in our e-commerce domain with microservices architecture.

As you can see that we have understand database architectures on microservices. What’s Next ? we will see how to manage querying different microservices.

So we should evolve our architecture with applying other Microservices Data Patterns in order to accommodate business adaptations faster time-to-market and handle larger requests.