An interesting thing I've read recently is that there can be different kinds of monolith: - application monolith (what we usually talk about) - database monol

An interesting thing I've read recently is that there can be different kinds of monolith: - application monolith (what we usually talk about) - database monolith (multiple apps all using one db) - deployment monolith (multiple apps but need to be deployed together) - organization monolith (multiple apps built by teams that have to follow the same processes and practices, or using the same technologies) This made me think that migration to services has different layers and just running multiple apps might solve some problems, bet introduce others. I think learning how to slice things properly is the key here and is often only considered in terms of source code.