Business, society, and technology are changing at an ever-increasing rate, and we technologists constantly create new programming languages, frameworks, platforms, and tools to help us keep up. However, in most cases it is not enough. We must also rethink how we approach the design and architecture of software for the future.
Architectural modularity will be a cornerstone of these software applications. Mark Richards explores the history of architectural modularity, discusses current architecture patterns that support modularity, and explains why architectural modularity is so important (and necessary).
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’s been in the software industry since 1983 and has significant experience and expertise in application, integration, and enterprise architecture. Mark’s the founder of Developertoarchitect.com, a website devoted to helping developers in the journey to software architect. He’s the author of numerous O’Reilly technical books and videos, including several books on microservices, the Software Architecture Fundamentals video series, Enterprise Messaging video series, Java Message Service, second edition, and a contributing author to 97 Things Every Software Architect Should Know. Mark has a master’s degree in computer science and numerous architect and developer certifications from IBM, Sun Microsystems, The Open Group, and Oracle. He’s spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics.
©2017, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org