Why Developers Should Care about Service Mesh
Node.js Denver/Boulder/Ft. Collins
Why developers should care about service mesh
A disruptive technology pattern like a service mesh is exciting, but can also be confusing as it straddles various concerns and responsibilities ranging from SecOps to application developers.
This talk will dissect service mesh capabilities using Istio as an example and focus on the pieces that developers should care about and how they can offload some of the logic traditionally baked into the applications – distributed tracing and telemetry, request retries and timeouts, mutual TLS and end user validation, and service decomposition – into a common infrastructure layer. The session will also explore various questions developers should be asking their platform teams like “do I need to update my applications to use service mesh?” and “will the sidecars degrade my application performance?” as they adopt a service mesh in their environment.
Neeraj Poddar is the Engineering Lead at Aspen Mesh. He has worked on various aspects of operating systems, networking and distributed systems over the span of his career. He is passionate about developing efficient and performant distributed applications. At Aspen Mesh, he is currently building an enterprise service mesh and their hosted SaaS platform. In his free time you can find him playing racquetball and gaining back the calories spent playing by trying out new restaurants.
6:30pm: Pizza, beer, networking
Hope you all can make it out to this great talk. If you have any questions, don’t hesitate to reach out.