
< session />
Thu, April 29Architecture & Distributed SystemsBackend Engineering & Runtimes
When do you need an architecture? How should you iterate on it as a system evolves? How do you create a microservices architecture, and how do you know whether your services are too small? These are common questions, and many of them point to architecture anti-patterns and pitfalls that can lead teams into trouble.
In this session, you will explore common architecture anti-patterns and pitfalls, how they arise, and ways to avoid these architectural traps as you design and evolve software systems.
What You Will Learn
How to recognise common architecture anti-patterns and pitfalls
How to think about architecture as a system evolves
How to avoid common architectural traps, including those associated with microservices
Who Should Attend
Software Architects, Developers, Technical Leads, and practitioners involved in designing and evolving software systems.
< speaker_info />
Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures and other distributed systems in a variety of technologies. 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 free website devoted to helping developers in the journey to becoming a software architect. In addition to hands-on consulting, Mark has authored numerous technical books and videos, including his two latest books Fundamentals of Software Architecture and Software Architecture: The Hard Parts that he co-authored with Neal Ford. Mark has spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics.