liveBook · Manning

Resource requirement

As explained in Microservices Patterns, Second Edition

A resource requirement is the amount and type of computing resources needed by software to achieve its operational goals.

Subdomains can need different amounts or types of CPU, GPU, memory, network bandwidth, storage, and service instances. Because services scale by instance, combining subdomains with mismatched needs can overprovision resources. Separating them into services allows independent scaling, improving utilization and potentially reducing costs. section 7.4.5

Order management and fraud detection

An application needs 10 Order Management instances but only 5 Fraud Detection instances, which require GPUs. If both subdomains share a service, five instances’ fraud-detection capacity is underused. Separate services can scale each subdomain to its own needs. section 7.4.5

Figure 7.7 Subdomains within the same service are scaled together, which can require over-provisioning of some resources. Putting them in separate services enables them to be scaled independently which improves resource utilization and reduces cost.
segregate by resources

Compare coupled scaling within one service with independent scaling after separating subdomains. section 7.4.5

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines resource needs and instance counts, then traces coupled scaling to overprovisioning and cost; does not compare broader design trade-offs.
Examples
Contrasts 10 Order Management instances with 5 GPU-equipped Fraud Detection instances.
What you can do after
Evaluate whether separating subdomains can align service scaling with their resource needs and reduce overprovisioning.
How it connects
Connects microservice architecture, subdomains, scalability, availability, and resource utilization.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.