2017 Microservices Practitioner Virtual Summit - Opening Keynote: Trends in Microservices - Richard Li
0 likes2,864 views
The document outlines the schedule and key trends discussed at a microservices summit, featuring speakers from companies like Squarespace and Lyft. Key trends include the evolving role of operations, the necessity of polyglot programming, the rise of service meshes, and the increasing use of open-source infrastructure. Attendee roles are predominantly developers and engineers, with a strong interest in adopting modern microservices architectures.
2017 Microservices Practitioner Virtual Summit - Opening Keynote: Trends in Microservices - Richard Li
- 3. What best describes your role? Other 15% DevOps Engineer 12% Platform Engineer 15% Engineering Management 25% Developer 33%
- 5. Monday, July 24 1 PM - 1:30 PM EDT Opening Keynote: Trends in Microservices Richard Li, Datawire 1:30 PM - 2:30 PM EDT Microservices at Squarespace Kevin Lynch & Doug Jones, Squarespace Tuesday, July 25 10 AM - 11 AM EDT How to Avoid Creating a GitHub Junkyard Lauri Apple, Zalando 1 PM - 2 PM EDT Ancestry’s Journey towards Microservices, Containerization, and Kubernetes Paul MacKay, Ancestry Wednesday, July 26 1 PM - 2 PM EDT Move fast, make things: how developers can successfully adopt microservices Rafael Schloming, Datawire Thursday, July 27 1 PM - 2 PM EDT The Mechanics of Deploying Envoy at Lyft Matt Klein, Lyft
- 7. 7 Microservices Single Release Cycle of Monolithic Apps Multiple, Independent Release Cycles
- 11. 11 • dev environment • app resilience • CD pipeline • app monitoring • canary deployment • … Platform Engineers: common tools & infrastructure for the rest of the dev team.
- 14. 14 It’sveryhardtobuildaneffectivemicroservices architecturewithasinglelanguagestack. Each service might be written in a single language, but the library versions used are different • If you try to make them the same, you end up with a distributed monolith Different languages are good at different things, e.g., Python for data analysis is a common use case
- 17. 17 ServiceMesh Service Service Service Service Service Service Resilience Observability Security
- 18. 18 Aservicemeshletsservicescommunicatewitheachother. Hystrix, Ribbon, Eureka (Library approach) AirBnb SmartStack (Proxy approach) Envoy / Istio (Proxy)
- 20. I'm running a service mesh in production 3% I'm actively evaluating service meshes 8% I've read about them 32% Not at all 57%
- 22. 8% 8% 7% 19% 58% We are not using Kubernetes We have a dev/test cluster for evaluation We have a dev/test cluster under active use We are running a few production services on Kubernetes We’re mostly running our production on Kubernetes
- 25. 25 “We’re going agile” “We’re adopting J2EE” “We’re adopting the cloud”
- 26. 26 “We’re going agile” “We’re adopting J2EE” “We’re adopting the cloud” “This is taking forever, I’m just going to start with an empty repo.”
- 27. 27 “This is taking forever, I’m just going to start with an empty repo.” Wednesday, 1pm EDT