The document discusses building a SaaS e-commerce system using microservices. It outlines the company's goals of working independently as scalable teams. It describes initially using an object-oriented microservice architecture with services for individual business domains. This led to issues of a distributed monolith due to tight coupling. The company then shifted to an aspect-oriented approach with services focused on specific user workflows. This reduced coupling and allowed independent development and scaling of teams within bounded contexts of the domain.

1. BUILDING A SAAS E-COMMERCE SYSTEM WITH
MICROSERVICES
JAN-OLIVER PANTEL
SOFTWARE ENGINEER @NEWSTORE

2. BUILDING A SAAS ECOMMERCE SYSTEM WITH MICROSERVICES
AGENDA
▸ Company & Goals
▸ Object Oriented Microservices
▸ Aspect Oriented Microservices
▸ Bounded Context and Team Changes
▸ Where we’ve got

5. GOALS

6. ONE COMPANY
WE WANT TO WORK AS

7. INDEPENDENT AND
SCALABLE TEAMS
WE DO OUR BEST TO ENSURE

8. INDEPENDENTLY
SCALABLE
WE WANT OUR SOFTWARE TO
BE

9. OBJECT ORIENTED MICROSERVICES

10. OBJECT ORIENTED MICROSERVICES
SHIPMENT
PAYMENT
SALES
ORDER
RETURNS
PRODUCT

11. OBJECT ORIENTED MICROSERVICES
SHIPMENTPAYMENT
SALES
ORDER
RETURNS
PRODUCT

12. OBJECT ORIENTED MICROSERVICES
SHIPMENT
PAYMENT
SALES
ORDER RETURNS
PRODUCT
NETWORK

13. DANGER OF THE
DISTRIBUTED MONOLITH
A OBJECT ORIENTED MICROSERVICE
ARCHITECTURE IS IN

14. SHARED CODE
DISTRIBUTED MONOLITH

15. The evils of too much coupling between services
are far worse than the problems caused by code
duplication.
Jan Stenberg (infoQ)
OBJECT ORIENTED MICROSERVICES

16. HIGHLY DEPENDENT
SERVICES
DISTRIBUTED MONOLITH

17. We can not just simply change that object. We
don’t know what this will do to our system.
Developer working on a distributed monolith
OBJECT ORIENTED MICROSERVICES

18. When I change this in service A I also need to
change that in service B.
Developer working on a distributed monolith
OBJECT ORIENTED MICROSERVICES

19. I need to know which other services I need to start
so that your service does not crash.
Dev-Ops working on a distributed monolith
OBJECT ORIENTED MICROSERVICES

20. BUILD
FUNCTIONALITY
WE DON’T WANT TO BUILD
OBJECTS, WE WANT TO

21. ASPECT ORIENTED MICROSERVICES

22. FUNCTIONALITY NOT
OBJECTS
SERVICES CARE ABOUT

23. CATALOG BROWSING CHECKOUT
AUTHORISE
CREDIT CARD
ROUTE ORDER PICK AND PACK
CHARGE CREDIT
CARD
PRODUCT PRODUCT PRODUCTPAYMENT PAYMENTORDER
ORDER ORDER

24. CATALOG BROWSING CHECKOUT PICK AND PACK
PRODUCT PRODUCT PRODUCT
•Price
•Tax class
•Weight
•Dimensions
•Image
•Name
•Image
•Price

25. The evils of too much coupling between services
are far worse than the problems caused by code
duplication.
Jan Stenberg (infoQ)
ASPECT ORIENTED MICROSERVICES

26. REPLICATE OVER
SHARING
ALSO ON THE DATA LEVEL

27. ENTITIES EVOLVE
INDEPENDENTLY
WE BECAME MORE FLEXIBLE
WHEN WE LET

28. LESS SCHEMA
COUPLING
SERVICES BECOME
INDEPENDENT THROUGH

29. YOU CAN SCALE THE
RIGHT PART
DEPENDING ON NEEDS

30. TO SHAPE A FINAL
PRODUCT
COMPOSE FUNCTIONALITIES

31. TIME TO GET THERE

32. LOW INTER TEAM
COMMUNICATION
TROUGH HIGH DISTRIBUTION

33. HIGH DEPENDENCIES
LAYERED APPLICATION WITH

34. LACKING
SCALABILITY
WE FOUND OURSELVES

35. Like any architectural style, microservices bring costs and
benefits. To make a sensible choice you have to understand these
and apply them to your specific context.
Martin Fowler
BUILDING A SAAS ECOMMERCE SYSTEM WITH MICROSERVICES

36. BOUNDED CONTEXTS

37. BUYEXPLORE OMS FULFILL
Browse and select products
Create and checkout order
Route order to store and inform customer
Guide associate through fulfilment

38. FOCUS TEAMS FOR
EACH CONTEXT
WE BUILD

39. BUYEXPLORE OMS FULFILL

40. BUYEXPLORE FULFILL
ROUTING
FINANCE

41. ROUTING
FINANCE
CHECKOUT
MONITORING
CATALOG
RECOMMEND
SHIP
OPERATE

42. COMMUNICATE
ACROSS TEAMS
WE LEARNED THE NEED TO

43. FIRST CHANGE THE
ORGANISATION
AS CONWAY TAUGHT US

44. WHERE WE’VE GOT

45. INDEPENDENT THROUGH
LESS COUPLING
TEAMS ARE MORE

46. END TO END IN ONE
TEAM
FEATURES ARE DEVELOPED

47. WE CAN SPLIT INTO
SMALLER TEAMS
WHEN THE TEAM GROWS

48. BUILDING FUNCTIONALITY
NOT BEHAVIOUR
TEAMS CAN FOCUS ON

49. SCRUM
WE REALLY HAVE FUN USING

50. A LONG WAY TO GO

51. GET IN TOUCH!

53. QUESTIONS?

54. APPENDIX
IMAGE SOURCES
https://pixabay.com/en/light-bulbs-hanging-lighting-918581/
https://pixabay.com/en/letters-numbers-blocks-alphabet-691842/
http://barnimages.com/wires/
https://pixabay.com/en/diner-restaurant-room-people-336499/
http://bossfight.co/wp-content/uploads/2015/05/boss-fight-free-stock-images-photos-photography-fingers-woman-string.jpg
https://www.pixabay.com/en/audience-crowd-people-persons-828584/
https://stock.tookapic.com/photos/28518
http://jaymantri.com/post/93427518193/download
https://pixabay.com/en/books-library-education-literature-768426/
https://static.pexels.com/photos/7096/people-woman-coffee-meeting.jpg
http://johnsonbrandon.com/assets/gallery_images/daily-scrum.jpg
https://pixabay.com/en/people-crowd-group-team-dock-690105/
https://static.pexels.com/photos/7075/people-office-group-team.jpg
https://pixabay.com/en/mechanics-engine-springs-mechanic-424130/
http://skitterphoto.com/?portfolio=car-engine
https://pixabay.com/en/rollercoaster-looping-amusement-801833/
https://stocksnap.io/photo/SWDR6XR7YS
https://stocksnap.io/photo/O7S9P51D9M
https://stock.tookapic.com/photos/7714
https://pixabay.com/en/digital-camera-disassembly-336670/
http://negativespace.co/photos/traffic-trails/
http://www.splitshire.com/straight-country-road/
http://skitterphoto.com/?portfolio=board-game
https://picjumbo.com/man-in-a-winner-pose-walking-on-the-road/
https://static.pexels.com/photos/519/light-sign-typography-lighting.jpg
http://www.splitshire.com/people-enjoying-concert/
https://www.pixabay.com/en/dart-target-aim-arrow-goal-point-444196/
https://stock.tookapic.com/photos/539
http://barnimages.com/old-mail-boxes/
http://barnimages.com/using-mobile-phone-in-cafe/
https://stock.tookapic.com/photos/31873