問題文
A design team has to say what separates a modular single build from a set of microservices, if the two are alike in the way their interfaces are written. Which reading does the microservices guidance support, and what does it say about meeting a rise in load?
選択肢
- The parting line is that the interface of a microservice is written in a modeling language and is therefore quicker to review and open to reuse, while the calls inside a modular single build reach across the network, and a rise in load is met by giving more resources to the whole set of services, while a single build takes resources for the parts whose showing falls short, and a change in a small part of a single build sends that part out again, in that network-exposed difference.
- The parting line is that the interface of a microservice is exposed on the network and is therefore callable on its own and open to reuse, while the calls inside a modular single build are local to that build, and a rise in load is met by giving more resources to the whole set of services, while a single build takes resources for the parts whose showing falls short, and a change in a small part of a single build sends that part out again, in that network-exposed difference.
- The parting line is that the interface of a microservice is exposed on the network and is therefore callable on its own and open to reuse, while the calls inside a modular single build are local to that build, and a rise in load is met by giving more resources to the services whose showing falls short, while a single build takes resources for the whole of it, and a change in a small part of a single build sends the whole of it out again, in that network-exposed difference.
- The parting line is that the interface of a microservice is written in a modeling language and is therefore quicker to review and open to reuse, while the calls inside a modular single build reach across the network, and a rise in load is met by giving more resources to the services whose showing falls short, while a single build takes resources for the whole of it, and a change in a small part of a single build sends the whole of it out again, in that network-exposed difference.