4 ms·

What is actually the difference between a "microservice" architecture, and a component based architecture?

• ownagefool 12y ago
  You can install a component and never upgrade it. You might fall behind on security concerns and be running different code from your counterparts but you can do that if you like. If you consume some service, you're going to have to keep your app up-to-date should the service chage, go away, or fail. Therefore one could argue that services are easier to manage centrally at the expense of some overhead and less flexibility.
  • mhluongo 12y ago
    That doesn't sound like a primary difference between the two? You can certainly leave up an old service.
    • vidarh 12y ago
      Yes, but that is not up to the consumer of the service (or not under the direct control of the consumer, in any case; assuming for the sake of argument that the consumer of the service is distinct from the producer)
• mhluongo 12y ago
  This might help http://petritsch.co.at/download/SOA_vs_component_based.pdf http://petritsch.co.at/download/SOA_vs_component_based.pdf It seems like a distinction is between organization-wide, discoverable services (SOA -> microservices) and reusable components that may or may not communicate via a remote protocol. EDIT - From reading more about component-based, another difference is that services are less tightly coupled. They often run on different machines & OS's, and are also often written in different languages. In the case of microservices, a common theme in these resources is that each microservice is owned by the part of the organization that created it, which is pretty interesting.