Microservices Design Pattern
1. Service Discovery.
2. API Gateway.
3. Circuit Breaker.
4. SAGA.
5. CQRS.
6. DB PER Service.
7. Strangler.
8. Bulk Ahead.
9. Event Sourcing. 1
10. BFF Back end for Front end.
Search for a command to run...
1. Service Discovery.
2. API Gateway.
3. Circuit Breaker.
4. SAGA.
5. CQRS.
6. DB PER Service.
7. Strangler.
8. Bulk Ahead.
9. Event Sourcing. 1
10. BFF Back end for Front end.
No comments yet. Be the first to comment.
One Questions, Why Redis Handle more TCP Connection: What makes Redis Special: Redis is an open source in memory ds store that can be use on Database, cache, Message Broker and Stream engine Some ds
Statistics probality (bayes , conditional) linear regression principle component (PCA) see last Dimenstion reducton ltechqies LDA TSNV ML: Supervised Learnming: Regression logistics Navibase KNNen SVM (solid and hard) Decision trees Loss Funtions Ens...
Small Companies may good to use ORM until we get perofrmance issue Let Say why i am using sucks? Example we can take, U want to get the all user orders. what u do? Simple i will use User.findAll() and user.getOrder() thats it completed okay good is i...
Distributed Tracing helps for the trace of the application logs Let say user A hit an ap in distrubted to racing the log of this user for Each user one trace Id is there which is common for all the Service and When one service calls another service t...