Cloud Foundry realizes a service mesh
Crossroads
The main benefit of the Cloud Foundry service mesh is the weighted routing option. Routes can now be assigned to more than one application, a feature many members of the Cloud Foundry community have had on their wish list for several years. The growing popularity of the service mesh idea created a critical mass that led to the idea finally being implemented. (See also the "Microservices and the Service Mesh" box.) The function can be used to define a weighting that distributes the load among the applications involved. The weighting factor of each application statistically determines how many incoming requests it receives on average.
Microservices and the Service Mesh
Many developers are now involved with microservice architectures. The new paradigm is causing a departure from monolithic applications and movement toward distributed application systems.
One of the advantages of microservice architectures is that developers of individual applications can now freely select both the programming language and, for example, the database on a case-by-case basis and in line with the purpose of the application. This capability creates local autonomy, leads to better design decisions, and ultimately promotes software quality. On the flip side, whereas previously a single application depended on a central database, you now might have to support a dozen applications and several databases, message queues, and analytics servers. This significantly greater system complexity drives corresponding increases in operating costs.
Not coincidentally, the spread of the microservice architecture approach has coincided with the advent of cloud computing: These trends are mutually dependent. Furthermore, the symbiosis of the two technologies also favors the emergence of service meshes such as Istio
Buy this article as PDF
(incl. VAT)