Download to read offline
Uploaded byCloud Native Day Tel Aviv
Not my problem! Delegating responsibilities to the infrastructure - Yshay Yaacobi, Soluto - Cloud Native Day Tel Aviv 2018
The document discusses the transition from monolithic applications to microservices, emphasizing the need for improved infrastructure management, automation, and service-oriented architecture. Key topics include logging, error handling, security, and monitoring within a microservices environment, along with the utilization of sidecars for additional functionality. The document also highlights tools and resources beneficial for developers to enhance productivity and maintainability in service-oriented development.
More Related Content
Similar to Not my problem! Delegating responsibilities to the infrastructure - Yshay Yaacobi, Soluto - Cloud Native Day Tel Aviv 2018
More from Cloud Native Day Tel Aviv
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Not my problem! Delegating responsibilities to the infrastructure - Yshay Yaacobi, Soluto - Cloud Native Day Tel Aviv 2018
- 1.
- 2. @yshayy As a developer,I want to focus on building features that deliver business value
- 3.
- 4.
- 5.
- 6. @yshayy FewMonolithsFewMonoliths Application code Infra code Applicationcode Infra code Application code Infra code
- 7. @yshayy Monoliths ----→ Lotsof Microservices
- 8. @yshayy Monoliths ----→ Lotsof Microservices
- 9. @yshayy ServicestructureServicestructure ----→ Infra-code and businesslogic code live together with every Microservice
- 10. @yshayy ServicestructureServicestructure ----→ How can wewrite only our business code and let our hosting environment take care of the rest?
- 11. @yshayy Yshay Yaacobi @yshayy AboutmeAboutme Tech lead@ Soluto Open source Cloud architecture Functional Programming Docker Code Quality
- 12. @yshayy AboutSolutoAboutSoluto Based in TelAviv, acquired by Asurion at 2013 Next generation of tech support 150M users worldwide We love open-source
- 14.
- 15. @yshayy ShiftingtomicroservicesShiftingtomicroservices ~5 services ->100+ services Cultural change, new aspects of ownership CI/CD - Better tooling automation Self-service
- 16.
- 17.
- 18. @yshayy Spec‑NotificationsserviceSpec‑Notificationsservice We want tosend notifications to users Notifications will be based in templates Notifications will be personalized
- 19. @yshayy Flow‑NotificationserviceFlow‑Notificationservice 1. Get useridentifier and notification type 2. Fetch user details from users micro-service 3. Format message using a template 4. Send a message
- 20.
- 21.
- 22.
- 23. @yshayy LoggingLogging We need toadd a logger We send logs to a 3rd party provider Let's get a library + a provider
- 24. @yshayy ☑ Logging ☐ Errorpolicies ☐ Authentication ☐ Monitoring
- 25. @yshayy ErrorpoliciesErrorpolicies The network canfail We want to retry failed requests Let's add Polly
- 26. @yshayy ☑ Logging ☑ Errorpolicies ☐ Authentication ☐ Monitoring
- 27. @yshayy AuthenticationAuthentication We'll use JWTtoken OIDC/OAuth2
- 28. @yshayy ☑ Logging ☑ Errorpolicies ☑ Authentication ☐ Monitoring
- 29. @yshayy MonitoringMonitoring Performance metrics, throughput,latency Statsd client
- 30. @yshayy ☑ Logging ☑ Errorpolicies ☑ Authentication ☑ Monitoring
- 31.
- 32. @yshayy Whatjusthappenedhere?Whatjusthappenedhere? We wanted asmall micro service and got a bunch of code and dependencies
- 33. @yshayy Whatjusthappendhere?Whatjusthappendhere? 4 X Linesof codes !!! 3 X Direct dependencies !!!
- 34. @yshayy Soluto‑microservicesv1Soluto‑microservicesv1 Shared template -dependencies and code blocks Used by teams as a boilerplate Shared “common” packages/frameworks Lots of DI magic Worked well until...
- 35. @yshayy ProblemsProblems Upgrades are Hard Dependenciescan break Dependencies can conflict Dependencies requires re-build+re-deploy Extremely difficult to introduce global change
- 36.
- 37.
- 38.
- 39.
- 40. @yshayy As a developer,I want to focus on building features that deliver business value
- 41. @yshayy Which of theseconcerns can be solved at environment level ?
- 42.
- 43. @yshayy KubernetesKubernetes Orchestrate our services Solvesmany cross cutting concerns
- 44. @yshayy AASidecarSidecarContainerContainer Additonal Container ina pod Provide functionality to support main app Co-scheduled together in replicas
- 45.
- 46.
- 47.
- 48. @yshayy LoggingLogging Treat Logs asevent streams Use log forwarder Scrape the logs from Docker
- 49. @yshayy FluentDFluentD Run on everynode (Daemonset) Declarative configuration to define log pipelines
- 50. @yshayy Logging‑extrabenefitsLogging‑extrabenefits Different policies Info/Debug ->low retention Error/Fatal -> high retention Plugins -> anonymization
- 51. @yshayy ☑ Logging ☑ Errorpolicies ☑ Authentication ☑ Monitoring
- 52.
- 53. @yshayy ErrorpoliciesErrorpolicies Service-mesh, THE buzzwordfor 2018 Istio Injects proxy sidecar
- 54.
- 55.
- 56.
- 57. @yshayy ☑ Logging ☑ Errorrecovery ☑ Authentication ☑ Monitoring
- 58.
- 59. @yshayy AuthenticationAuthentication Let's use asidecar Soluto/Airbag
- 60.
- 61. @yshayy Authentication‑AirbagAuthentication‑Airbag Configuration yaml example Opensource Probably be superseded by Istio's origin authentication
- 62. @yshayy ☑ Logging ☑ Resiliency ☑Authentication ☑ Monitoring
- 63.
- 64.
- 65. @yshayy ☑ Logging ☑ Resiliency ☑Authentication ☑ Monitoring
- 66.
- 67. @yshayy AnewrequirementAnewrequirement It's black friday! Wewant to send lots of messages
- 68. @yshayy AnewrequirementAnewrequirement It's a batchprocess Let's use a queue
- 69.
- 70.
- 71.
- 72.
- 73.
- 74. @yshayy DequeueDaemonSidecarDequeueDaemonSidecar Soluto/DQD Read items fromqueue, activate service Back-pressure support Expose consumption metrics
- 75.
- 76.
- 77. @yshayy SeconditerationSeconditeration Lots of codeelimination Dependencies removal Leaner, more testable service Declarative approach Better visibility
- 78. @yshayy ArchitectureArchitecture External processes Agents &Proxies Co-scheduling
- 79.
- 80.
- 81. @yshayy HowdiditHowdiditaffectaffectus?us? Cleaner, leaner services Testinggot easier Faster adoptions of new languages and tools No more Soluto.Logging/Monitoring/Auth/... packages Rapid adoption of k8s by teams We're still learning...
- 82. @yshayy Howfarcanwego?Howfarcanwego? Gateways - routing,caching, validation, rate limiting, policies Configuration - secrets, cloud resource binding Tools - remote debugging/profiling Supporting services - analytics, feature flags, etc… Platform - FAAS/Serverless/Workflows Probably more… ( )https://landscape.cncf.io/
- 83. @yshayy As a developer,I want to focus on building features that deliver business value
- 84.
- 85.
- 86.
- 87. @yshayy Additionalresources‑toolsAdditionalresources‑tools AirBag - github.com/soluto/airbag DQD- github.com/soluto/dqd FluentD - Prometheus - Istio - Skaffold - github.com/GoogleContainerTools/skaffold Oidc-server-mock - github.com/Soluto/oidc-server- mock FluentD k8s level filter - github.com/Soluto/fluent- plugin-kubernetes-log-level https://www.fluentd.org/ https://prometheus.io https://istio.io/
- 88. @yshayy AdditonalresourcesAdditonalresources CNCF landscape - Designpatterns for container-based distributed systems - Introduction to modern network load balancing and proxying - https://landscape.cncf.io/ https://static.googleusercontent.com/media/research.google.com/e https://blog.envoyproxy.io/introduction-to-modern-network-load-b a57f6ff80236