When creating a new Microservice you typically need to add a lot of boilerplate to the code, such as logging, metrics, authentication, SSL, secrets/credentials, etc... All this ends up overshadowing the actual logic of the service itself and results in a lot of dependencies and code. Because of this, we at Soluto created a template for the boilerplate, which worked great... ​ Until we had to upgrade one of the dependencies which resulted in huge effort of code upgrades and deployment across each and every service that uses the template. And that’s besides the fact we needed to make a separate template for each language we used (and over the years, the number of programming languages we use at production increased dramatically). We needed a way to simplify all this. We wanted to get rid of the boilerplate while maintaining the functions listed above. So we decided to delegate the entire responsibility to the Kubernetes infrastructure. In this lecture, I will do a live coding session and show you how to remove the boilerplate from your code and move it to the infrastructure, and discuss the benefits and limitations of this approach.

1. @yshayy
Notmyproblem!Notmyproblem!DelegatingrespobisiblitestoDelegatingrespobisiblitesto
infrastrucutreinfrastrucutre
Yshay Yaacobi
@yshayy
https://git.io/fxh57

2. @yshayy
As a developer, I want to focus on
building features that deliver
business value

3. @yshayy
InfrastructureInfrastructure

4. @yshayy
Monolith ---------→ Microservices

5. @yshayy
FewMonolithsFewMonoliths
Monolith #1
Monolith #2 Monolith #3

6. @yshayy
FewMonolithsFewMonoliths
Application code
Infra code
Application code
Infra code
Application code
Infra code

7. @yshayy
Monoliths ----→ Lots of Microservices

8. @yshayy
Monoliths ----→ Lots of Microservices

9. @yshayy
ServicestructureServicestructure
----→
Infra-code and business logic code live together with
every Microservice

10. @yshayy
ServicestructureServicestructure
----→
How can we write 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 Tel Aviv, acquired by Asurion at 2013
Next generation of tech support
150M users worldwide
We love open-source

14. @yshayy

15. @yshayy
ShiftingtomicroservicesShiftingtomicroservices
~5 services -> 100+ services
Cultural change, new aspects of ownership
CI/CD - Better tooling automation
Self-service

16. @yshayy
HowdoesaserviceHowdoesaservice
looklike?looklike?

17. @yshayy
DEMO‑NotificationsserviceV1DEMO‑NotificationsserviceV1

18. @yshayy
Spec‑NotificationsserviceSpec‑Notificationsservice
We want to send notifications to users
Notifications will be based in templates
Notifications will be personalized

19. @yshayy
Flow‑NotificationserviceFlow‑Notificationservice
1. Get user identifier and notification type
2. Fetch user details from users micro-service
3. Format message using a template
4. Send a message

20. @yshayy
Let'swritesomecodeLet'swritesomecode

21. @yshayy
DemoDemo

22. @yshayy
What'smissing?What'smissing?
- Visibility
- Security
- Resiliency

23. @yshayy
LoggingLogging
We need to add a logger
We send logs to a 3rd party provider
Let's get a library + a provider

24. @yshayy
☑ Logging
☐ Error policies
☐ Authentication
☐ Monitoring

25. @yshayy
ErrorpoliciesErrorpolicies
The network can fail
We want to retry failed requests
Let's add Polly

26. @yshayy
☑ Logging
☑ Error policies
☐ Authentication
☐ Monitoring

27. @yshayy
AuthenticationAuthentication
We'll use JWT token
OIDC/OAuth2

28. @yshayy
☑ Logging
☑ Error policies
☑ Authentication
☐ Monitoring

29. @yshayy
MonitoringMonitoring
Performance metrics, throughput, latency
Statsd client

30. @yshayy
☑ Logging
☑ Error policies
☑ Authentication
☑ Monitoring

31. @yshayy
DemoDemo

32. @yshayy
Whatjusthappenedhere?Whatjusthappenedhere?
We wanted a small micro service and got a
bunch of code and dependencies

33. @yshayy
Whatjusthappendhere?Whatjusthappendhere?
4 X Lines of 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
Dependencies can break
Dependencies can conflict
Dependencies requires re-build+re-deploy
Extremely difficult to introduce global change

36. @yshayy
Andthat'snottheworse...Andthat'snottheworse...

37. @yshayy
WeneedtosolveitforeachandeveryWeneedtosolveitforeachandevery
programminglanguageprogramminglanguage

38. NotalllanguagesarebornequalNotalllanguagesarebornequal

39. @yshayy

40. @yshayy
As a developer, I want to focus on
building features that deliver
business value

41. @yshayy
Which of these concerns can be solved at environment
level ?

42. @yshayy
Soluto‑microservicesv2Soluto‑microservicesv2
+

43. @yshayy
KubernetesKubernetes
Orchestrate our services
Solves many cross cutting concerns

44. @yshayy
AASidecarSidecarContainerContainer
Additonal Container in a pod
Provide functionality
to support main app
Co-scheduled together in
replicas

45. @yshayy
SidecarscanhelpussolveSidecarscanhelpussolve
infrastructureconcernsinfrastructureconcernsexternallyexternallytoto
ourappourapp

46. @yshayy
Let'sgetridofstuffLet'sgetridofstuff

47. @yshayy
LoggingRevisitedLoggingRevisited

48. @yshayy
LoggingLogging
Treat Logs as event streams
Use log forwarder
Scrape the logs from Docker

49. @yshayy
FluentDFluentD
Run on every node (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
☑ Error policies
☑ Authentication
☑ Monitoring

52. @yshayy
ErrorpoliciesRevisitedErrorpoliciesRevisited

53. @yshayy
ErrorpoliciesErrorpolicies
Service-mesh, THE buzzword for 2018
Istio
Injects proxy sidecar

54. @yshayy
Servicemesh‑IstioServicemesh‑Istio

55. @yshayy
Servicemesh‑ResiliencyServicemesh‑Resiliency
Configurable failure handling

56. @yshayy
ServicemeshextrabenefitsServicemeshextrabenefits
Security
Traffic management
Tracing
Too many to count...

57. @yshayy
☑ Logging
☑ Error recovery
☑ Authentication
☑ Monitoring

58. @yshayy
AuthenticationRevisitedAuthenticationRevisited

59. @yshayy
AuthenticationAuthentication
Let's use a sidecar
Soluto/Airbag

60. @yshayy
Authentication‑AirbagAuthentication‑Airbag

61. @yshayy
Authentication‑AirbagAuthentication‑Airbag
Configuration yaml example
Open source
Probably be superseded by
Istio's origin authentication

62. @yshayy
☑ Logging
☑ Resiliency
☑ Authentication
☑ Monitoring

63. @yshayy
MonitoringRevisitedMonitoringRevisited

64. @yshayy
MonitoringMonitoring

65. @yshayy
☑ Logging
☑ Resiliency
☑ Authentication
☑ Monitoring

66. @yshayy
DEMODEMO

67. @yshayy
AnewrequirementAnewrequirement
It's black friday!
We want to send lots of messages

68. @yshayy
AnewrequirementAnewrequirement
It's a batch process
Let's use a queue

69. @yshayy
Howdeweprocessqueueitems?Howdeweprocessqueueitems?

70. PrevioussolutionsPrevioussolutions

71. @yshayy

72. YetAnothersidecarYetAnothersidecar

73. @yshayy

74. @yshayy
DequeueDaemonSidecarDequeueDaemonSidecar
Soluto/DQD
Read items from queue, activate service
Back-pressure support
Expose consumption metrics

75. @yshayy
DQD‑DemoDQD‑Demo

76. @yshayy
DQD‑benefitsDQD‑benefits
Scaled with service
Testing
Agnostic

77. @yshayy
SeconditerationSeconditeration
Lots of code elimination
Dependencies removal
Leaner, more testable service
Declarative approach
Better visibility

78. @yshayy
ArchitectureArchitecture
External processes
Agents & Proxies
Co-scheduling

79. NotalllanguagesarebornequalNotalllanguagesarebornequal

80. @yshayy
X

81. @yshayy
HowdiditHowdiditaffectaffectus?us?
Cleaner, leaner services
Testing got 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. @yshayy
WhatcantheWhatcanthe
infrastructuredoforinfrastructuredofor
you?you?

85. @yshayy
Thankyou.Thankyou.

86. @yshayy
Questions?Questions?
(Yes, we're hiring )

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 -
Design patterns 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