For your core service. I think you are right most of the time.
But you are probably not talking about the website marketing wants to build.
And you are maybe using S3 or similar for documents storage?
And your logging system are probably not on the same machine?
But if by "system" you mean the main API + SaaS website or similar yeah. Sounds reasonable.
in reality we do so much more now. That I think some part of what was the monolith years ago is now just SaaS the company use. That the development department do not even need to know about.
I agree that I took it "a bit" far to make a point… that just ruined my case.
I do think that in a monolith you try to do most things yourself.
Take Auth for example. It's huge. And I think we more and more are excepting that even for a monolith we do not want to do that ourself.
If you start from scratch and your spec say that they want OIDC and SAML then most ppl will look for a saas service to get help.
Same with storing files, we would make use of S3 or similar.
But if we go to pre 2010. I think most people would try to both of these themself.
Im not saying that this is microservice at all, but I'm saying we are moving stuff that are commodity's out from the monolith compare to what we did 10-15 years ago. Because there are services that does a much better job for us.
And that was part of my point with the original comment. That trying to keep everything in one place is probably not the right choices.
Sorry for not being more precise on my previous reply.
Yes, you should build your system initially like that. One team builds one system and splits it out as necessary.