In this episode, Markus talks to Rebecca Wirfs-Brock on what she has learned from architecture reviews. This is a very complement to the earlier episode on architecture evaluation.

In this episode we talk with Klaus Marquardt about building systems out of plugins. After briefly introducing the concept of a plugin in contrast to modules and related software engineering concepts, we discuss different views on plugins and different ways of working with plugins for developing software. We are looking at plugins for embedded systems as well as large business systems, at how plugins change the working mode and team organization, and discuss the possibilities of why and when to use plugins for implementing software systems.

In this episode we discuss with Randy Shoup, Distinguished Architect at eBay, about architectural pinciples and patterns used for building the highly scalable eBay infrastructure. The discussion is structured into four main ideas: partition everything, use asynchrony everywhere, automate everything, and design the system keeping in mind that everything fails at some point in a large distributed system.

During Evolution of a software system, it becomes more and more difficult to understand the originally planned software architecture. Often an architectural degeneration happens because of various reasons during the development phases. In this session we will be looking how to avoid such architectural decay and degeneration and how continuous monitoring can improve the situation (and avoid architectural violations). In addition we will look at "refactoring in the large" and how refactoring can be simulated. A new family of "lint like tools for software architectures" is currently emerging in the marketplace I will show some examples and how they scale and support you in real world projects.

This is a discussion with Eoin Woods about his collection of top 10 software architecture mistakes. Looking at things that don't work is always a good way to learn what you should actually do.

This is another episode recorded at OOP 2009, thanks to SIGS Datacom and programme chair Frances Paulisch for making this possible. Here is the abstract from the conference program: Many software systems have fragile architectures that are based on brittle assumptions or rigid architectures that reduce options and make change difficult. On the one hand, an architecture needs to be fit for the present day, suitable for immediate use, and on the other it needs to accommodate the future, absorbing reasonable uncertainty. However, an approach that is overly focused on today's needs and nothing more can create an inflexible architecture. An approach that becomes obsessed with possible future changes creates an overly complex architecture that is unfit for both today's and tomorrow's needs. Both approaches encourage an early descent into legacy for a system. The considerations presented in this talk reflect an approach that is more about thinking in the continuous present tense than just the present or the future tense. This includes principles from lean thinking, practices common in agile processes and techniques for loosely coupled design.

This time we have John Wiegand on the mic for an episode on architectures and agile software development. We talk about the role of architectures in an agile world and why architectures change and need to change over time. We discuss the characteristics of those living architectures, using the Eclipse and the Jazz projects as examples, and the surrounding development methods for such environments.

In this episode, Robert talks with Nati Shalom about the emergence of large-system architectures consisting of a grid of high-memory nodes.

Micro services is an emerging trend in software architecture that focuses on small, lightweight applications as a means to avoid large, unmaintainable, monolithic systems. This approach allows for individual technology stacks for each component and more resilient systems. Micro services uses well-known communication schemes such as REST but also require new technologies for the implementation. […]

Gernot Starke talks about arc42: an open-source set of templates he developed to document software architecture based on his practical experience with real projects. Also Gernot and host Eberhard then discuss how documenting architecture fits into agile processes and how to find the right amount of documentation for a system. They walk through the different parts of the arc42 templates covering requirements and the context of the system and the solution structure, including building blocks, runtime, and deployment. They discuss tooling, versioning, testing documentation, and how to keep documentation up to date.

Mike Barker talks with Sven Johann about the architecture of the LMAX system. LMAX is a low-latency, high-throughput trading platform. Their discussion begins with what LMAX does; the origins of LMAX; and extreme performance requirements faced by LMAX. They then delve into systems that LMAX communicates with; LMAX users; the two main components of the system (broker and exchange); Mechanical Sympathy as an architectural driver; message flow using the Disruptor library; and lock-free algorithms. Mike and Sven wrap up by discussing how a well modeled domain model can improve the performance of any system; automated (performance) tests; continuous delivery; and measuring response times.

Bryan Reinero talks with Gregor Hohpe about IT Transformation, the process by which organizations adapt and reorganize themselves in response to evolution and how the Enterprise Architect leads that transformation.

Travis Kimmel and Kevin Goldsmith discuss the correspondence between organizational design and software architecture. Their conversation covers: what Conway’s Law is; Kevin’s experiences in different organizational structures (e.g., Avvo, Spotify, Adobe, and Microsoft) and how those structures influenced the software architecture; what the “Reverse Conway Maneuver” is and how organizations can leverage it; how organizations can evolve existing architectures.

Edaena Salinas talks with Stephen Ewen about streaming architecture. Stephen is one of the original creators of Apache Flink. Topics discussed: stream processing vs batch processing, architecture components of stream architectures, Apache Flink...

Jay Kreps, CEO of Confluent, talks with Robert Blumen about how an enterprise integration architecture organized around a Kafka event log simplifies integration and enables rich forms of data sharing. #podcast #seradio #ieeecs #ComputerSociety

Barry O’Reilly of Black Tulip Technology discusses Antifragile Architecture, an approach for designing systems that actually improve in the face of complexity and disorder.

Tim Sneath, product management for Flutter and Dart at Google discusses what Flutter is, why it was created, where Dart came from, what the different layers of Flutter are, why it is so popular and why it makes a developers life much easier.

Michael L. Perry discusses his recently published book, The Art of Immutable Architecture, distinguishing immutable architecture from other approaches and, using familiar examples such as git and blockchain, addresses some possible misunderstandings...

Randy Shoup of eBay discusses the evolution of eBay's tech stack. SE Radio host Jeremy Jung speaks with Shoup about eBay's origins as a single C++ class with an Oracle database, a five-year migration to multiple Java services, sharing a database...

Ipek Ozkaya, Principal Researcher and Technical Director of the Engineering Intelligent Software Systems group at the Software Engineering Institute, Carnegie Mellon, discusses generative AI for Software Architecture with SE Radio host Priyanka Raghavan. The episode delves into fundamental definitions of software architecture and explores use cases in which gen AI can enhance architecture activities. The conversation spans from straightforward to challenging scenarios and highlights examples of relevant tooling. The episode concludes with insights on verifying the correctness of output for software architecture prompts and future trends in this domain. Brought to you by IEEE Computer Society and IEEE Software magazine.

Stevie Caldwell, Senior Engineering Technical Lead at Fairwinds, joins host Priyanka Raghavan to discuss zero-trust network reference architecture. The episode begins with high-level definitions of zero-trust architecture, zero-trust reference architecture, and the pillars of Zero Trust. Stevie describes four open-source implementations of the Zero Trust Reference Architecture: Emissary Ingress, Cert Manager, LinkerD, and the Policy Engine Polaris. Each component is explored to help clarify their roles in the Zero Trust journey. The episode concludes with a look at the future direction of Zero Trust Network Architecture.

This episode is sponsored by QA Wolf.

Nick Tune and Jean-Georges Perrin join host Giovanni Asproni to talk about their proposed approach to modernizing legacy systems. The episode starts with some high-level perspective to set context for the approach described in their book, Architecture Modernization (Manning, 2024). From there, the discussion turns to important details, including criteria for deciding which aspects to revisit; some of the activities, processes, and tools; and the importance of data engineering in modernization efforts. Nick and Jean-Georges describe how to successfully implement an architecture-modernization effort, and how to fit that work with the teams' other priorities. The episode finishes with some warnings about the typical risks associated with modernizing a legacy system, and suggestions on how to mitigate them.

This episode is sponsored by QA Wolf.

William Ulrich and Neal McWhorter, authors of Business Architecture: The Art and Practice of Business Transformation, cover the basics and discuss the role of business architecture in a changing market landscape.

William Ulrich and Neal McWhorter, authors of Business Architecture: The Art and Practice of Business Transformation, discuss why billions of IT investment dollars are wasted, and how to stop the bleeding.

William Ulrich and Neal McWhorter, authors of Business Architecture: The Art and Practice of Business Transformation, discuss why the IT and business sides of many organizations can't play nice.

William Ulrich and Neal McWhorter, authors of Business Architecture: The Art and Practice of Business Transformation, discuss how IT architects and business architects can work together to get the ship back on course and keep it there.

Two architects, Dr. Helen Sun of Oracle, and Dr. Karine Ishkhanova with TFA Wise Applications, Inc., describe their career paths and what drew them to the their respective roles.

Dr. Helen Sun of Oracle, and Dr. Karine Ishkhanova with TFA Wise Applications, Inc., discuss the role of gender in IT and offer career advice to women interested in IT architect careers.

Pete Farkas, Deepak Arora, and Derek Sharpe talk about the mission and focus of Oracle's Fusion Middleware A-Team.

Pete Farkas, Deepak Arora, and Derek Sharpe discuss the most common problems Oracle Fusion Middleware A-Team members encounter in the field.

Pete Farkas, Deepak Arora, and Derek Sharpe describe the interaction between Oracle Fusion Middleware A-Team and product teams, and the hazards of field assignments.

Are reference architectures blueprints to be followed to the letter, or adaptable guidelines? A community panel discussion.

Is there a problem with reference architectures? Or is the problem in how people use them? The panel discussion continues.

The panel wraps up the discussion with a look at the relationship between reference architectures, reuse, and standards.

What happens to architecture in the rush to deliver solutions? Community members share their opinions in this roundtable discussion.

Cloud computing may be a new take on not-so-new concepts, but getting it right still requires an architectural approach. The community panel weighs in.

Experts Eric Stephens and Tim Hall discussion why it's important to revived the dormant conversation about IT governance.

Balancing functional, technical, operational requirements to meet the challenge of defining appropriate governance "guardrails."

Bringing IT architecture out of the ivory tower to make governance a less intimidating, more collaborative process.

A panel of Oracle ADF Mobile experts discusses the relative merits of the Web, Native, and Hybrid mobile architectures.

The panel of Oracle ADF Mobile experts discusses the challenges of designing and developing mobile apps for the enterprise.

The panel of Oracle ADF Mobile experts looks at the most important considerations for architects and developers as we move into the future of mobile applications for the enterprise.

Meet some of the people behind the new Oracle Fusion Middleware A-Team Chronicles blog, where you'll find technical tales from the trenches.

The panel of A-Team architects discussed the tech trends that are having the greatest impact in the real world.

Oracle Fusion Middleware A-Team architects discuss the resources they rely on and share to keep their skills sharp.

What distinguishes an architecture that is ready for Big Data from one that is not? What are some of the typical mistakes organizations make as they take their first steps toward big data?

Big data experts discuss how Oracle Database fits into a Big Data Architecture, and share insight on a persistent problem in technology adoption.

There's big, and then there's BIG. Experts discuss the challenges of keeping up with coming data explosion.