A JOURNEY INTO DOMAIN DRIVEN DESIGN
Cluj-Napoca, Romania |
18 November 2019
The more we push the boundaries of technology, the more innovative solutions we have to find for the problems emerging along the way, and it’s not a surprise that often we tackle them through software development.
Domain-Driven Design might seem like a complex tool that requires robust domain expertise at first glance, but its applicability can be of great use when trying to discover what are the real problems and to solve them.
Join the conversation on Domain-Driven Design and discover more about how you can analyse, design and programme software in a way that helps you meet the complex business requirements of fluid business model concepts.
DEVELOPER, CONSULTANT, FOUNDER AND LEAD ARCHITECT/DEVELOPER VLINGO/PLATFORM
RETHINKING LEGACY & MONOLITHIC SYSTEMS
Legacy monoliths have generated profit for decades. Gradually the myriad of changes to these revenue generators has led to a paralysing tangle. The recurring plea for help? Teams are demoralised by the mud, and hardware has outpaced software architecture. How can you achieve mobility and relief? Vaughn explores practical steps that can be made toward enterprise modernisation.
ABOUT VAUGHN: Vaughn Vernon is the founder and chief architect of the Vlingo/PLATFORM. A software developer and architect with more than 35 years of experience in a broad range of business domains, Vaughn is a leading expert in Domain-Driven Design (DDD), champion of simplicity and reactive systems. The open-source, DDD-friendly, reactive vlingo/PLATFORM is one example of his commitment to balancing the right technology choices with every essential and unique business vision. He consults on and teaches DDD, and reactive software development, helping teams and organisations realie the potential of business-driven and reactive systems as they transition from technology-driven legacy web implementation approaches, putting a strong emphasis on embracing simplicity whenever possible. Vaughn is the author of three books: Implementing Domain-Driven Design, Domain-Driven Design Distilled, and Reactive Messaging Patterns with the Actor Model, all published by Addison-Wesley.
SENIOR ARCHITECT, ENDAVA
FRAMING PROBLEMS USING UBIQUITOUS LANGUAGE
Why do we build software? To solve problems. What problems are we trying to solve?
Business value is delivered when we solve a problem in the real world, not inside a computer. Domain Experts are the people who know how to solve those problems.
Ubiquitous language is a common, model-based language that is shared by everybody. Through his presentation, Ged explains how it helps us to collaborate closely with Domain Experts and make sure we deliver effective valuable solutions. He also introduces the complementary Problem Frame method. Five common frames that help us to identify, describe and solve the real-world problems within our Business Domains.
ABOUT GED: Ged Byrne has been working as developer and architect for over 20 years. He has been with Endava since 2014 and is currently the Design Authority for Insurance and Finance. He is a big fan of Michael Jackson. Not that one, the other one. He is keen to share some of Jackson’s work and show how it complements Domain-Driven Design.
DESIGN AUTHORITY - ARCHITECTURE, ENDAVA
PRIME DIRECTIVE - THE NON-INTERFERENCE WITH NATURAL EVOLUTION OF OTHERS
Dan North says that "Even with the best intentions, entropy and complexity are a fact of life in growing applications." This is no news to us because in the heath of deadlines or simply by being unaware, we all can make decisions that blur the boundaries or complicate the interconnections between our systems. Soon the trade-offs we've made become our anchors, slowing us down. In response, DDD advocates that in order to make the right calls, we need a realistic, large-scale view of the model extending across our codebase(s).
Through this talk, Dan will share with us how you can identify and measure the blurred edges of our bounded contexts and act when they bleed into each other.
ABOUT DAN: Dan is a pure technology enthusiast. No matter if we talk about architecture, design, Big Data, Continuous Delivery, user experience or any other aspect of technology, he is very involved and passionate. Although he calls himself a true engineer, therefore a technical person, Dan pays a lot of attention to what makes a great team and what are the best practices, being a dedicated advocate of the agile mindset.
Johan Peeters is an independent security architect. Besides commercial consulting and bespoke development, he also teaches software security at Erasmus University College Brussels. He is the founder of secappdev.org.
IDENTITY IN APPLICATION SECURITY
Identity is who you are and determines what you are entitled to. It holds you accountable for your actions. Thus identity must be revealed for access control and auditability. But prying eyes also watch us for other, less savory, reasons. How then to effectively use identity in application architectures to afford appropriate security guarantees and avoid abuse? If there was previously little incentive to consider user privacy, GDPR has put it on the map for anyone practicing security by compliance. I also argue that privacy can and should be a competitive advantage.
The popular OAuth standard puts end users in control of their digital resources in the cloud. Digital identity data is considered a special case important enough to deserve an extension in the form of OpenID Connect. Despite their popularity, there seem to be a lot of misunderstandings and frustrated expectations regarding these standards. Notably, they offer Discretionary Access Control, whereas most enterprises require Mandatory Access Control, a point not lost on authorization server vendors who have jumped into the breach to supplement OAuth and OpenID Connect specifications with capabilities to meet this need.