O'Reilly logo
  • Kevin Cho thinks this is interesting:

it became clear that the use cases of SnapCI were subtly different enough that the initial take on the service boundaries wasn’t quite right. This led to lots of changes being made across services, and an associated high cost of change. Eventually the team merged the services back into one monolithic system, giving them time to better understand where the boundaries should exist


Cover of Building Microservices


How about us?