When starting with microservice architectures a common question people ask is "how big should a service be?” While this is sometimes useful when considering the complexity of a system, it doesn’t capture the variety of use cases or problems systems may be solving — a service that selects emoji for push notifications will probably be simpler than one of the core services in a payment processor?
In this talk we’ll look at how Monzo approach problem solving, taking business ideas and breaking them down into small, simple, services which together build a system that is more than the sum of its parts.
mattheath
miciek
mugi_uno
minako__ph
takefumiyoshii
twada
ivargrimstad
.jpg){kind=avatar}
yumnumm
aridlehoover
toricky6
akkyie
ivanova1991
chimame
edds
rmw
kevinliebholz
shlominoach
bkeepers
soudai
maltzj
tmm1
chriscoyier
brianwarren
geoffreycrofte
ddemaree