Focus

Spring Boot

Spring Boot simplifies the development of production-ready Java applications and provides many of the building blocks needed for configuration, operations, and integration.
Learn more Get in touch

Understand Spring Boot and use it effectively

Spring Boot is an established framework for building Java applications. Based on the Spring ecosystem, it reduces the effort required to set up and operate applications through auto-configuration, dependency management, and integrated components.

These abstractions save development teams a considerable amount of work. At the same time, understanding what happens under the hood helps teams make better decisions about transactions, testing, observability, security, and deployment. INNOQ brings this experience into its Software Architecture and Development work.

What Is the Magic Behind Spring Boot? takes a closer look at how the framework works. Testing Spring Boot Applications explores different testing strategies. Further resources cover topics ranging from Spring Boot Actuator and Spring AI to transactions and running Java applications in containers.

On this page, you will find articles, podcasts, talks, and further resources on Spring Boot and Java application development.

Our Services

We advise honestly, think innovatively and love to build. The result: successful software solutions, infrastructures and business models.

Learn more

Blog Posts

Blog Post

Why not scatter @Transactional everywhere?

Fabian Walther Senior Consultant
Blog Post

Spring Boot Actuator Endpoints

What does ‘production-ready’ actually mean?

Michael Vitz Senior Consultant
Blog Post

Use webjars-locator-lite with internal WebJars

Michael Vitz Senior Consultant
Blog Post

Rate Limiting with Spring Boot, Bucket4j, and Redis

Martin Weck Senior Consultant
Blog Post

Rate Limiting with Spring Boot

Martin Weck Senior Consultant
Blog Post

Containers for tests and local development with Spring Boot 3.1

Spring Boot test containers & Docker Compose

Michael Vitz Senior Consultant

Talks

Talk
Talk

Spring Boot Test - A look behind the curtain

INNOQ Technology Night Rhein-Main (April) / 20:00 - 21:00

Talk
Talk

Spring Boot Test - A look behind the curtain

Voxxed Days Zürich

Talk
Talk
Slides available

Getting your application production-ready with Actuator

Spring I/O 2025 / 10:00 - 10:50

Case Studies

Case Study

HILFE FÜR JUNGS (“Help for Boys”): Reliable software for mobile consultations

Read case study

Popular Topics

Frequently Asked Questions

Do you have questions about Software Architecture and Development? Here you will find answers to questions we are frequently asked.

When does a software project need architectural change rather than just new features?

If changes regularly cause unexpected side effects, releases become increasingly risky, or teams spend more time coordinating and maintaining systems than evolving them, the underlying issue is often architectural. That is when it makes sense to examine the system structure itself and identify which dependencies, boundaries, or technology decisions are slowing development down.

INNOQ supports teams both in assessing existing systems and in evolving them: Software Architecture and Development and Software Reviews

When is custom software a better choice than off-the-shelf software?

Custom software makes sense when core business processes or products are too specific to be supported effectively by standard software, or when extensive customization would be required over the long term. It is particularly relevant when software itself provides competitive differentiation or forms a key part of the business model.

INNOQ develops custom software from domain design and architecture through implementation and operation, while integrating it into existing system landscapes: Software Architecture and Development

How do you choose the right technology stack for a software project?

The right technology depends on the context. Programming languages, frameworks, databases, and infrastructure should not be chosen because they are new or popular, but because they fit the system’s requirements, the team’s capabilities, and the long-term dependencies they create. Operations, maintainability, and future evolution should also be considered from the start.

INNOQ is vendor-independent and evaluates both existing and new technologies against business requirements, team structures, and strategic goals: Software Architecture and Development

How should software architecture and development work together?

Architecture works best when it is not separated from implementation. Architectural decisions need to prove themselves in real development work and should be revisited as requirements evolve. At the same time, development teams need clear guidance on system boundaries, interfaces, technology choices, and quality goals.

At INNOQ, architecture and development therefore go hand in hand. Our architects are experienced developers themselves and have worked with software throughout different stages of its lifecycle: Software Architecture and Development

How does INNOQ support development teams without creating long-term dependency?

INNOQ can take on different roles depending on the situation: providing individual architects or developers, working alongside existing teams, or taking responsibility for complete teams and applications. Knowledge transfer is part of the engagement. Architectural decisions are documented transparently, and knowledge is shared throughout the project so that teams can continue developing and operating their systems independently.

The explicit goal is to strengthen internal capabilities rather than create long-term dependence on external support: Software Architecture and Development