Kom_pai @Kom_Ratco - Twitter Profile

Kom_pai @Kom_Ratco

over 2 years ago

ยาก - นภ พรชํานิ ครับ #จดหมายเด็กแมว

0

1

0

201

Kom_Ratco retweeted

System Design Codex

@ProgressiveCod2

almost 3 years ago

Building microservices is NOT easy. Even in the best of times, you might end up in a mess. But if you still have to build microservices for some reason, it’s better to know a few patterns that can make your life easy. Here are 4 must-know patterns for building microservices: (don't forget to bookmark) ✅ Database per service - In this pattern, each microservice manages its own data. - This means that no other service can access that data directly. - Communication or exchange of data can only happen through the owner service. - The success of this pattern depends on how well you’ve defined the bounded context of your application. ✅ Shared Database - Avoid this pattern as much as possible - But sometimes, it’s the only viable option to incrementally move to a microservice architecture. - This approach is lenient in the sense that multiple services use a shared database. - However, it creates a bigger impact surface and chances of run-time issues. ✅ API Composition - This pattern tries to solve the problem of implementing complex queries in a microservices architecture. - An API Composer invokes other services in the required order. - After fetching the results, it performs an in-memory join of the data before returning it to the caller. - This is an inefficient approach due to in-memory joins on potentially large datasets. ✅ CQRS + Event Sourcing - Next, we have CQRS - AKA Cory's (@CorysDomain) favorite pattern 😉 - It can help get around the issues with the API Composition Pattern. - An application listens to domain events from other services and updates a separate query database. This makes it easy to serve complex aggregation queries. - CQRS can also be combined with Event Sourcing where you store the state of the entity (aggregate) as a sequence of events. - Of course, this pattern can sometimes be unfamiliar to the developers. At the end of the day, no pattern is perfect. As developers, we must learn about the trade-offs with each pattern and choose what works for your system. Do mention your favorite patterns in the comments... === That’s all for now If you enjoyed this post, don’t forget to: - Destroy the LIKE button - REPOST so that everyone can choose the right pattern - BOOKMARK for future reference when you have to make a decision - Follow me for more posts like this.