Cloud-Native Architecture

Build by hand the pieces you need the moment you split one service in two. Six courses: service-to-service communication and resilience, queues and asynchronous APIs, Redis caching and live leaderboards, S3 and SeaweedFS, order events flowing through Kafka, and Raft consensus down to the moment there are two leaders. By the end you can argue in an architecture review in terms of what you pay and what you get.

코스

• Microservice Architecture — How not to split, before how to split.
• Queues and Asynchronous APIs — Slow work, later and safely.
• Redis and Caching — Leaderboards with ZSet; caches, carefully.
• Object Storage and S3 — Thinking in objects rather than files.
• The order arrived twice, and once it vanished — Reproduce and stop duplicates and loss on a single-node KRaft broker
• There Were Two Leaders — Feel terms, quorum and partitions with your own hands