Moving from A and B to ~150 microservices, the journey, and learnings Geshan Manandhar Senior Software Engineer (THE ICONIC) @geshan

◉ Senior Software Engineer ○ Tech solution provider ◉ Agile follower ◉ Conditional microservices believer whoami

I am from Kathmandu, Nepal

I was working for a GFG venture in Middle East

Now I work at THE ICONIC

And I came here from the future, a future without legacy monoliths

Who ‘does not like’ working with legacy apps/monoliths?

What to expect from this talk?

No content

What is microservices architecture?

“ “Microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery” - Martin Fowler Source: https://martinfowler.com/articles/microservices.html

“ “Microservices is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities. The microservice architecture enables the continuous delivery/deployment of large, complex applications. It also enables an organization to evolve its technology stack” - Chris Richardson Source: http://microservices.io/

Microservices at Namshi

From 2 monoliths, to SOA (C) to Microservices, in past 4-5 years

Migrating to a REST based JSON API triggered a transformation

Stateless auth is a blessing, JWS in a cookie saved hassles.

A chunk of the backend is in PHP, other apps are built with NodeJs + Js

There are ~150 microservices at Namshi, with ~10 backend engineers

OMS Studio (Prod) Wallet Shipments Catalog QC Pick It Order Exporter WeBuy Cart Some of the microservices

Moving to microservices enabled to ship changes faster

Docker and kubernetes really helped to have a stable infrastructure

9 out of 10 applications at Namshi are written in Node Js

Microservices != free lunch, lots of configs come with it

How to get started with Microservices

Start with an opportunity to extract out a business feature/function

Transform a pain point into a new service

Solve a small part of the issue, collaboratively. Roll out working software

Think out of the box, don’t code a microservice like a monolith

Feature flags and canary deployments keep us on the safe side

Key Takeaways

Requires inter team communication, business needs to buy into the idea

Replacing frontend can take ‘X’ months, back-office will take years

Design your systems with resilience in mind from the beginning

How small is micro? Yes, Your service can be of ~100 lines of your code

It is about speed and agility of software delivery

Questions welcome :) THE ICONIC is hiring. You can find me at ◉ @geshan ([email protected]) ◉ Geshan.com.np ◉ Slides: http://bit.ly/ab-to-ms Thanks! Presentation template by SlidesCarnival

Credits/References ◉ https://pixabay.com/en/primate-ape-thinking-mimic-view-1019101/ ◉ https://pixabay.com/en/running-sprint-cinder-track-498257/ ◉ https://pixabay.com/en/stacked-stones-cairn-rock-balance-1007944/ ◉ https://pixabay.com/en/lego-stones-build-toy-622602/ ◉ https://pixabay.com/en/tractor-vehicles-farm-machinery-387275/ ◉ https://pixabay.com/en/workplace-team-business-meeting-1245776/ ◉ https://pixabay.com/en/network-server-system-2402637/ ◉ https://pixabay.com/en/logs-wood-timber-lumber-woodpile-498538/ ◉ https://pixabay.com/en/sunset-sea-the-sun-clouds-1603974/ ◉ https://pixabay.com/en/change-arrows-clouds-sky-direction-948024/ ◉ https://pixabay.com/en/cheetah-africa-namibia-cat-run-2859581/ ◉ Kathmandu - https://pixabay.com/en/nepal-kathmandu-buddhism-pagodas-306621/ ◉ https://pixabay.com/en/characters-shield-note-street-sign-3533352/ ◉ https://www.flickr.com/photos/brianandjaclyn/4137335458 ◉ https://pixabay.com/en/time-tiempo-count-day-future-699965/ ◉ https://pixabay.com/en/doors-choices-choose-open-decision-1767563/