In the last few years, microservices or microservice architecture has become a popular reference in IT due to its benefits and the flexibility this architectural style brings.
Before we get into working with microservices and Talend, we should review the basics of microservices or a microservice architecture.
In a previous blog from Ravi Chebolu, he provided a great insight on Microservices:
“Microservices is often quoted as an architectural style for software development as a variant derived from the foundations of Service Oriented Architecture(SOA)”
To make it simple, we often compare microservices versus a monolith.
- A monolith is an application that holds a group of operations together, like a frontend interface and the backend services which receives the data.
- A microservices architecture will take the same operations but instead of creating one big application, it will decompose it into a collection of loosely coupled services.
For more information on Microservices and Talend, I will recommend looking at these articles:
- “Going Serverless with Talend through CI, CD and Containers”
- “How to Schedule a Talend Job with Kubernetes”
- “Microservices, a Lean Thinking Approach”
A microservices architecture can bring a ton of benefits including better maintenance and upgrade, better fault isolation, easier continuous integration, better integration with containers, scalability and so much more. But if not well-managed and by default, it can also bring some complexity in the day to day life and management like request tracing and monitoring.
So what is a Service Mesh?
A service mesh is a network of microservices that makes service-to-service scenarios secure, performant and reliable. Istio is a service mesh backed up by Google and they added direct Istio access to its Kubernetes Engine.
Istio’s Core features include:
- Traffic Management
- Platform support
- Integration and customization
In terms of implementation, a service mesh can help by adding more features to assist in the deployment of microservices like:
- A/B testing
- Blue / Green deployment
- Canary releases
- Rate limit
- Access control
- End-to-end authentication.
Usually, service mesh is an infrastructure layer relying on proxies to be implement and the corresponding architecture.
To understand more about service mesh with Talend, I invite you to register for the webinar we just put together that dives into the technical details. In it, I’ll show you how to use service mesh with Talend and Istio. Until next time!