Microservice Gateway and access patterns
Blog post from Tyk
Jennifer Craig's article explores three common approaches to microservice architecture that organizations can employ to reduce team coordination and enhance delivery speed. The first approach, direct request/response microservices, uses HTTP and REST constraints but can lead to a fragile system with tight consumer coupling. The second method, message-oriented microservices, favors asynchronous communication through message queues, offering a more evolvable architecture by reducing direct dependencies between consumers and services. The third approach, experience APIs with microservices, involves defining an external API contract that orchestrates microservices, allowing for flexibility and evolution without affecting consumers. This method, though complex, is recommended for large-scale teams due to its adaptability. The article emphasizes the importance of selecting the right strategy for microservices, suggesting starting with simpler models and incorporating API gateways for flexibility.