Podcasts about sven johann

Im Podcast diskutieren Torsten Mandry und Sven Johann Überlegungen und Erfahrungen für oder gegen eine Microservices-Architektur bzw. einen Modulithen. Während Microservices oft wegen ihrer Unabhängigkeit und Entkopplung geschätzt werden, zeigen sich auch Nachteile, etwa durch erhöhten Schnittstellenaufwand, komplexes Deployment und Infrastruktur. Torsten beschreibt, wie er durch ein eigenes Experiment mit einem Modulith herausfinden wollte, ob und wie Modularisierung ohne Microservices gelingen kann. Die beiden diskutieren die Abwägungen dieser Entscheidung – abhängig von Teamgröße, Projektphase, technischen Anforderungen und strategischer Planung.

In this episode of the CaSE Podcast, Sven Johann, Alex Heusingfeld, and Heinrich Hartmann dive into the concept of sensitivity points in software architecture, using the recent Volkswagen data leak as a striking example. They explore how seemingly minor architectural decisions and code changes can carry massive implications when balancing trade-offs like data privacy versus functionality. The trio also discusses the growing impact of AI-assisted development, reflecting on practical experiences with tools like ChatGPT, Cursor, and GitHub Copilot.

Plattformen sind überall – aber meinen wir immer dasselbe? In dieser Episode des INNOQ Podcasts sprechen Sven Johann und Erik Wilde über die unterschiedlichen Bedeutungen des Plattformbegriffs. Von Business-Plattformen über API-Plattformen bis hin zu Internal Developer Platforms und Infrastrukturplattformen: Welche Rolle spielen sie in Unternehmen, wie grenzen sie sich voneinander ab und warum ist es wichtig, den Begriff richtig einzuordnen? Ein Gespräch über strategische Plattformentscheidungen.

Simon Harrer sagt: „Von Data Contracts werden wir ganz viel hören. Sie werden die Datenwelt im Sturm erobern, weil sie gebraucht werden.” In dieser Folge sprechen Sven Johann und Simon Harrer über Data Contracts und warum diese unverzichtbar für moderne Datenverarbeitung werden. Doch wie genau funktioniert das in der Praxis? Data Contracts sichern die Datenqualität, geben Teams klare Vereinbarungen und gestalten Prozesse effizienter. Simon nennt Anwendungsbeispiele, wie diese Verträge heute schon eingesetzt werden, und gibt einen Ausblick darauf, wie sie die Zukunft der Datenarchitektur prägen werden.

In dieser Folge des INNOQ Podcasts geht es um einen echten Klassiker der modernen Softwareentwicklung: „Programming as Theory Building" von Peter Naur. Daniel Westheide und Sven Johann sprechen über dessen anhaltende Relevanz und warum Programmieren weit mehr als das Schreiben von Code ist. Sie erläutern, wie genaue Planung und ein tiefes Verständnis für das Softwaresystem die Grundlage für erfolgreiche Projekte bilden. Daniel gibt zudem Einblicke in praktische Methoden wie Domain-driven Design, Event Storming und Prototyping, die helfen, langfristig wartbare Software zu entwickeln. Außerdem sprechen Sven und sein Gast über die Bedeutung von genauer Dokumentation und warum es wichtig ist, Entwickler:innen langfristig im Team zu halten, um Wissen zu teilen.

Wie verändern Vektordatenbanken die Suche in Webshops und auf Unternehmenswebseiten? In dieser Folge diskutieren Sven Johann und Marco Steinke die Vorteile von Vektordatenbanken gegenüber der traditionellen indexbasierten Suche. Marco erklärt, wie AI-Modelle wie Word2Vec Wörter semantisch repräsentieren und in bestehende Softwarearchitekturen integriert werden. Die Folge zeigt, wie Vektorsuche die klassische indexbasierte Suche ergänzen kann und welche Use Cases besonders profitieren.

Backstage ist ein vielseitiges Framework, mit dem individuelle Developer Portale erstellt werden können. Tammo van Lessen hat es sich genauer angesehen, weil es Probleme löst, die an vielen Ecken und Enden auftauchen: "Wer maintained denn das Stück Software eigentlich?" oder "Wo finde ich den Bug Tracker?". In dieser Folge diskutieren Tammo van Lessen und Sven Johann, wie Backstage als zentrale Plattform dezentrale Inhalte automatisch zusammenbringt und dadurch die Verwaltung von Services, Templates, APIs, Observability und Dokumentationen vereinfacht.

Eine zentrale Frage steht am Beginn dieser Folge zu Architekturqualität mit Sven Johann und Gernot Starke: Was bedeutet eigentlich Qualität? Im Gespräch erörtern sie, wie durch direkte Dialoge mit Stakeholdern Anforderungen nicht nur identifiziert, sondern auch effektiv für die Entwicklungsarbeit nutzbar gemacht werden können. Mit einer Vielzahl an praxisnahen Beispielen illustrieren die, wie essenziell es ist, Qualitätsanforderungen flexibel an den jeweiligen Projektkontext anzupassen.

Microservices-Katastrophen, proprietärer Unsinn und überengineerte Single-Page-Applications (SPAs): In dieser Folge sprechen Sven Johann, Jörg Müller und André Aulich darüber, warum Softwareentwicklung einen starken Drall zu übermäßiger Komplexität bekommen hat, beleuchten, wie es dazu kam und diskutieren mögliche Lösungsansätze.

Sven Johann spricht über seine Karriere im Bereich Software-Architektur.

Sven Johann talks to Adam Tornhill about the link between how organizations write code and how teams work together. Adam Tornhill can make this link visible to help improve your team's code and your organization's work. The interview is based on Adam's book "Software Design X-Rays".

Cross-funktionale Teams sind autonom und dadurch produktiver. In der Realität scheitern Initiativen für einen Wandel zu solchen Teams jedoch viel zu oft. Sven zeigt uns, wieso crossfunktionale Teams in den Abgrund gestürzt werden, oft natürlich unabsichtlich - und selbstverständlich auch, wie man so etwas vermeiden kann. Uwe Friedrichsen “You build it, you run it!” wird machtpolitisch missbraucht Tweet von Stefan Roock Team Topologies Folge mit Anja Kammer Team Topologies Buch Folge mit Gerrit Beine Folge zu Site Reliabilty Engineering mit Bastian Spanneberg Buch Anleitung zum Unglücklichsein Gregor Hohpe: Enterprise Architecture = Architecting the Enterprise

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubAdam Tornhill - Author of "Software Design X-Rays" and Founder & CTO at CodeSceneSven Johann - Senior Consultant at INNOQ and Podcast Host at CaSEDESCRIPTIONThere's a link between how organizations write code and how teams work together. Adam Tornhill can make this link visible to help improve your team's code and your organization's work. The interview is based on Adam's book "Software Design X-Rays": https://amzn.to/3DEeEnIRead the full transcription of the interview here:https://gotopia.tech/bookclub/episodes/behavioral-code-analysishttps://gotopia.tech/bookclub/episodes/behavioral-code-analysis-part2RECOMMENDED BOOKSAdam Tornhill • Software Design X-Rays • https://amzn.to/3DEeEnIAdam Tornhill • Your Code as a Crime Scene • https://amzn.to/3FI5E2VAdam Tornhill • Lisp for the Web • https://leanpub.com/lispwebAdam Tornhill • Patterns in C • https://leanpub.com/patternsincMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQJohn Ousterhout • A Philosophy of Software Design • https://amzn.to/3DBP9DCDave Thomas & Andy Hunt • The Pragmatic Programmer • https://amzn.to/3azvUy3Fred Brooks Jr. • The Mythical Man-Month • https://amzn.to/31NJc5Chttps://twitter.com/GOTOconhttps://www.linkedin.com/company/goto-https://www.facebook.com/GOTOConferencesLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at https://gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

Sven Johann talks with Manuel Pais about the challenges of development teams being asked to be responsible for many topics like their problem domain, technology/programming languages, security, infrastructure and operations, UX, etc. Manuel explains what cognitive load is, which types of cognitive load exist and where it can be reduced and where not. They then discuss the four fundamental team topologies stream-aligned, enabling, platform and complicated subsystem: their benefit, how you should run those teams and which obstacles you need to overcome to be successful.

Alex Bramley continuous his conversation with Sven Johann. They begin with how granular you should monitor your user journeys and then discuss error budget policies in depth. They continue on how to iterate on SLIs, SLOs and error budget policies. They close the conversation with SLO alerting.

Alex Bramley continuous his conversation with Sven Johann. They start with what external and internal dependencies do with your availability requirements and how you calculate availability if you have a microservices dependency tree. They look into how you can introduce SLOs to your organisation. After that, they switch to measure user happiness with your monitoring system, measurement windows and how to report those results.

Alex Bramley talks to Sven Johann about the basics of service level objectives. They begin with terminologies (SLI, SLO, SLA, Error Budget), look at costs of outages and discuss what reliability has to do with customer happiness. They continue with having 100% reliability is the wrong target and what’s possibly the right target. Alex then explains how to get started with collecting data about your system’s behaviour. They close the first part of this series by looking into latency SLIs.

Eoin Woods discusses with Sven Johann all the things developers need to know to bring systems successfully into production and how to keep them there. They discuss production environments, what goes wrong in production, architectural requirements for operations, cost of very high availability, stability and capacity, communicating operational concerns, observability, learning from incidents, chaos engineering and operational models (SRE, You build it, you run it, classic).

Birgitta Böckeler talks with Sven Johann about cultivating architecture principles. They first discuss what architecture principles are, why they are useful, how they are structured and how they help to guide decision making across multiple teams. They then talk about their lifecycle: who creates them, checks if they are aligned with business goals, prioritizes them, how they should be communicated, how you know they are useful and when to potentially retire them.

Daniel Bryant talks with Sven Johann about the business problems to modernize applications. They need to be decoupled from the compute fabric and the network fabric and Daniel explains the reasons for that, what products are available and what strategies the different cloud vendors follow. They move on with how to get started, questions to select an API gateway, technologies behind them and the challenges. They talk about service meshes features, especially on the canary testing side, how they work under the hood and how they help as infrastructure with application modernization. They close the discussion on how to select a service mesh product and what rollout strategies exist.

Peter Elger talks with Sven Johann about AI as a service - commodity web services offered by large cloud providers, which make it very easy to use AI in your application just by using an API. They start the discussion with the typical AI use cases companies in finance, retail and so on have and which of those are already as a commodity available and which are not. They then discuss how those APIs are used, from very simple API calls like text-to-speech to slightly more complicated ones like chat bots or recommendation engines. They continue with understanding how you come up with AI requirements and how to (regression) test your AI service, which is often different than doing the same with non-AI code. They clarify how much AI you need to know to use those services, the cost models of them and how to get your AI to production. The conversation then moves to lower level AI services like AWS SageMaker or Google Tensorflow and how you combine them to create novel pieces of AI relatively quickly. They close the conversation with when to use specific packaged AI solutions and when to create your own AI to push the envelope.

In this episode, Sven Johann hosts Philippe Kruchten, the author of the Managing Technical Debt book. They talk about the research leading to the book and the practical implications the book and the research offer. They start the conversation with discussing terms: technical debt, interest, principal and then start with technical debt on the code level, e.g. code smells, tests and refactoring followed by static analysis and the prioritization of the findings. They then move to technical debt on the architectural level and go through the possibilities on estimating cost and value on those improvement and how to sell it to the business stakeholders. This is followed by explaining technical debt on the infrastructure level and how great code can become technical debt by time passing by (technological gap, software aging). After that the conversation moves towards solving the problem tactically and strategically.

In this episode, Sven Johann hosts Sam Newman, the author of the first Microservices book, to talk about security in the world of Microservices. They discuss why and where it is different to security in a monolithic architecture and why developers must care. They start with automatically rolling out passwords, credentials and API keys in a secure way and continue with patching containers and secure base images. They then continue with automatically update (transitive) dependencies if they have vulnerabilities. They close the conversation with discussing authorisation and authentication using gateways, proxies and service meshes.

Sven Johann talks with Susan Landau about Security and Privacy. After defining those terms they proceed to find out why this important to individuals and societies. They discuss why its the job of intelligence agencies to collect data, but how we can protect us against them. Then Susan discusses the importance of Two-Factor Authentication, how wiretapping and backdoors work these days and how the FBI tries to unlock locked devices with “1984” terminology. The conversation moves from end-to-end encryption, metadata analysis and VOIP decryption to targeted attacks and political influence of security threats. They finish the conversation with what we can learn from Google and Sun Microsystems on privacy, security and the architectural requirements of anonymized test data.

Sven Johann talks with Steve McConnell about Software Estimation. Topics include when and why businesses need estimates and when they don’t need them; turning estimates into a plan and validating progress on the plan; why software estimates are always full of uncertainties, what these uncertainties are and how to deal with them. They continue with: […]

Sven Johann talks with Steve McConnell about Software Estimation. Topics include when and why businesses need estimates and when they don’t need them; turning estimates into a plan and validating progress on the plan; why software estimates are always full of uncertainties, what these uncertainties are and how to deal with them. They continue with: estimation, planning and monitoring a Scrum project from the beginning to a possible end. They close with estimation techniques in the large (counting, empirical data) and in the small (e.g. poker planning).

Kief Morris talks to Sven Johann about Infrastructure as Code and why it is important in the “Cloud Age”. Kief talks about the practices and benefits and why you should treat your servers as cattles, not pets.

Kief Morris, cloud specialist at ThoughtWorks and author of the recent book Infrastructure as Code, talks to Sven Johann about why this concept is becoming increasingly important due to cloud computing. They discuss best practices for writing infrastructure code, including why you should treat your servers as cattle, not pets, as well as how to […]

Sven Johann talks with Bill Curtis about Software Quality. They discuss examples of failed systems like Obama Care; the role of architecture; move an org from chaos to innovation; relation between Lean, quality improvement and CMM; Team Software Process.

Sven Johann talks with Bill Curtis about Software Quality. They start with what software quality is and then discuss examples of systems which failed to achieve the quality goals (e.g. ObamaCare) and it’s consequences. They then go on with the role of architecture in the overall quality of the system and how to achieve it […]

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 […]

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.

Sven Johann talks with Andrew Phillips about DevOps. First, they try to define it. Then, they discuss its roots in agile operations, its relationship to lean development and continuous delivery, its goals, and how to get started. They proceed to system thinking and what “You build it, you run it” means for a system when developers have pager duty. They continue with the diversity of DevOps requirements among companies and industries; copying ideas versus finding your own way; culture, mindset, and recommended practices; and the mandatory tool chain. They wrap up by discussing architectural styles that support DevOps and DevOps costs versus benefits.

Sven Johann talks with Andrew Phillips about DevOps. First, they try to define it. Then, they discuss its roots in agile operations, its relationship to lean development and continuous delivery, its goals, and how to get started. They proceed to system thinking and what “You build it, you run it” means for a system when […]

Sven Johann talks with Dave Thomas about innovating legacy systems. Dave clarifies first why legacy systems are both valuable and problematic. Next, they discuss bad systemic and good incremental approaches for innovation of legacy systems; why you shouldn’t rewrite an old system but rather focus on tactical changes to reduce cost or increase productivity within […]

Simon Brown, author of Software Architecture for Developers, talks with Sven Johann about using simple sketches to visualize, communicate and document software architecture. The show starts with a consideration of why sketches are more useful than UML and then continues with the explanation of the C4 model (context, containers, components and classes) and how it fits […]

In this episode, Sven Johann and Eberhard Wolff talk about technical debt and how to handle it. They begin by defining external and internal quality and then talk about technical debt as a metaphor for discussing quality with management. They then consider whether technical debt is bad and how to handle it by using Eric […]