A malha de servi?os ¨¦ uma abordagem para operar um ecossistema de microsservi?os seguro, r¨¢pido e confi¨¢vel. Ela tem sido um importante passo para facilitar a ado??o de microsservi?os em escala. Oferece descoberta, seguran?a, rastreamento, monitoramento e processamento de falhas. Fornece recursos interfuncionais sem a necessidade de um ativo compartilhado, como uma API gateway ou bibliotecas baking em cada servi?o. Uma implementa??o t¨ªpica envolve processos de proxy reversos leves, tamb¨¦m conhecidos como sidecars, implementados junto com cada processo de servi?o em um cont¨ºiner separado. Os sidecars interceptam o tr¨¢fego de entrada e sa¨ªda de cada servi?o e fornecem os recursos interfuncionais mencionados acima. Essa abordagem aliviou os times de servi?os distribu¨ªdos de construir e atualizar os recursos que a malha oferece como c¨®digo em seus servi?os. Isso levou a uma ado??o ainda mais f¨¢cil da programa??o poliglota em um ecossistema de microsservi?os. Nossos times t¨ºm usado essa abordagem com sucesso em projetos de c¨®digo aberto, como Istio, e continuaremos a monitorar outras implementa??es abertas de malha de servi?os, como , de perto.
As large organizations transition to more autonomous teams owning and operating their own microservices, how can they ensure the necessary consistency and compatibility between those services without relying on a centralized hosting infrastructure? To work together efficiently, even autonomous microservices need to align with some organizational standards. A service mesh offers consistent discovery, security, tracing, monitoring and failure handling without the need for a shared asset such as an API gateway or ESB. A typical implementation involves lightweight reverse-proxy processes deployed alongside each service process, perhaps in a separate container. These proxies communicate with service registries, identity providers, log aggregators and other services. Service interoperability and observability are gained through a shared implementation of this proxy but not a shared runtime instance. We've advocated for a decentralized approach to microservices management for some time and are happy to see this consistent pattern emerge. Open source projects such as and Istio will continue to mature and make service meshes even easier to implement.
As large organizations transition to more autonomous teams owning and operating their own microservices, how can they ensure the necessary consistency and compatibility between those services without relying on a centralized hosting infrastructure? To work together efficiently, even autonomous microservices need to align with some organizational standards. A service mesh offers consistent discovery, security, tracing, monitoring and failure handling without the need for a shared asset such as an API gateway or ESB. A typical implementation involves lightweight reverse-proxy processes deployed alongside each service process, perhaps in a separate container. These proxies communicate with service registries, identity providers, log aggregators, and so on. Service interoperability and observability are gained through a shared implementation of this proxy but not a shared runtime instance. We've advocated for a decentralized approach to microservice management for some time and are happy to see this consistent pattern emerge. Open source projects such as and will continue to mature and make service meshes even easier to implement.
As large organizations transition to more autonomous teams owning and operating their own microservices, how can they ensure the necessary consistency and compatibility between those services without relying on a centralized hosting infrastructure? To work together efficiently, even autonomous microservices need to align with some organizational standards. A service mesh offers consistent discovery, security, tracing, monitoring and failure handling without the need for a shared asset such as an API gateway or ESB. A typical implementation involves lightweight reverse-proxy processes deployed alongside each service process, perhaps in a separate container. These proxies communicate with service registries, identity providers, log aggregators, and so on. Service interoperability and observability are gained through a shared implementation of this proxy but not a shared runtime instance. We've advocated for a decentralized approach to microservice management for some time and are happy to see this consistent pattern emerge. Open source projects such as and will continue to mature and make service meshes even easier to implement.
