3 ms·

It's almost as if there's no solution that's correct 100% of the time

• crdoconnor 11y ago
  This does : https://en.wikipedia.org/wiki/Loose_coupling https://en.wikipedia.org/wiki/Loose_coupling It seems a lot of people confuse "microservice architecture" for "loosely coupled architecture".
  • buckbova 11y ago
    Coupling and cohesion are not specific architecture choices like micoservices/business objects/etc but more of a way to describe the program design/architecture.
  • ExpiredLink 11y ago
    "the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. " http://martinfowler.com/articles/microservices.html http://martinfowler.com/articles/microservices.html
    • oldmanjay 11y ago
      Martin Fowler has some interesting ideas and writes some interesting articles, but he's not architecture jesus laying down inviolable laws on mere mortals. We get to virtualize the concepts at will. If I declare that all of my microservices get combined into a single process at the deploy stage, so let it be said, so let it done. Martin Fowler's opinion on it has no bearing. edit: accidental reply click