InfoQ Homepage Architecture & Design Content on InfoQ
-
John DesJardins on In-Memory Data Grids, Stream Processing, and App Modernization
In this podcast, John DesJardins, field CTO and VP solution architecture at Hazelcast, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: how in-memory data grids have evolved, use cases at the edge (IoT, ML inference), integration of stream processing APIs and techniques, and how data grids can be used within application modernization.
-
Akhilesh Gupta on the Architecture of LinkedIn’s Real-Time Messaging Platform
Charles Humble talks to Akhilesh Gupta, the technical lead for LinkedIn's real-time delivery infrastructure, and also LinkedIn messaging. They discuss the architecture behind LinkedIn’s real-time platform, its building blocks, the frameworks used and other technical details.
-
Yan Cui on Serverless, Including Orchestration/Choreography, Distributed Tracing, & More
Today on the InfoQ Podcast, Yan Cui (a long time AWS Lambda user and consultant) and Wes Reisz discuss serverless architectures. The conversation starts by focusing on architectural patterns around choreography and orchestration. From there, the two move into updates on the current state of serverless cold start times, distributed tracing, and state.
-
Liran Haimovitch on Understandability, Complexity, and Live Debugging
In this podcast, Liran Haimovitch, CTO at Rookout, sat down with InfoQ podcast co-host Daniel Bryant. Topics discussed included: the concept of “understandability” and how this relates to building modern software systems, how complexity impacts a system’s understandability, and the benefits of live debugging tooling.
-
Ana Medina on Chaos Engineering, Game Days, and Learning
In this podcast, Ana Medina discussed with Daniel Bryant about how enterprise organisations are adopting chaos engineering with the requirements for guardrails and the need for “status checks” to ensure pre-experiment system health; how to run game days or IT fire drills when everyone is working remotely; and why teams should continually invest in learning from past incidents.