
< session />
Fri, April 30Architecture & Distributed SystemsData & Intelligent SystemsAI-Assisted Software Engineering
Many teams treat a system’s physical architecture and data architecture as separate concerns, even though a system’s data topology can directly influence its architecture, and vice versa. Keeping the two aligned requires a way to describe and govern that relationship as the system changes.
In this session, you will explore how to use the Architecture Definition Language (ADL) alongside agents to describe, validate, and govern a system’s data topologies. You will learn how architecture as code can be used to govern bounded contexts in microservices, ensure proper data partitioning, and govern data access.
What You Will Learn
How to use ADL and agents to describe, validate, and govern data topologies
How to govern bounded contexts and ensure proper data partitioning in microservices
How architecture as code can be used to govern data access
Who Should Attend
Software Architects, Data Architects, Developers, Technical Leads, and practitioners designing or governing data-intensive and microservices-based 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.