Add Dot

Vaughn and Asanka—WSO2's CTO— discuss a relatively radical and fresh approach to cloud applications and services development. The tools include the domain-driven Cell-based Architecture, the Ballerina programming language, and the Choreo cloud platform. This purpose-built trio is composed as one powerful offering to give software engineers the ability to focus their efforts on delivering cloud-native applications and services. Of course, engineers are not required to use the Ballerina programming language. They may use Java and any other choice of language. Yet, those looking for a practical approach to functional programming that offers asynchronicity and handles service integrations well, Ballerina is a language worth trying. Together, this architecture-language-platform trio deserves consideration for use in your future enterprise.

Asanka Abeysinghe, WSO2's CTO, is a technology visionary with over 20 years of experience designing and implementing scalable distributed systems, microservices, and business integration solutions. He advances WSO2's corporate reference architecture, collaborates with customers and industry analysts, and drives the company's technology mission. Asanka is also a contributor to the Apache Software Foundation and a sought-after speaker at global events.

Hosted on Acast. See acast.com/privacy for more information.

Vaughn Vernon has a conversation with Alfredo Muñoz regarding the transformation and modernization within banks, why it's so urgently needed, and how efforts can be successful. Their discussion encompasses BIAN, Domain-Driven Design, Data Mesh, and why focusing on business capabilities as business, service, events, and data domains is critical. We address why banks are so resistant to change but why they must learn a new mindset in order to both survive and flourish in the age of cloud and digital banks. For example, a bank transaction that has 1,000 COBOL calls will never work in the cloud, nor will a transaction that makes 100 API calls. How can new technologies and approaches to software development help banks, insurance, airlines, telecom, and other industries that heavily rely on mainframe power successfully switch out of the old status quo?

Alfredo is an Enterprise Architect, and Banking Transformation Expert with more than 25 years of experience in large scale banking transformations in Europe, Asia and Latam, always involving first tier banks

He currently works in the Global Center of Excellence for Banking and Financial Market at IBM

During the past years he has developed the methodology for the modernization of corebanking systems, including the adoption cloud infrastructure in coexistence with legacy systems, the BIAN Industry Standards, the industrialization and standardization of the design and development processes and the use of low code development frameworks with the primary objective to deliver transformation at scale, as required for large Financial Institutions.

He has authored leading points of view, methods and assets on core systems transformation to Cloud.

https://www.fintechna.com/authors/alfredo-muñoz-ríos/

https://www.linkedin.com/in/alfredomunoz/

Hosted on Acast. See acast.com/privacy for more information.

Hosted on Acast. See acast.com/privacy for more information.

Mark Wardle, Chief Clinical Information Officer, and Vaughn Vernon discuss the intersection of healthcare and technology. Mark emphasizes the need for technology to improve patient care and the challenges of integrating digital systems in healthcare.

Mark also highlights the importance of Domain-Driven Design in healthcare, as it allows for a more patient-centered approach and better communication between clinicians and patients. He discusses the limitations of current electronic health records and the need for tools that support continuity of care. Mark believes that technology should be used to enhance the human connection in healthcare and improve patient outcomes.

Mark discusses the application of Domain-Driven Design (DDD) in healthcare and its potential to address the complexity and challenges in the industry. He emphasizes the need to break down healthcare systems into modular components and build them based on a shared understanding of the domain. Wardle highlights the importance of technical standards, interoperability, and the use of common models to decouple systems and improve integration. He also discusses the role of open source in healthcare and the potential for disruptive innovation. Wardle envisions a future where technology enables faster iteration, better orchestration of clinical pathways, and improved decision-making in healthcare.

• Technology has the potential to greatly improve patient care in healthcare.
• DDD is crucial in healthcare to create a patient-centered approach and improve communication between clinicians and patients.
• Current electronic health records are often not user-friendly and do not support continuity of care.
• Technology should be used to enhance the human connection in healthcare and improve patient outcomes. Domain-Driven Design can help address the complexity and challenges in healthcare by breaking down systems into modular components and building them based on a shared understanding of the domain.
• Technical standards and interoperability are crucial for decoupling systems and improving integration in healthcare.
• Open source has the potential to disrupt the healthcare industry by providing foundational building blocks and higher-value tools.
• Improving orchestration of clinical pathways and decision-making in healthcare can be achieved through the use of technology and data-driven approaches.
• Faster iteration, better integration, and improved decision-making can lead to a learning health and care system that continuously improves patient outcomes.

Mark is a Consultant Neurologist and Chief Clinical Information Officer in the UK. He is also a keen software developer, building a range of clinician and patient-facing applications, most recently preferring to work in Clojure and ClojureScript. He thinks digital technologies should play a fundamental role in improving and transforming health and care with Domain-Driven Design playing a key role in unbundling the electronic patient record, and turning what we think of as health applications inside-out.

Hosted on Acast. See acast.com/privacy for more information.

Summary

In this podcast episode, Vaughn and Mark Planagumà discuss various aspects of data strategies and the implementation of Data Mesh. Mark shares his background in data engineering and his experience in building data platforms for different companies. They explore the use of Domain-Driven Design in data strategies and the role of contracts in data architecture. Mark explains the concept of Data Mesh and how it shifts the focus from centralized data warehouses to domain-driven, decentralized data products. They also discuss the implementation of data governance and automation, the influence of operational software architectures on data strategies, and the design of a semantic layer in a Data Mesh. The conversation explores the maturity in operational and analytical architecture, the influence of Domain-Driven Design on Data Mesh, the tooling required for Data Mesh, the future of analytics, challenges with AI and metadata, and where to learn more about Data Mesh.

Takeaways

• Domain-Driven Design can be applied to data strategies to organize data by domains and enable domain owners to take responsibility for their data.
• Data Mesh is a paradigm shift that emphasizes decentralized, domain-driven data products instead of centralized data warehouses.
• Contracts play a crucial role in data architecture by defining the metadata and governance rules for data products.
• Implementing data governance and automation can help ensure the discoverability, accessibility, and reusability of data in a data mesh.
• Organizational structure needs to align with the principles of Data Mesh, with domain-driven teams owning and managing their data.
• A semantic layer in a Data Mesh helps organize and aggregate data products by domains, making it easier to discover and consume data.
• Operational software architectures can influence data strategies by providing the infrastructure and tooling for data products in a Data Mesh. Data is typically behind operational and application maturity, but Data Mesh is emerging to bridge the gap.
• Domain-Driven Design plays a significant role in shaping Data Mesh and enabling interoperability between operational and analytical systems.
• Existing tools like lake houses and data warehousing can be leveraged to support Data Mesh, focusing on creating interoperable data products.
• The future of analytics lies in improving data quality, metadata management, and leveraging AI to interact with data in a more natural and business-focused way.

Chapters

Please note these are approximate locations! We are trying new tools and hope you find this helpful.

00:00 Introduction and Background

05:32 Using Domain-Driven Design with Data Strategies

09:20 Understanding Data Mesh

11:18 The Role of Contracts in Data Architecture

28:21 Influencing Organizational Structure for Data Mesh

34:00 Semantic Layer Design in Data Mesh

37:36 Impact of Operational Software Architectures on Data Strategies

37:52 Maturity in Operational and Analytical Architecture

42:30 Domain-Driven Design and Data Mesh

47:08 Tooling for Data Mesh

53:29 The Future of Analytics

01:01:08 Challenges with AI and Metadata

01:09:36 Learning More about Data Mesh

Marc Planagumà, is a native of Olot (Catalonia) with degrees in Telecommunications from UPC. He is a prominent figure in data engineering and governance.

He serves as the Data Platform & Governance Director at Adevinta Spain, where he has spearheaded the development and implementation of Lakehouse architecture and Data Mesh paradigm, focusing on scalability, autonomy, and effective governance by design.

Hosted on Acast. See acast.com/privacy for more information.