Born in 1979, engineer, doctorate in 2008, I've started my working activity both as a researcher and as a freelance in the industrial automation field.
Yes, because you have to remember that more services require more boilerplate, more deploying time, more of non-core activity, therefore: either you automate every single bit to the extreme, or you are open to pay a lot of time to non-core as this saves time in development management (e.g: how the fox can I manage this new piece of functionality while not crashing everything around?! how can I better manage the scrum/agile/anything approach for a project such big?!)
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.
Qovery guy also said so. Just monolith first, until it scales.
Yes, because you have to remember that more services require more boilerplate, more deploying time, more of non-core activity, therefore: either you automate every single bit to the extreme, or you are open to pay a lot of time to non-core as this saves time in development management (e.g: how the fox can I manage this new piece of functionality while not crashing everything around?! how can I better manage the scrum/agile/anything approach for a project such big?!)