Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Spring System Design in Practice
  • Table Of Contents Toc
Spring System Design in Practice

Spring System Design in Practice

By : Rodrigo Santiago
close
close
Spring System Design in Practice

Spring System Design in Practice

By: Rodrigo Santiago

Overview of this book

Software system design goes beyond just writing code—it requires a structured approach to translating real-world requirements into scalable, maintainable solutions. With Rodrigo Santiago’s hands-on mentoring style and Java Spring expertise, he makes system design accessible to developers at all levels. Spring System Design in Practice guides you through building robust software architectures with Spring. From breaking down complex business needs into actionable use cases to implementing services using Spring Boot, this book equips you with the tools and best practices needed for developing secure, high-performance applications. You'll explore inter-service communication, security, and aspect-oriented programming to streamline development. Covering microservices architecture, the book demonstrates how to create self-configuring, resilient, and event-driven services that integrate seamlessly into the cloud. Through hands-on experience, you'll apply best practices to enhance reliability and scalability while tackling complex challenges such as state management, resilience patterns, concurrency issues, and distributed transactions—including bottlenecks related to asynchronous and reactive programming.By the end of this book, you'll have the confidence to analyze system requirements and design well-structured, scalable architectures.
Table of Contents (19 chapters)
close
close
1
Part 1: Foundations for System Design
6
Part 2: Designing Great Spring Services
10
Part 3: Security, Performance, and Scalability
14
Part 4: Orchestrating Resilient Services

Sorting Complex Requirements into Features, Use Cases, and Stories

In this chapter, we will continue our conversation about how to structure strong requirements. In the previous chapter, we created high-level requirements. Although useful for setting the direction of the products we are going to create, they are vague. In other words, they do not tell the whole story. They lack details that would allow us to start writing our software. If you have too many details at that phase, you have done it wrong.

In this chapter, we will look at the following topics:

  • Naming the distinct features of your product
  • Identifying actors, events, life cycles, stages, types, levels, and loops
  • Creating user journeys, use cases, and stories
  • Structuring the final business requirements document
  • Which of these artifacts should come first?
  • Scaling results with long-term business requirements

If high-level requirements are the “bones” of a system development...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Spring System Design in Practice
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon