April 1, 2014

Spring Boot 1.0 released

Pivotal released Spring BootA Java framework for production-ready apps — auto-configuration and embedded servers for microservices. 1.0 on April 1, 2014 — opinionated auto-configuration for Spring apps with embedded servers and starter dependencies.

What it was for

Spring BootSpring BootA Java framework for production-ready apps — auto-configuration and embedded servers for microservices. (`java -jar app.jar`) eliminated XMLExtensible Markup Language — a markup format for structured documents and data exchange. boilerplate: starters bundle dependencies, auto-config wires beans, and Actuator exposes health checks. microservicesAn architecture splitting applications into small independent services — each deployed and scaled separately. teams ship RESTRepresentational State Transfer — a style for web APIs using HTTP methods and resource URLs. APIs and batch jobs without application servers; it became the default way new JavaA portable language running on the JVM — dominant in enterprise servers, Android, and big data. backends start in the 2010s.

Companies

  • Sun Microsystems

Why it's here

Spring BootA Java framework for production-ready apps — auto-configuration and embedded servers for microservices. made Spring as fast to start as RubyA dynamic language emphasizing developer happiness — Rails made it the default for web startups in the 2000s. or NodeNode.js — JavaScript on the server via an event-driven runtime built on V8. microframeworks.

Why it mattered

Embedded Tomcat/Jetty and starter POMs defined the containerless JavaA portable language running on the JVM — dominant in enterprise servers, Android, and big data. deployment model.

What it solved

Spring apps required heavy WAR deployments and pages of XMLExtensible Markup Language — a markup format for structured documents and data exchange. before writing business logic.

Media

  • Spring Boot
    ImageSpring Boot

    Pivotal Software, Apache License 2.0, via Wikimedia Commons

Related