Week 14

Architecture Patterns

Communication Patterns

Background Processing

Architectural Trade-offs

Messaging

Hands-on: RabbitMQ

Practice

Assignment

• Teachers

Backend Track

Week 14 Overview

Until now, your backend has been a single service: one Spring Boot application talking to one database. Real systems rarely stay that simple. Some work is too slow to happen during a request, and some systems grow too big to live in one deployable unit. This week you will see how backends grow beyond a single service: architecture patterns, communication between services, background work, and message queues.

Learning goals

• Explain when a monolith is enough and what microservices trade off against it
• Choose between synchronous and asynchronous communication between services
• Move slow work out of the request path with background jobs and a message queue
• Run a RabbitMQ producer and worker, and make the consumer safe to retry

The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

Built with ❤️ by the HackYourFuture community · Thank you, contributors

Found a mistake or have a suggestion? Let us know in the feedback form.