Backend Engineering in Ruangguru

With Agung Wahyu Kurniawan, we share about our backend engineering practice in Ruangguru

Transcript

1. Backend Engineering in Ruangguru Agung Wahyu Kurniawan Harits Fahreza Christyonotoputra
2. Halo Ker!
3. 15 awesome backend engineers and keep counting We design, analyze, code, review, deploy and repeat
4. Once upon a time ...
5. Monolith
6. Until ... • Our team is getting bigger • More complex • Not reliable • Scalability
9. Is it hype technology? Well, not really... 2014 Martin Fowler He discussed microservices in his blog 2017 Ruangguru was infected Our first milestone to implement microservices 2011 “Microservice” discussed at a workshop of software architects near Venice 2012 “Microservices” same group decide `microservices` as the coolest name
11. Pros • Reduce system complexity • Increase development speed on each domain • Improve fault isolation • Increase product ownership • Loosely coupled • Integration Testing • Deployment • Maintenance (Logging, Alerting, Auto Scaling) • Transactional Data Cons
12. Why we REALLY needs microservices • We have a LOT of business domains • We have teams that works independently with their own tempo, target and problem • We don't want to disturb our colleagues if our service is broken
13. How Microservices is implemented in Ruangguru
14. Development Process Define Business Requirements Define business requirements with product team Design Architecture Design architecture written by software engineer What Technologies? Decide tech stack, what should we choose the technologies Let's code & deploy! What are you waiting for~ Write Docs We are human, btw 05 01 02 03 04
15. Languages
16. Project Structure
17. Entity • Table representation • Request and Response
18. Repository
19. Service • Business Logic • Cross domain service • Interservice Client
20. Protofile • GRPC Related • Function and Entity • Generate via rogu
21. Handler • GRPC / REST Handler • Convert pb to domain struct
22. Async Process
23. Unit Test • Implementing unit test in each of the layer • Mock the dependencies (service unit test, mock the repo) • Why? To make sure our code is not break
24. Communication Protocol But ...
25. Introducing Morse • Go framework to run REST and GRPC concurrently • REST x GRPC Reverse Proxy • Why? ◦ Legacy service is still using REST ◦ All-in-one interceptor
26. Rogu CLI • CCLI tools to speed up our development process • Why we need rogu? ◦ Deploy ◦ Generate proto file ◦ Deployment status ◦ Scaling ◦ And many more ...
27. 100+ Services maintain (and keep going). Approx. 90% written in Golang!
28. What’s Next?
29. In the next few months, we want to ... • Implement Event Driven • Open Source • Automation Testing • Implement GraphQL, will improve 30% in client
31. Nuwus Ker!