Microservices characteristics - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Which characteristic best describes microservices' independence?

Microservices are designed to be independent units. Which of the following best explains this independence?

A Each microservice can be developed, deployed, and scaled without affecting others.

B All microservices share the same database to maintain consistency.

C Microservices must be deployed together to ensure proper communication.

D Microservices rely on a single codebase for all services.

💡 Hint

Think about how microservices allow teams to work independently.

Microservices are independent units that can be developed, deployed, and scaled separately, which improves flexibility and fault isolation.

❓ Architecture

intermediate

What is the main advantage of decentralized data management in microservices?

Microservices often use decentralized data management. What is the main advantage of this approach?

A It forces all microservices to use a single shared database for consistency.

B It allows each microservice to manage its own database, reducing dependencies.

C It requires a central database administrator to manage all data.

D It prevents microservices from communicating with each other.

💡 Hint

Consider how data ownership affects service independence.

Decentralized data management means each microservice owns its data, which reduces coupling and allows independent scaling and deployment.

❓ scaling

advanced

How does microservices architecture improve scalability compared to monolithic architecture?

Consider a system built with microservices and one built as a monolith. How does microservices architecture improve scalability?

A Microservices cannot be scaled independently due to tight coupling.

B Microservices require scaling the entire system together to maintain consistency.

C Monolithic systems scale better because they use a single database.

D Microservices allow scaling only the parts of the system that need more resources.

💡 Hint

Think about resource usage and flexibility in scaling.

Microservices architecture allows scaling individual services based on demand, which is more efficient than scaling the whole monolith.

❓ tradeoff

advanced

What is a common tradeoff when using microservices for fault isolation?

Microservices improve fault isolation, but what is a common tradeoff of this benefit?

A Simplified debugging due to centralized logging.

B All services share the same failure domain.

C Increased complexity in managing inter-service communication and data consistency.

D Reduced ability to deploy services independently.

💡 Hint

Think about what happens when many small services need to work together.

While microservices isolate faults, they introduce complexity in communication and data consistency across services.

❓ estimation

expert

Estimate the number of microservices needed for a large e-commerce platform with catalog, user, order, payment, and notification features.

Given these features, estimate how many microservices would be appropriate to design for scalability and maintainability.

A 10 microservices, splitting features into smaller subdomains like product search and payment processing.

B 1 microservice handling all features to reduce complexity.

C 5 microservices, one for each feature area.

D 20 microservices, with each microservice handling a single database table.

💡 Hint

Consider splitting features into smaller logical parts for better scalability.

Large platforms benefit from splitting features into smaller microservices to isolate responsibilities and scale independently.