There is this youtube video from CodeOpinion where he says he prefers to start with a monolith but each bounded context would only communicate through public API and events as in microservices style. Everything is in a single codebase so quite easy to modify and since each bounded context is loosely coupled it should be easy to extract them if necessary. youtu.be/Z_pj1mUDKdw
And actually if microservices is not a good choice in you case, SOA would be worst. You will get most of the distributed architecture issues but in a more tightly coupled style do... More issues...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There is this youtube video from CodeOpinion where he says he prefers to start with a monolith but each bounded context would only communicate through public API and events as in microservices style. Everything is in a single codebase so quite easy to modify and since each bounded context is loosely coupled it should be easy to extract them if necessary.
youtu.be/Z_pj1mUDKdw
And actually if microservices is not a good choice in you case, SOA would be worst. You will get most of the distributed architecture issues but in a more tightly coupled style do... More issues...