Service meshes are not only for big companies. It works for intermediate-sized companies as well. We have 10+ teams and 30+ services and we built our-own service mesh using Envoy proxy. By building a service mesh, we can start using service meshes with a small start and benefit from it. I will share knowledges, techniques and benefits to build and operate your own service mesh.
Service meshes are not only for big companies. It works for intermediate-sized companies as well. We, Cookpad, are a mid-sized company having 200+ developers, 10+ teams, 90M monthly users.
We are building our-own service mesh using Envoy proxy for our microservices. And, we are getting the benefit of service mesh. The biggest benefit is observability: we can easily know how our microserives are working by looking into fine-grained metrics including RPS, status codes, latency and status of cirbuit breaker... per upstream service. And also visualization with Netflix's Vizceral brings more observability to manage our services well. The second benefit is process model independency: we now have the outbound proxy for every app which controls retries, timeouts, circuit breaking and load balancing. No need to implement libraries per laungage.
I will share the knowledge and techniques through our case: how did we build, and our architecture and toolchains. We are using AWS ECS as a container orchestration, and our service mesh is built on it. Audiences using AWS especially learn how to build or introduce service mesh.
Prerequisite knowledge for this presentation:
This talk will be based on the blog post: https://blog.envoyproxy.io/service-mesh-and-cookpad-ba4d5d915dbd.
|Starts On||9/7/18, 12:30 PM|
|Session Duration||Regular Session (30min)|
Your session will be confirmed when you press the button below