Search the Community

In the dynamic world of microservices architecture, efficient service communication is the linchpin that keeps the system running smoothly. To maintain the reliability, security, and performance of your microservices, you need a well-structured service mesh. This dedicated infrastructure layer is designed to cater to service-to-service communication, offering essential features like load balancing, security, monitoring, and resilience. In this comprehensive guide, we’ll delve into the world of service meshes and explore best practices for their effective management within a microservices environment... View the full article

We are excited to announce the public beta of HashiCorp Consul service mesh support for Amazon’s serverless functions service: AWS Lambda. This release will ensure service mesh users can now take advantage of consistent workflows and encrypted communications from all mesh services to all upstream workloads including Lambda functions. As organizations focus on getting to market faster, serverless adoption helps developers accelerate application development. Datadog’s State of Serverless Survey shows that AWS Lambda is leading the serverless landscape. However, effectively integrating AWS Lambda into a service mesh requires first-class support. Previously, other Lambda integrations bypassed the service mesh. This beta release addresses these limitations by extending Consul service mesh capabilities and secure communications to AWS Lambda in addition to existing support for Kubernetes, virtual machines, HashiCorp Nomad, and Amazon ECS... View the full article

View the full article

Kubernetes networking is, for the most part, intra-cluster. It enables communication between pods within a single cluster: The most fundamental service Kubernetes networking provides is a flat L3 domain: Every pod can reach every other pod via IP, without NAT (Network Address Translation). The flat L3 domain is the building block upon which more sophisticated communication services, like Service Mesh ... https://blogs.cisco.com/developer/multicloudhybrid01

CNCF conducted a microsurvey of the cloud native community at the end of 2021 to discover how organizations are adopting service meshes. Cloud native is driving digital transformation, with organizations keen to capitalize on the agility and flexibility it provides to their business and operations. But as more applications and services are deployed using a […] The post Service Meshes Are on the Rise – But Greater Understanding and Experience Are Required appeared first on DevOps.com. View the full article

Anthos Service Mesh is a managed service mesh for Google Kubernetes Engine (GKE) clusters. Anthos Service Mesh allows GKE clusters to use a single logical service mesh, so that pods can communicate across clusters securely and services can share a single Virtual Private Cloud (VPC). Using Anthos Service Mesh requires GKE clusters and firewall rules. As well, access to the GKE GKE control plane needs to be granted, if private clusters are used. Infrastructure-as-code (IaC) makes bootstrapping Anthos Service Mesh significantly easier. In this blog post, we explain the new features of Anthos Service Mesh, and how to implement it across two private GKE clusters using Terraform. We also provide automation scripts, giving a guided tour for setting up a cloud environment. For those who want to get started immediately, there is a Git repo with complete source code and README instructions. There are also bonus sections at the end, for mesh traffic security scanning and external databases respectively. GKE best practices: Exposing GKE applications through Ingress and Services We'll walk through the different factors you should consider when exposing applications on GKE, explain how they impact application expos... Read Article