Mark Richards explores the history and patterns of architectural modularity, and explains why modularity is so important.
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 in J2EE and other technologies. He has been involved in the software industry since 1983, and has significant experience and expertise in application, integration, and enterprise architecture. Mark served as the President of the New England Java Users Group from 1999 thru 2003. He is the author of numerous technical books and videos, including "Software Architecture Fundamentals" (O’Reilly video), "Enterprise Messaging" (O’Reilly video), "Java Message Service 2nd Edition" (O’Reilly), and 97 Thinks Every Software Architect Should Know (O'Reilly). Mark has a masters degree in computer science and numerous architect and developer certifications from IBM, Sun, The Open Group, and BEA. He is a regular conference speaker at the No Fluff Just Stuff (NFJS) Symposium Series, and has spoken at over 100 conferences and user groups around the world on a variety of enterprise-related technical topics.When he is not working Mark can usually be found hiking in the White Mountains or along the Appalachian Trail.
Mark Richards offers a glimpse of what software architecture will look like in the future, and he shares the things software architects will need to focus on in the years ahead.
Mark Richards discusses the factors that have enabled the evolution of software architecture over the past three decades and explores what the future of software architecture might look like.
Author Mark Richards walks you through the 10 most common microservice anti-patterns and pitfalls, and provides solutions for avoiding them.
Learn the core differences between microservices and SOA so you can make an informed choice when determining which is best for your particular situation.
Mark Richards focuses on the essential soft skills of architecture, including working with architecture teams, leadership skills, leveraging checklists, negotiation skills, and facilitation skills.
Using the wrong architecture pattern (or no pattern at all) can be a very costly mistake.
Take a deep dive into several common software architecture patterns