API GatewaysĪn API Gateway is the bigger brother of the good old reverse proxy for HTTP calls. Of course, there's also a number of other approaches, ranging from simple static load balancing and fixed IPs to central orchestration servers - but for the purpose of this post, let's look at the currently most popular and in many ways most sophisticated options. The solutionsĪlright, time to meet the contenders for solving these problems: Service Meshes, API Gateways, and Message Queues. VersioningĪs systems mature it becomes paramount to update available endpoints and APIs while simultaneously ensuring that older versions remain available. Tracing & MonitoringĪ single transaction in a microservice architecture might travel through multiple services, making it hard to trace its journey. The more complex and distributed an application, the harder it becomes to find existing endpoints and to establish a communication channel with them. In fact, one of the most effective cost-saving measures for large architectures is to increase the precision of routing and scaling decisions. With potentially hundreds of endpoints capable of fulfilling a request, routing and scaling are anything but trivial. There might be dozens or even hundreds of instances of any given microservice - each of which might fail at any point in time for any number of reasons. To function properly, microservice-based architectures have to tackle a number of challenges specific to their distributed nature: Resiliency This post aims to shed some light onto the various ways to organize communication amongst microservices and when a Service Mesh, an API Gateway or a Message Queue might be the best solution for your needs.īut before we talk about the solution, let's talk about the problem: So - what's the problem? The trouble is: once we've shattered our monolith, how do we put it back together into a larger system that still makes sense? Despite what Istio, Kong or Kafka enthusiasts will tell you, there's more than one answer to this question and different solutions are differently suited for different needs. In fact, few topics have received as much coverage in recent years as the unsurprising fact that breaking down a big thing into many small ones can make it easier to handle. Let's skip the pitch for microservices - you already know what they are and why they make sense. Service Mesh VS API Gateway VS Message Queue - when to use what?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |