``` You should always start with a monolith. Ensure that it is well tested, well designed and developed with several iterations from the core developers. ``` U

``` You should always start with a monolith. Ensure that it is well tested, well designed and developed with several iterations from the core developers. ``` Upgrading services can be a pain, but starting with a monolith is not a requirement. Architecture can happen before any code is written, and it can illustrate a need for SOA (or not). Difficulty in changing your services as your product matures or as requirements change will be hit at the beginning, but there is not hard stop to that either. Vague statements like the above leave us in the monolith culture indefinitely. It does, however, speak to the need to understand/form patterns for service upgrades.