No dates yet
Tell us the schedule that would work
We plan batches around demand. Weekend, morning and intensive formats open when enough people ask for them.
Register your interestDTA-09AvailableJavaSpring BootSpring CloudResilience4jKafkaOpenTelemetryDocker
Microservices with Spring Cloud
Split one service into several without inventing a distributed monolith
- Fee
- ₹3,600
- Duration
- 20 guided hours
- Level
- Advanced
- Mode
- Online / Offline
Designed for
- Backend developers whose single service has outgrown one team
- Engineers who have heard "we use microservices" and want to know what that costs
- Anyone asked in an interview why a retry made an outage worse
Course curriculum
6 progressive modules
Duration: 20 guided hours
- Foundation
- Intermediate
- Advanced
FoundationSessions 1–2
When not to split
- What a service boundary is, and what a database boundary is
- The distributed monolith, and how teams arrive at one
- Costs you take on the day you split — latency, partial failure, deployment
- Modular monolith as the honest default
- Deciding a boundary from how the business changes, not from the schema
What you will build
One monolith cut into two candidate boundaries, with the second one argued down and abandoned in front of the room.
Module 1
FoundationSessions 1–2
When not to split
- What a service boundary is, and what a database boundary is
- The distributed monolith, and how teams arrive at one
- Costs you take on the day you split — latency, partial failure, deployment
- Modular monolith as the honest default
- Deciding a boundary from how the business changes, not from the schema
What you will build
One monolith cut into two candidate boundaries, with the second one argued down and abandoned in front of the room.
Module 1
Learning outcomes
What you will be able to do
- 01Argue when a system should not be split, with reasons a reviewer accepts
- 02Route and secure traffic through a gateway without duplicating concerns
- 03Set timeouts, retries and circuit breakers that make an outage smaller
- 04Design a consumer that tolerates the same message arriving twice
View all 6 learning outcomes
- Trace one request across several services and find the slow span
- Diagnose a partial failure rather than restarting until it goes away
Batches
Choose a schedule that works for you
Who teaches this
Learn with experienced practitioners
All trainers and mentors
Vishal Shah
Founder & Principal Trainer
Two decades building and teaching commerce, banking and cloud platforms — still writing code
- Java & Spring Boot microservices
- TypeScript, React, Angular & Next.js
- Composable commerce (commercetools)
Detailed course information
Full course brief
Most microservices teaching starts with how to split. This starts with when not to — because the expensive mistake in this field is not a monolith, it is a distributed system built by a team that did not need one.
Once you have argued a boundary properly, the rest of the course is about what you have just taken on: partial failure, duplicate messages, and the fact that you can no longer see the whole system in one log file.
Who this is for
You need a working Spring Boot service and an understanding of transactions. If you do not have that, Spring Boot & REST APIs comes first.
Where it leads
Group three of Full-Stack Developer — Java and group six of Backend Developer — Java.
Get batch details
Tell us the schedule that would suit you and we will let you know when a batch opens.
Where this leads
Step 4 of 6
Java Full-Stack Developer · 3–4 months
Step 4 of 4
Java Backend Developer · 6–8 months
Need help deciding?