Waking up in the weeds of microservices, how to diagnose your first bug.

Lightning talk from Swamp Up 2020

Transcript

1. WAKING UP IN THE WEEDS OF MICROSERVICES, HOW TO DIAGNOSE YOUR FIRST BUG.
2. ABOUT ME • Senior Software Engineer at Adobe • Interested in open source, cloud and technology evangelism • Open Source Advocate and Contributor to 20 + Open Source Projects (Hystrix, Servo, Contour, Spinnaker, OpenTracing, Istio, Liferay etc.) • Founder of Sunnyvale Java User Group, GDG Sunnyvale • Docker Mentor • Speaker into various conferences (OSCon, APIStrategy, JavaOne,API World, DockerCon, ScaleByTheBay) @mukteshkrmishra @mukteshkrmishra
3. MICROSERVICE ARCHITECTURE: A SYMPHONY HETEROGENOUS DISTRIBUTED RESOURCES MULTI-PASS https://medium.com/free-code-camp/a-note- on-distributed-systems-3c796f1eb0a0 https://medium.com/@hemantchhonkar/this- article-mainly-focuses-on-the-basics-about- microservices-be1917ddaaf1 https://medium.com/@tomasz_96685/saga- pattern-and-microservices-architecture- d4b46071afcf
4. DEVELOP CODE AND INFRA WITH OPERATIONAL EXCELLENCE MINDSET Logging Structured Common Formatted Observability Distributed Tracing Call Graphs Control Switches, bounded architectural contexts Aware about surroundings Controlled Blast radius Well defined SLXs Reduce noise Know System boundaries Smart alerting
5. WHAT DID WE LEARN THEN? • https://cloud.google.com/logging/docs/structured-logging • https://opentracing.io/ • https://apifriends.com/api-management/microservice-whodunit/ • https://howtodoinjava.com/log4j2/log4j-2-json-configuration-example/ • https://github.com/thangbn/json-logging-python • Loggers and information is important • Architecture consists of components • Call graphs should be traceable • Service Level Notations should be a part of design (shift left)