Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Software Architecture with Spring 5.0

You're reading from   Software Architecture with Spring 5.0 Design and architect highly scalable, robust, and high-performance Java applications

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781788992992
Length 372 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
 Enríquez Enríquez
Author Profile Icon Enríquez
Enríquez
 Salazar Salazar
Author Profile Icon Salazar
Salazar
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
1. Software Architecture Today 2. Software Architecture Dimensions FREE CHAPTER 3. Spring Projects 4. Client-Server Architectures 5. Model-View-Controller Architectures 6. Event-Driven Architectures 7. Pipe-and-Filter Architectures 8. Microservices 9. Serverless Architectures 10. Containerizing Your Applications 11. DevOps and Release Management 12. Monitoring 13. Security 14. High Performance 1. Other Books You May Enjoy Index

Silos


Some years ago, the software industry used the waterfall model to manage the systems development lifecycle (SDLC). The waterfall model includes many phases, such as gathering requirements, designing a solution, writing the code, verifying that the code meets the user requirements, and finally, delivering the product. In order to work on each of these phases, different teams and roles were created, including analysts, developers, software architects, QA teams, operations people, project managers, and so on. Each one of these roles were responsible for producing output and delivering it to the next team.

The steps needed to create a software system using the waterfall model are as follows:

  1. Analysts gather the software requirements
  2. Software architects review the requirements carefully and expand the documents with information about the tools and technologies that will be used, modules that have to be written to create the system, diagrams showing how the components are going to be connected...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images