Komplett Group is a large ecommerce company that started with a monolithic architecture but is transitioning to microservices. They made several mistakes in their transition including rewriting everything at once and just adding more developers without changing their processes. They have learned that services need to be independently deployable and scalable. Their current approach is to split functionality out of the monolith into small, autonomous services with consistent deployment processes. They are continuing to refine their architecture, processes, and organization to support scaling their business needs through continued learning from failures.

1. Making Komplett BIG
By Going Small
Making every mistake count

2. Who Are We?
Pavneet Singh Saund
Web Developer
@pavsaund
Tomas Ekeli
Lead Software Architect
@tomasekeli

3. Let’s talk about...
How we are scaling our architecture, process
and organization to meet ever-changing business
needs.

4. Komplett Group
16 web shops
7.3 Billion NOK revenue 2015
1.8 Million active customers
800 Employees
20 Million uniques

6. In The Beginning

7. In The Beginning

8. In The Beginning

10. We’re in a bad place...

11. Business Need: “We need a mobile web presence”
Developers: “Sure, we can do that”

12. Mistake:
“Rewrite Everything!”

13. Business Need: Mobile First http://m.komplett.no
Project K2
Code Quality
SOLID
Test-Driven
CQRS
Event Sourcing
Domain Driven Design
Scrum
Pair-programming
New admin pages
New infrastructure
New architecture
New deployment pipeline

14. K2 is a Deadly Mountain
Our project did not survive

15. Learning:
“Don’t Rewrite Everything!”

16. It was a dark time…

17. They Still Trust Us!
New business-domains.
Great big heap of code.
Can we do this?
but...

18. Do We Trust Us?

20. Mistake:
“Just Add Developers”

21. Before Scaling

22. Spotify Model

23. The Minion-project

25. Growing Pains

26. Komplett As Services
Our architectural vision
A landscape of small Services
Versioning is naming
Consistent deployment
Splitting out services from the monolith

27. Creating A New Service

28. Learning:
“Services must be cheap”

29. OK, How Do We Do That?
How can we get all this done?
How do we push more features through the pipeline?

30. Komplett Model

31. '

32. How we communicate

33. Learning:
“Organisation matters”

34. Mistake:
“Just split it into services”

35. OK, How Do We Do That?
How do we keep it running?
Caching
Performance tests
Independently scaling services
Health-checks and monitoring
Central logging service

36. Learning:
“Services are differenterer”

37. Where Do We Go From Here?
Fully mandated squads?
More microservices?
Public APIs
More business-areas!

38. Summary
Scaling is hard
Culture is Crucial
Embrace and learn from failures
We intend to keep failing and sharing as we go.

39. HAPPY PEOPLE MAKE GREAT STUFF
A sad and 'red developer does not a good system deliver. Having a great 'me is the best
indicator of whether or not you're heading for success.

40. Let’s Talk
@komplettdev, http://kodepanelet.no
@pavsaund, http://codingwithempathy.com
@tomasekeli