When do you need an architecture? How specific should my contracts be? Should I make everything a microservice? Are my services too small? If you are wondering about these questions, you’re not alone. It turns out these questions all relate to architecture anti-patterns and pitfalls - things we do that get us into trouble. In this lively session, Mark Richards talks about some of the common architecture anti-patterns and pitfalls you’re likely to encounter, and ways to avoid these common architectural traps.
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 DeveloperToArchit...