Entradas

Mostrando las entradas etiquetadas como Microservices

Microservices and Service Deployment

A Microservice application is made up of tens or even  hundreds of services,  written in different languages and frameworks .  Each service  is a mini application that  must be provided with the appropriate memory, CPU and other resources . In spite of the complexity,  deploying services must be reliable, fast and cost-effective.  The  process should be automated as much as possible from Continuous Integration (CI) to Continuous Deployment (CD).  This could save a lot of time and money. Packaging Services Every service might require a different set of dependencies for its execution.  Satisfying dependencies of all the services can be a tedious and challenging job. Hence,  you need both the service and its dependencies packed as single   Docker or VMI images , before the service deployment. You can package all the services as separate Docker or VMI images and create isolation. These images are then...

Microservices Architecture - Patterns

Imagen
API Gateway Microservices provide fine-grained APIs based on client needs. Each client needs to interact with multiple services to collect relevant information. For example, a  payment  client needs to fetch data from several services such as product, customer, and billing. API Gateway takes care of the  external traffic of coordinating with different services . The API Gateway encapsulates the internal system architecture and provides an API that is tailored to each client. The API Gateway is liable for Protocol translation, Composition, and Request Routing. Benefits: Insulates the clients from internal structure of the application Provides specific API to each client, reducing the number of round trips between the client and application. Simplifies the client by transferring logic for calling various services from the client to API gateway. Communication In a monolithic application, components invoke each another through functio...