4 ms·

It seems like an endless cycle of some new trend coming out (microservices), then the reactionary comments which create even more new trendy buzzwords. Applicat

It seems like an endless cycle of some new trend coming out (microservices), then the reactionary comments which create even more new trendy buzzwords. Application design and development is not this black and white. SOA is not GOOD or BAD. It is a design structure that some people like, and some people seem to hate. There are good ways of doing things and bad ways of doing things. In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain. But, that is my opinion not something I think is a universal truth. Architecture/Design/Implementation of any complex system is not an exact science with perfect formulas for creation. It would be nice to have more articles about new and exciting ways of doing things, instead of the same old tearing down of others for being stupid/wrong/etc because they think functional/OO/SOA/microservices/containers/etc is the wrong way to do things.

AdrianRossouw 11y ago
> In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain. I think everybody agrees with that. The issue is that architecting your system like that on a code / repo level means that you gain the complexity of having to manage dependencies between your components, and it complicates the deployment story. microservices then further complicates things by requiring you to be able to independently deploy each service. this is a lot of complexity to manage for something that doesn't directly solve any problems in your business domain. This reaction you are seeing is because people have now had enough time to actually work on and hear about projects that were built using microservices. Many of them have found that they don't deliver on their promises, because of the reasons mentioned in the article.
andrewflnr 11y ago
You just rephrased the OP in a confrontational tone. It didn't say that SOA was bad, just overused in some places where it's not appropriate. It looks like the closest thing you have to a disagreement is that you can probably still get the some of the small code-base benefits while not getting into the distributed-systems stuff the article talked about (making sure your processes are all on the same machine or something, I don't know).

AdrianRossouw 11y ago

> In my experience, having small manageable code bases that are responsible for one domain makes things so much easier to develop and maintain. I think everybody agrees with that. The issue is that architecting your system like that on a code / repo level means that you gain the complexity of having to manage dependencies between your components, and it complicates the deployment story. microservices then further complicates things by requiring you to be able to independently deploy each service. this is a lot of complexity to manage for something that doesn't directly solve any problems in your business domain. This reaction you are seeing is because people have now had enough time to actually work on and hear about projects that were built using microservices. Many of them have found that they don't deliver on their promises, because of the reasons mentioned in the article.

andrewflnr 11y ago

You just rephrased the OP in a confrontational tone. It didn't say that SOA was bad, just overused in some places where it's not appropriate. It looks like the closest thing you have to a disagreement is that you can probably still get the some of the small code-base benefits while not getting into the distributed-systems stuff the article talked about (making sure your processes are all on the same machine or something, I don't know).