Live and recent posts from across the Fediverse tagged #software-architecture, aggregated by home.social.
AI is changing how we build software. Are we thinking long term?
From monoliths vs. microservices to testing, requirements, and training junior engineers, AI-driven development raises architectural questions we can’t ignore.
🎧 Listen to the #InfoQ podcast with Joy Ebertz: https://www.infoq.com/podcasts/what-really-mean-program-ai/
🚀 3 engineering deep-dives to level up your week:
📖 READ: Cloudflare’s Vite+ hits 1.0 (GitLab CI support, hooks, tsup migration)
[🔗 https://www.infoq.com/news/2026/10/cloudflare-viteplus-stable/]
🍿 WATCH: Netflix’s ontology-driven observability (Enterprise-scale knowledge graphs)
[🔗 https://www.infoq.com/presentations/netflix-observability-aiops-ontology-scale/]
🎧 LISTEN: What does it really mean to program with AI? (Joy Ebertz & Michael Stiefel)
[🔗 https://www.infoq.com/podcasts/what-really-mean-program-ai/]
👇 Which one are you checking out first?
#InfoQ #SoftwareEngineering #AI #Netflix #Cloudflare #SoftwareArchitecture #EngineeringCulture
What happens when one API knows every provider? The real challenge is keeping a simple interface while making room for the differences behind it—without losing clarity.
How I'd scope a broad prompt down to two flows — filing a claim and the adjuster work queue — and the decisions an interviewer wants to hear. https://hackernoon.com/designing-a-claims-intake-platform #softwarearchitecture
Clean architecture is a lot easier when you get to start from scratch. David Pace shares how @Merck is bringing modern technology together with years of existing systems and data during our healthcare virtual panel. #SoftwareArchitecture #SoftwareEngineering #HealthTech #thoughtbot
AI doubled Spotify’s code output. Can its delivery pipeline keep up?
Monthly merged code changes jumped from 8K to 17K. Now, Spotify is rethinking testing, rollback safeguards, deployment timing, observability, and workload prioritization to keep delivery stable.
🔗 Read the full story on InfoQ: https://www.infoq.com/news/2026/10/spotify-ai-quality-controls/
Transactional Outbox, Saga Pattern, Idempotent Consumers, Clickbait Events ...
In der Event-Driven Architecture gibt es viele Patterns & Anti-Patterns. Nächsten Dienstag bei oose greife ich 4–5 spannende heraus – universelle wie kontextabhängige.
Freue mich auf eure Geschichten & den Austausch! Meldet euch an und sagt es weiter. 👇
FYI: Explaining middleware: Middleware is software that sits between applications, operating systems and networks, translating and routing requests so separate systems can work as one. https://ppc.land/middleware/ #Middleware #SoftwareDevelopment #ApplicationIntegration #ITInfrastructure #SoftwareArchitecture
Frontend: Vue.js. Backend: Kotlin. Endgerät: ein Mikrocontroller.
MICRO, das Remote Lab der THM, ist ein verteiltes System mit Microservices pro Station, Livestream und Shared Sessions per WebSocket. Gebaut von Studierenden, international ausgezeichnet.
Jakob Czekansky zeigt beim nächsten programmier.bar-Meetup, wie das System aufgebaut ist.
📅 Do, 22.10., ab 18 Uhr, Lotum, Bad Nauheim
🎟️ Kostenfrei anmelden: https://www.meetup.com/programmierbar/events/316564328/
Die #BaselOne26 läuft! 🚀
Heute sind die Workshops bereits in vollem Gange – morgen folgt der grosse Konferenztag mit mehr als 30 Talks.
Kurzfristig neu im Programm: @patbaumgartner spricht über „From Chaos to Cohesion: Building Modular Monoliths in the Real World“ – mit Spring Modulith, klaren Grenzen, Tests und Doku statt Big-Bang-Rewrite. 💡
👉 Programm: https://baselone.org/#programm
🎟️ Tickets: https://eventfrog.ch/BaselOne26
#GitHub migrated 800k+ lines of Copilot code from TypeScript to #RustLang in 14.5 weeks using Copilot.
Results:
▫️ Startup time dropped 5.25s ➡️ 292ms
▫️ Shipped 135 releases during the rewrite with zero downtime
▫️ 128 PRs via incremental N-API interop
🔗 Read more: https://www.infoq.com/news/2026/10/github-copilot-rust-migration/
Oh!
"Creepy Uncle Bob" (Robert C. Martin) has completely ditched his "Clean Code" grift and fully pivoted to AI!
🫠
#cleancode #creepyunclebob #coding #programming #neverslop #unclebob #friedbrain #midlifecrisis #agile #softwarearchitecture
Darauf freue ich mich — am Donnerstag, 15. Oktober, in der Markthalle.
Frage vorab: Was wolltest du schon immer über ein bestimmtes System wissen und hast es nur mühsam oder gar nicht herausgefunden?
Gern konkret — nicht „wie schneidet man Microservices", sondern „warum hängt Modul X an Y". Eine davon greife ich auf und beantworte sie live.
Beispielsystem ist Apache Maven: öffentlich und damit nachprüfbar.
JobSmart shows how quickly evidence-heavy apps stop being simple CRUD.
A job can combine structured records, photos, signatures and generated PDFs. Those create distinct states:
local save ≠ upload ≠ document generation ≠ recipient delivery.
Artifact lifecycle deserves first-class product state.
#FieldService #DocumentAutomation #JobSmart #SoftwareArchitecture
When an engineering team spends three months debating architecture, they are rarely debating architecture. They are debating who gets to say no to whom. 1/2
How do you maintain strict, session-level message ordering across thousands of independent channels in Apache Kafka?
Joshua Oluikpe breaks down a Go-based solution utilizing:
• Application-level routing & consistent hashing
• Retries
• Contiguous watermark commits
🔍 Dive deep - https://www.infoq.com/articles/apache-kafka-golang-session-ordered-pipeline/
#ApacheKafka #Golang #DistributedSystems #SoftwareArchitecture #InfoQ
"What is an ontology, and why is #Netflix using one for observability?
When engineers hear ""ontology,"" they usually think of academic papers or dry semantic standards. But as Renzo Sanchez-Silva puts it: it’s actually as simple as how a baby learns - or how Tarzan loves Jane.
An ontology encodes meaning through simple Subject-Predicate-Object triples, helping connect scattered data across microservices and make it instantly useful for enterprise AI.
🎥 Watch the full video: https://www.infoq.com/presentations/netflix-observability-aiops-ontology-scale/
#Observability #AIOps #SoftwareArchitecture #DataEngineering #NetflixEng"
Am 26./27.11. gebe ich in Hamburg mein EDA-Training, bewusst vor Ort. Zwei Tage raus aus dem Projektalltag und Zeit für die Grundlagen: Outbox, Idempotenz, Fehlerbehandlung, Prozesse über viele Services. Dazu Übungen und Diskussion mit Leuten, die vor ähnlichen Problemen stehen.
Infos und Anmeldung: https://www.oose.de/seminar/event-driven-architecture
Teilen ist sehr willkommen!
Change one line in the tls module and I've signed myself up for twelve releases, in four sequential waves, each one gated on a human pressing a button. I know, because I was the human.
An architectural review of the toolkit last July called it "propagation debt" and named it the principal systemic risk. Not a bug... the way I'd built it. Fifty-one modules at the time, sixty-seven now.
The part that stuck with me: propagation stalls where fan-out is largest. The change with twelve downstream releases is the one you look at late on a Friday and decide is a problem for next week.
Split things badly and you get a mess; split them properly and you get a bill. So the question became how cheap I can make the tax:
- Renovate does the bumping, fleet-wide, from one group-level bot
- the pipelines do the gating
- a release-train skill (still in review) that knows which way round to cut a release
That last one matters more than it sounds. Leaves first across the config family: 53 releases. Upstream first: 27. I had it backwards for about an hour.
None of it is finished, but all twenty-six config adapters are sat on the current core without me chasing a single one.
Akka tested a spec-driven AI porting workflow across 65 open-source projects:
➡️ 9.41B tokens used over 99.3 hours
➡️ 57 ports delivered fewer lines of code or better performance.
See how the workflow works, the Sonnet vs. Opus speed/token trade-offs, and why infrastructure projects often took a performance hit.
📖 Read more: https://www.infoq.com/news/2026/10/ai-spec-driven-delivery/
How do you keep a culture of team autonomy while you scale, without losing coherence?
At DHL eCommerce Benelux we've been living with that question for 2.5 years, growing from a handful of engineers to 150+ people in 35 teams. This Wednesday Marc Rooding and I share the story at Digital Architecture Design Day in Nieuwegein. >>>
What if AI agents are actually more useful in brownfield than greenfield? 🤖
At #BaselOne26, Marek Dominiak shows how agentic AI helped modernize a 2M+ LOC Java monolith – with bounded agentic loops, testing & security guardrails and a clear definition of done.
No magic prompts. No blind vibe coding. Just practical lessons on where AI helps – and where it wastes engineering effort.
Explore more #BaselOne talks: 👉 https://baselone.org/#programm
In this #InfoQ video, Ian Cooper explores how AsyncAPI, xRegistry, CloudEvents, and schema registries bring discovery, governance, and automation to asynchronous APIs.
From event definitions to code generation and infrastructure provisioning, see how Just Eat Takeaway manages event-driven integrations at scale.
🎬 Watch now [transcript included] – https://www.infoq.com/presentations/managing-async-apis/
#EventDrivenArchitecture #AsyncAPI #CloudEvents #SoftwareArchitecture #InfoQ
I can't talk a lot about my clients, and this is not my project, but I am still proud of what some of the teams around me do.
Publicis Sapient and Schneider Electric use the open source tool e-footprint to measure emissions across digital services. Instead of checking single devices, it evaluates the full setup from edge to cloud. Better architecture decisions cut emissions by over 40 percent.
https://www.publicissapient.com/company/news/schneider-electric-e-footprint
𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗔𝗜 🤖 Nikita Golovko & Roger Rhoades explore 5 architectural patterns for making #AI systems more dependable in production, from Training–Serving Separation to Simplex Architecture & Inference Gateways. Thanks for sharing your insights!
👉 t1p.de/nwvri
𝗧𝗵𝗲 𝗶𝗦𝗔𝗤𝗕 𝗚𝗲𝗻𝗲𝗿𝗮𝗹 𝗔𝘀𝘀𝗲𝗺𝗯𝗹𝘆 2026 𝗰𝗮𝗺𝗲 𝘁𝗼 𝗮 𝗰𝗹𝗼𝘀𝗲 𝘁𝗼𝗱𝗮𝘆 𝗶𝗻 𝗘𝗿𝗳𝘂𝗿𝘁, 𝗚𝗲𝗿𝗺𝗮𝗻𝘆. 🤝
To all our members: thank you. You contribute your time and expertise on a voluntary basis to develop #SoftwareArchitecture education and certification for professionals around the world. That commitment is at the heart of #iSAQB, and we deeply appreciate it.
Thank you for two days of open conversations, different perspectives and thoughtful work together and for everything you do throughout the year.