Developing Service Oriented Architectures

Re:Developing Service Oriented Architectures by zimpenfish on Thursday March 20, 2014 @07:53AM (#7434951)

Last job wanted SOA but wouldn't deploy Rabbit (or any other message bus) because "it's another thing to look after". Ended up as a simple REST-alike webservice. Which I guess includes "service" in the description...

[ Parent | on HN ]

Re:Developing Service Oriented Architectures by mattmanser on Thursday March 20, 2014 @08:18AM (#7435032)

What's wrong with that? No need to overcomplicate stuff. That's a perfectly good solution depending on what reliability you want.

[ Parent | on HN ]

Re:Developing Service Oriented Architectures by zimpenfish on Tuesday March 25, 2014 @09:54AM (#7465820)

Oh, I have no objection to simple RESTian APIs. But they're very much not SOA.

[ Parent | on HN ]

Re:Developing Service Oriented Architectures by nbevans on Thursday March 20, 2014 @08:51AM (#7435181)

What you've just described is a proper micro service architecture. Which is basically a more minimalist and opinionated form of SOA.

Nothing wrong with wanting to avoid dependencies. Good programmers try to avoid dependencies and coupling, especially to third party products, all the time.

Service buses like Rabbit are cool n' all but sometimes you don't need the complexity.

[ Parent | on HN ]

Re:Developing Service Oriented Architectures by zimpenfish on Tuesday March 25, 2014 @09:56AM (#7465834)

No, it wasn't SOA or micro-services at all. There was one RESTian API which handled everything in a monolithic Perl app running in one Apache. No services anywhere to be seen.

[ Parent | on HN ]