Performance & Production Readiness
Two hands-on days finding out why a system is slow and proving you fixed it - profiling, load testing, database tuning, JVM behaviour and a readiness review. You leave with a measured improvement on your own code and a checklist you can apply to any service.
- Fee
- ₹2,700
- Duration
- 2 days · 16 hours
- Each day
- 09:00 - 17:00
- Mode
- Offline / Online
Designed for
- Developers told to make it faster with no idea where to start
- Engineers who have optimised the wrong thing and lost a week
- Teams preparing a service for its first real traffic
What to bring
- A laptop with Java, Docker and an IDE installed
- A service of your own, ideally one you suspect is slow
- Basic SQL
What you walk away with
A measured before-and-after on your own service, a load test you can rerun, a database index you justified with an execution plan, and a production readiness checklist marked up against what you actually run.
Outcomes
What you will be able to do
- 01Set a performance target that is a number rather than a feeling
- 02Write a load test that reflects real traffic instead of a flat curve
- 03Read a profile and name the method responsible
- 04Read an execution plan and say why the database chose that path
View all 9 outcomes
- Add an index for a reason, and know what it costs on write
- Recognise N+1, chatty calls and unbounded queries in review
- Explain what the JVM is doing with memory and when garbage collection matters
- Size a connection pool and a thread pool from evidence
- Run a production readiness review against a service you did not write
The two days
8 hands-on sessions
2 days · 16 hours
- Foundation
- Intermediate
- Advanced
FoundationDay 1 - 09:00 - 10:30
Guessing is the problem
- latency against throughput
- percentiles and why p99 is the user
- setting a target before touching code
- the cost of optimising the wrong thing
- Amdahl in plain terms
- establishing a baseline you can return to
What you will build
A baseline captured for a real endpoint, with p50 p95 and p99 recorded and a target agreed.
Module 1
FoundationDay 1 - 09:00 - 10:30
Guessing is the problem
- latency against throughput
- percentiles and why p99 is the user
- setting a target before touching code
- the cost of optimising the wrong thing
- Amdahl in plain terms
- establishing a baseline you can return to
What you will build
A baseline captured for a real endpoint, with p50 p95 and p99 recorded and a target agreed.
Module 1
Book this workshop
This workshop runs on request, for individuals and for teams. Tell us the dates that would suit you.
Running this for a team?