3 ms·
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 webservic
by zimpenfish 13y ago
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...
- mattmanser 13y agoWhat's wrong with that? No need to overcomplicate stuff. That's a perfectly good solution depending on what reliability you want.
- zimpenfish 13y agoOh, I have no objection to simple RESTian APIs. But they're very much not SOA.
- nbevans 13y agoWhat 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.
- zimpenfish 13y agoNo, 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.