When writing a new Spring web app, teams often have some nagging scaling doubts:
- How many users can my app simultaneously handle?
- How fast will my @RestControllers dash out those JSON responses?
- How much memory, CPU, or I/O does my application need?
- How much money do I need to spend on hosting?
Surprisingly, there's very little advice out there on how to sensibly approach these questions in a practical way—apart from simply autoscaling random Kubernetes pods into oblivion.
In this #almostnoslides session, we're going to use an IDE, a pen tablet, and a few libraries to get a deep, practical understanding of the following:
- Throughput and latency: How to (reliably) find out how many users your Spring app can handle
- CPU/memory/IO: How much (or how little) your app actually needs
- Hosting: What server your app needs
By the end of this talk, you'll have learned solid load-testing processes and skills that make you never worry about scaling your Spring web apps again.