Spring Boot Fundamentals
Fast recall
Quick revision
Core answer
java -jar or a single main method. It exists because the raw Spring Framework, while powerful, required significant manual configuration (XML, then Java config), dependency wiring, and an external servlet container to run; that ceremony slowed development and made onboarding hard. Spring Boot's auto-configuration, starters, and embedded server collapse weeks of plumbing into minutes, while staying 100% Spring under the hood.Whether you understand Spring Boot as an opinionated auto-configuring layer on Spring (starters, embedded server, sensible defaults) rather than a different framework.
Confusing Spring Boot with Spring ('they're the same') — missing auto-configuration, starters, and the embedded server, which are the point of Boot; or believing Boot replaces Spring rather than configures it.
Frame Boot as an opinionated layer ON Spring: auto-configuration (classpath-driven beans), starters (curated dependency sets), embedded server (run with one command), and sensible defaults over XML — while staying Spring underneath, so anything Spring can do, Boot can override.
Interview-ready guide
Interview answer
Spring Boot is an opinionated layer on top of the Spring Framework that auto-configures the application based on the classpath, embeds a web server, and removes XML and boilerplate via sensible defaults — so you can run a production-ready app with one command.
It exists because raw Spring, while powerful, required significant manual configuration and an external servlet container to deploy, which slowed development and made onboarding hard. The pieces I anchor on are auto-configuration, which inspects the classpath and creates beans you'd otherwise write — if Tomcat's present it configures an embedded server, if a DataSource is present it configures one — and you override only what differs.
Starters, which are curated, tested dependency sets that prevent version conflicts. The embedded server, which runs inside the jar so the app is self-contained and runnable with java -jar. And the fact that it's still Spring underneath — every Boot behavior is Spring beans, so I can override any auto-config by defining my own bean, and actuator's /beans endpoint lists what's there.
The tension I'm honest about is convention versus control: the auto-configuration can feel like magic, but every auto-config has a conditional and is overridable, so the control is always there when I need it.
Spring Boot Fundamentals
Direct Answer
Spring Boot is an opinionated layer on top of the Spring Framework that auto-configures the application based on classpath, embeds a web server (Tomcat/Jetty), and removes XML/boilerplate via sensible defaults — so a developer can run a production-ready application with java -jar or a single main method. It exists because the raw Spring Framework, while powerful, required significant manual configuration (XML, then Java config), dependency wiring, and an external servlet container to run; that ceremony slowed development and made onboarding hard. Spring Boot's auto-configuration, starters, and embedded server collapse weeks of plumbing into minutes, while staying 100% Spring under the hood.
Common Mistakes & Pitfalls
Confusing Spring Boot with Spring ('they're the same') — missing auto-configuration, starters, and the embedded server, which are the point of Boot; or believing Boot replaces Spring rather than configures it.
Check your understanding
Answer these without looking back at the article.
- What does @SpringBootApplication combine, and why does one annotation start a whole app?
- How does Spring Boot's auto-configuration decide which beans to create, and how do you override one?
- What is a starter, and how does it prevent dependency version conflicts?
- Why is the embedded server a 12-factor improvement over deploying a WAR to an external Tomcat?
- How can you find out which beans auto-configuration created, and how do you turn one off?
Related interview prep categories
1Looking for a structured roadmap?
Every module on this page is also part of the full Java backend interview track.