It’s a Feature, Not a Bug: A Step-by-step Guide to Architectural Decisions This function will allow you to assess the expected effort for evolving a system and use it as a heuristic for optimizing architectural design decisions. Next, we will combine the existing knowledge into a coherent model - a simple function for evaluating a system’s decomposition into components. We will start by taking a journey through time, and explore the different models of evaluating coupling. Can we do better? What if there is a better way to handle coupling in distributed systems? Or even, what if instead of fighting coupling, we can use it as a heuristic for designing systems that are actually evolvable and maintainable? That’s exactly what you will learn in this session: what coupling is, and how you can use it as a design tool. But what results are we getting by following this reasoning? - Instead of the promised land of evolvable systems, many such “decouple everything” endeavors lead straight into the chains of distributed monoliths. Hence, we aim to break systems apart into the smallest services possible, in the ever-lasting quest of decoupling everything. His professional aspiration is to raise the bar of the software industry by helping developers become better at and care more about their craft.ĪWe are used to treating coupling as the necessary evil. Sandro is internationally renowned by his work on evolving and spreading Software Craftsmanship and is frequently invited to speak in many conferences around the world. Sandro has a lot of experience in bringing the Software Craftsmanship ideology and Extreme Programming practices to organisations of all sizes. During his career Sandro had the opportunity to work in a good variety of projects, with different languages, technologies, and across many different industries. He has worked for startups, software houses, product companies, international consultancy companies, and investment banks. Sandro has been coding since a very young age but only started his professional career in 1996. Software craftsman, author, and founder of the London Software Craftsmanship Community (LSCC). Sandro Mancuso Author of the book "The Software Craftsman: Professionalism, Pragmatism, Pride" Mark has been a regular confe has spoken at hundreds of conferences and user groups around the world on a variety of enterprise-related technical topics. Mark has a master’s degree in computer science and numerous architect and developer certifications from IBM, Sun, The Open Group, and Oracle. He is the author of numerous technical books and videos from O'Reilly, including several books on Microservices, the Software Architecture Fundamentals video series, Enterprise Messaging video series, Java Message Service, 2nd Edition, and a contributing author to 97 Things Every Software Architect Should Know. Mark is the founder of, a free resource website devoted to helping developers in the journey to software architect. He has been in the software industry since 1983 and has significant experience and expertise in application, integration, and enterprise architecture. 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. Mark Richards Co-author of the book "Fundamentals of Software Architecture" His primary consulting focus is the design and construction of large-scale enterprise applications. His topics include software architecture, continuous delivery, functional programming, cutting edge software innovations, and includes a business-focused book and video in improving technical presentations. Neal authored magazine articles and authored many books including "Building Evolutionary Architectures: Support Constant Change", "Functional Thinking: Paradigm Over Syntax", "The Productive Programmer (Theory in Practice (O'Reilly)", "Fundamentals of software architecture", "Software Architecture: the hard parts", "Software Architecture Metrics" and many others, dozens of video presentations, and spoken at hundreds of developers conferences worldwide. He is an internationally recognized expert on software development and delivery, especially in the intersection of agile engineering techniques and software architecture. Before joining ThoughtWorks, Neal was the Chief Technology Officer at The DSW Group, Ltd. Neal is Director, Software Architect, and Meme Wrangler at ThoughtWorks. Neal Ford Software Architect & Director at ThoughWorks
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |