Software Architecture Patterns
Mark Richards
Abstract
Mark Richards
Abstract
Just as developers use design patterns in software development, architects use well-defined architecture patterns to define the characteristics and shape of the architecture. Using the wrong architecture pattern (or no pattern at all) can sometimes be a very costly mistake resulting in an architecture that doesn't work. It is therefore vital that architects are aware of and understand the various architecture patterns available. During this webcast I will discuss several common architecture patterns, including the traditional layered architecture, microservices architecture, space-based architecture, event-driven architecture, and microkernel architecture. Along the way I will show real-world examples to demonstrate how the patterns work, as well as describe the pros and cons of each pattern. I will also discuss how requirements and operational aspects can drive which patterns to use. Using the right architecture pattern for your system is critical, because as we all know, once in place the architecture is very hard to change.
OpenAlex reports 143 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Just as developers use design patterns in software development, architects use well-defined architecture patterns to define the characteristics and shape of the architecture. Using the wrong architecture pattern (or no pattern at all) can sometimes be a very costly mistake resulting in an architecture that doesn't work. It is therefore vital that architects are aware of and understand the various architecture patterns available. During this webcast I will discuss several common architecture patterns, including the traditional layered architecture, microservices architecture, space-based architecture, event-driven architecture, and microkernel architecture. Along the way I will show real-world examples to demonstrate how the patterns work, as well as describe the pros and cons of each pattern. I will also discuss how requirements and operational aspects can drive which patterns to use. Using the right architecture pattern for your system is critical, because as we all know, once in place the architecture is very hard to change.
Key concepts: Space-based architecture, Architecture, Applications architecture, Reference architecture, Solution architecture, Enterprise architecture framework, Database-centric architecture, Computer science