Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architecture for Busy Developers

You're reading from   Software Architecture for Busy Developers Talk and act like a software architect in one weekend

Arrow left icon
Product type Paperback
Published in Oct 2021
Publisher Packt
ISBN-13 9781801071598
Length 174 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Stéphane Eyskens Stéphane Eyskens
Author Profile Icon Stéphane Eyskens
Stéphane Eyskens
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Introduction
2. Chapter 1: Introducing Software Architecture FREE CHAPTER 3. Section 2: The Broader Architecture Landscape
4. Chapter 2: Exploring Architecture Frameworks and Methodologies 5. Chapter 3: Understanding ATAM and the Software Quality Attributes 6. Section 3: Software Design Patterns and Architecture Models
7. Chapter 4: Reviewing the Historical Architecture Styles 8. Chapter 5: Design Patterns and Clean Architecture 9. Section 4: Impact of the Cloud on Software Architecture Practices
10. Chapter 6: Impact of the Cloud on the Software Architecture Practice 11. Section 5: Architectural Trends and Summary
12. Chapter 7: Trendy Architectures and Global Summary 13. Other Books You May Enjoy

Introducing architecture styles

Architecture styles are high-level design choices that influence the way applications are designed, built, and hosted. Making such a choice forces you to obey the standard practices that ship with the style in question. Some architecture styles act at a higher level than others.

For example, the three-tier architecture is based on three different layers – presentation, business, and data – all of which are physically separated. In a three-tier architecture, the presentation layer cannot talk directly to the data layer. Network policies should be enforced to prevent such occurrences. As you can see, this type of architecture has an impact, not only on the hosting piece but also on the way you organize the development of the different components. Conversely, the Model View Controller (MVC) pattern is also based on three layers, but all the layers can be deployed to a single server. Here, the physical split is not required. However, going...

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 $19.99/month. Cancel anytime
Banner background image