GO And Monolith to Microservice

Transcript

1. DEVFEST Kırklareli GO And Monolith to Microservice Murat Mirgün Ercan
2. Software Engineer & Consultant Backend Development Lead at Tourist-App Supabase Golang Maintainer Mef University GDSC Workshop Lead Go Turkey Moderator
3. Work Life as a Student Why Go in My Career Path Microservices in Go
4. Student Life
5. Community Side
6. Why Go? Go is the new general-use programming language. Works with compiler It is a static type. Developed on concurrency. Simple
7. Understanding Go with Errors Go: * Understand what you are trying to do * Learn how it is done * Implement using go stdlib * If there is an error, read the message, look at the source code
8. Monolith Backends Single deployment Single runtime Single codebase •*interaction between classes is most often Synchronous Most often every layer is in a separate package
9. Microservice Backends Many small modules with specific functionality More than one codebase Every microservice is a separate deployment Every microservices has its own DB Communication with web-services/protobuf/thrift/…
10. Downsides Monolith "spaghetti", "big ball of mud" You need a full redeploy Programmers often violate the layer boundaries Classes often "leak" their implementation Hard to work with multiple teams Hard to manage
11. Downsides Microservices Modelled around the business domain Deployment automation culture Hides implementation details Decentralization Option to use multiple languages Separate deployment, separate monitoring isolating problems
12. How We Use Microservices in Tourist