Understanding Reactive Architecture
The term “reactive architecture” is quickly becoming a common entry on most buzzword bingo cards. But what does this term really mean? In this session you will learn what it means for an architecture to be reactive as well as the differences between reactive programming and reactive architecture. Using the reactive manifesto as a guide, I will cover some architecture techniques for making architectures reactive, how to navigate around the reactive product space, and how to avoid the hype around reactive architecture.
Agenda TBD
About Mark Richards
Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures, service-oriented architectures, and distributed systems. He has been in the software industry since 1983 and has significant experience and expertise in application, integration, and enterprise architecture. Mark is the founder of DeveloperToArchitect.com, a website devoted to helping developers in the journey to software architect. He is the author of numerous technical books and videos, including the recently published Fundamentals of Software Architecture, Microservices AntiPatterns and Pitfalls, Microservices vs. SOA, the Software Architecture Fundamentals video series, The Enterprise Messaging video series, Java Message Service, 2nd Edition, and contributing author to 97 Things Every Software Architect Should Know. Mark has a master’s degree in computer science and is a regular conference speaker at the No Fluff Just Stuff (NFJS) Symposium Series. He has spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics.
More About Mark »