2
The scenario would be a great ERP application, it can be hosted on promisse or in the cloud according to customer needs.
What would be the best way to meet this type of architecture ?
Database architecture Centralized or distributed ?
Monolithic or Microservice Application ?
Use Docker for the seat and application or not, or use Docker for applications only ?
Without more information, it is not possible to answer, so it is not clear, or it is too broad or even bordering on the request of pure opinion. Although the subject is relevant and useful. I like the KISS of the YAGNI https://answall.com/q/23052/101. So right away I go centralized, if it is the meso that I understand of the term and monolithic, until it is necessary to do otherwise. I still don’t have an opinion on Docker, I’m not as sure as some that it’s always good.
– Maniero
I agree with @bigown, it will be a lot of opinion. Run away from the monolithic, and forget about database centralization. Docker is not part of your final solution, this is Host strategy. Here where I work we use Docker in development environment and automated testing, and Paas in environment, homologation and production. Microservices is not the opposite of monolithic.
– Thiago Lunardi
@Thiagolunardi to me is news microservices not to be the opposite of monolithic, unless you’re talking about something hybrid I wanted to know more, if it can be substantiated. Can I get an answer in https://answall.com/q/194663/101 or do you think I should ask a more specific question?
– Maniero
This is a common mistake. The fact of taking a monolithic system and breaking into parts, these parts will not necessarily be microservices, can be only services, with delimited contexts, all right, but without anything micro.
– Thiago Lunardi
If I can figure out a way to change your question to be able to answer, can I edit it to save it? Of course you can reverse it if you think I have changed too much what you want to know, although this will probably cause it to close.
– Maniero
@Thiagolunardi understood, this I know, is that there is not the opposite, is that it has middle term too.
– Maniero
Ramon Durães explains with a very pertinent example what can be considered a microservices in this video https://youtu.be/YOLFN_Du9E8
– Thiago Lunardi
@Thiagolunardi has already seen this and other Ramon videos. Don’t have a 100% opinion because it’s too early for anyone to have one. But the more I learn about microservices, the more I find it ugly to solve a problem that didn’t exist before people adopted solutions that weren’t needed. I have seen that MS is something very niche, although I think that this niche will grow a lot (from the engineering point of view, from the marketing point of view things grow without need even, which does not interest me), or for what I said before.
– Maniero
What Ramon clearly says is something to solve with monolithic specialized applications, which can even behave like a macro-service, and not with MS, but it’s trendy, so everybody goes for it. It’s a shame. Even defenders recognize that it is much more complicated to work with it. You have to have need to justify.
– Maniero
Yes, that’s right. In short, I don’t agree at all with monolithic practice, and deploy microservices when applicable.
– Thiago Lunardi
Well complicated, that theme. thank you very much for the opinions.
– Wandelson Bezer