RESPECTING THE MICROSERVICE.

Learning to respect the microservices through experience. We go through lessons learned from multiple scenarios based on Google Cloud

Transcript

1. Johann du Toit GDE Cloud @signedness RESPECTING THE MICROSERVICE. Learning to respect the microservices through experience.
3. qvik.com/monolith Been on a mission On how microservices if done right can change organizations for the better, but mostly they are used with any thought on long term
5. Microservices
6. Microservices
7. STANDARD EXTENDED
8. STANDARD EXTENDED
11. “It's fine to celebrate success but it is more important to heed the lessons of failure.” - Bill Gates
12. • What are microservices? • Lessons learned where it went wrong • Lessons learned where it went right • Closing Words and complete list Hopefully have some fun along the way Talking Points For those who love and hate these
13. Rinse and repeat What are microservices? I know. I know.
14. Who has had the privilege of working on a code base more than 10 years old?
20. URL Scraping The beginning of the end I was a excited and way too positive Lead Developer who wanted to fully embrace microservices
21. SCORE TESTS URL the idea was simple
23. CSS DNS HTML HTTP INSPECT JAVASCRIPT LIGHTHOUSE LINKS MALWARE MOBILE NETWORK SEO SOCIAL SPELLCHECK SSL ACCESSIBILITY
24. CSS DNS HTML HTTP INSPECT JAVASCRIPT LIGHTHOUSE LINKS MALWARE MOBILE NETWORK SEO SOCIAL SPELLCHECK SSL ACCESSIBILITY
25. passmarked <-r> http://example.com
29. CSS DNS HTML HTTP INSPECT JAVASCRIPT LIGHTHOUSE LINKS MALWARE MOBILE NETWORK SEO SOCIAL SPELLCHECK SSL ACCESSIBILITY
31. SCORE API URL Architecture in a nutshell
32. API URL Realtime all the way WSS
33. 40 services URL =
34. 40 services CHANGE = PLANNING COMMON SCHEMA STATE CHANGES VERSIONING CAPACITY SPEED
35. • ... • ... • … • ... • ... Let’s explore. Lessons? Quite a few ...
36. • Not every feature has the right of microservice • ... • … • ... • ... Let’s explore. Lessons? Quite a few ...
42. • Not every feature has the right of microservice • Logging becomes very important... • ... • ... • … • ... Let’s explore. Lessons? Quite a few ...
45. • Not every feature has the right of microservice • Logging becomes very important... • The amount of microservices per developer… • ... • … • ... Let’s explore. Lessons? Quite a few ...
47. • Not every feature has the right of microservice • Logging becomes very important... • The amount of microservices per developer… • Shared libraries in a fully microservices architecture points to bad coding practices • … • ... Let’s explore. Lessons? Quite a few ...
49. WORKER 1-24 COMMON LIBRARY WSS API
50. WORKER 1-24 COMMON LIBRARY WSS API
51. • Not every feature has the right of microservice • Logging becomes very important... • The amount of microservices per developer… • Shared libraries in a fully microservices architecture points to bad coding practices • Keep track and limit service-to-service calls • ... Let’s explore. Lessons? Quite a few ...
52. • Not every feature has the right of microservice • Logging becomes very important... • The amount of microservices per developer… • Shared libraries in a fully microservices architecture points to bad coding practices • Keep track and limit service-to-service calls • ... Let’s explore. Lessons? Quite a few ...
54. Service #2 Service #1 Service #4 Service #3 Service #5
55. Service #2 Service #1 Service #4 Service #3 Service #5 41ms 160m s 67ms 31m s 1.2s 5s 1.3s 300ms ? ? ?
56. Service #2 Service #1 Service #4 Service #3 Service #5 41ms 160m s 67ms 31m s 1.2s 5s 1.3s 300ms ? ? ?
57. Service #2 Service #1 limit calls to 1-2
58. • Not every feature has the right of microservice • Logging becomes very important... • The amount of microservices per developer… • Shared libraries in a fully microservices architecture points to bad coding practices • Keep track and limit service-to-service calls • Boring is Good™ Let’s explore. Lessons? Quite a few ...
62. Reservations Success with microservices Let’s explore a recent successful implementation of microservices I was involved with
63. Phase 1 • Migrate fully to Kubernetes/Docker • Setup a development workflow develop/master • Setup Standardized Health Checks • Get a good idea of metrics on the site Phase 2 • Create a service to specially deal with speed • Migrate all logic over from monolith to this service • Deployment and benchmarking of service
64. • ... • ... • ... • ... • ... Let’s explore. Lessons? Quite a few ...
65. • Good Base for development will do wonders • ... • ... • ... • ... Let’s explore. Lessons? Quite a few ...
68. • Good Base for development will do wonders • “Scaling Sessions” • ... • ... • ... Let’s explore. Lessons? Quite a few ...
70. • Good Base for development will do wonders • “Scaling Sessions” • Small optimizations add up quickly • ... • ... Let’s explore. Lessons? Quite a few ...
71. • Good Base for development will do wonders • “Scaling Sessions” • Small optimizations add up quickly • Standardized health checks • ... Let’s explore. Lessons? Quite a few ...
72. • Good Base for development will do wonders • “Scaling Sessions” • Small optimizations add up quickly • Standardized health checks • Cronjobs will not be made for running in parallel Let’s explore. Lessons? Quite a few ...
73. • Not every feature has the right of microservice • Distributed logging becomes very important... • The amount of microservices per developer… • Shared libraries in a fully microservices architecture points to bad coding practices • Boring is Good™ • Good Base for development will do wonders • Highly recommend Scaling Sessions • Small optimizations add up quickly • Standardized health checks • Cronjobs will not be made for running in parallel All together make a nice checklist
74. • Team Size? • State Management? • Consumer Diversity? • Logic Dependencies? • Team Expertise? • How does the Workflow? • What metrics are we specially tracking? Questions to ask yourself
75. As I grow more and more old and grumpy I’ve learned to love the monolith and be very careful on when I go the microservice approach.
77. Johann du Toit GDE Cloud @signedness Thank You!