Web API Design in the Face of Complex Distributed Architectures
Season 2, Ep. 7
Matt McLarty (@mattmclartybc) is the Global Field CTO at MuleSoft. He works closely with organizations to define digital strategies, as well as design and implement enterprise-grade API and microservices solutions. An experienced software architect, Matt has worked extensively in the field of integration and real-time data distribution. He is the co-author of the O'Reilly books Microservice Architecture and Securing Microservice APIs, co-author of the ebook Develop a Winning API Product Strategy, co-author of the HBR article “APIs Aren’t Just for Tech Companies” and co-host of the APIs Unplugged podcast.
The CQRS and Event Sourcing Long Position
Season 3, Ep. 2
Vaughn and Greg discuss a lot of topics!CQRSEvent SourcingThe CQRS and Event Sourcing book Greg was completing at the time of this interviewEventStore and specific unique featuresEventStore Clustering complexity PAXOS (defined by Leslie Lamport in 1998)Data Mesh "The Old New Thing" UDP multicast for trading messagingHis upcoming next bookHis current work challengesGregory Young coined the term “CQRS” (Command Query Responsibility Segregation) and it was instantly picked up by the community who have elaborated upon it ever since. He is the founder and creator of Event Store. He has 15+ years of varied experience in computer science from embedded operating systems to business systems and he brings a pragmatic and often times unusual viewpoint to discussions.
Writing Patterns for API Design
Season 3, Ep. 1
With several great books on API design already on our shelves, this one stands out as a hefty pattern language and catalog for API designers. It's chock full of about everything you could need to design an industrial-strength API. Our discussion steps through the pattern writing process, including working as a team of five industry and academic professionals. Learn insights from one of the book's co-authors and pattern writers—a software industry practitioner—including his favorite and most challenging pattern in the book.Daniel Lübke is a Software and Business Process Architect working at Digital Solution Architecture GmbH in Hanover, Germany. He received his PhD in Software Engineering in 2007. Since then he is working as a consulting and coding software architect in client projects. He is one of the contributors to the API Pattern collection, author and editor of several books and other publications, and is frequently sharing his experience in conference talks and lectures.
Viewpoints: Software Development's Future
Season 2, Ep. 8
What has changed in the software industry from 20 years ago and five years ago, and what might trends indicate about the future? Consider what developers use over and over again, year after year: programming languages, databases, testing, deployment, and operations. How can we improve developer experience with advanced programming language features, atomic and long-running transactions, and DevOps/SRE? Gazing into the future possibilities with Lev and Vaughn is fun and engaging.