home.social

#software-architecture — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #software-architecture, aggregated by home.social.

fetched live
  1. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  2. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  3. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  4. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  5. #AgenticAI architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This #InfoQ eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

    #SoftwareArchitecture #AIArchitecture #AIAgents

  6. architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

  7. “The real problem is not whether machines think but whether men do.” – B. F. Skinner

    New tools, AI included, can accelerate development, but they do not replace critical thinking. Architecture decisions, risk assessment, and system design still require human judgment. Better tools make thinking more important, not less.

    💬 How do you ensure that convenience does not replace understanding?

    #DevThinking #SoftwareArchitecture #CodeQuality

    Photo by Eugen Str on Unsplash

  8. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read #InfoQ to see how the system performed 👉 bit.ly/4p0w8Uh

    #AI #GenerativeAI #LLMs #SoftwareArchitecture #RAG

  9. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read to see how the system performed 👉 bit.ly/4p0w8Uh

  10. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new #InfoQ article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

    #Java #SpringBoot #ApacheKafka #Redis #Microservices #SoftwareArchitecture

  11. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

  12. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  13. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  14. Not every pattern improves a system. A design pattern applied without understanding often adds more complexity than value. The best pattern is the one that solves a real problem and disappears into the background.

    Based on “Patterns Compact” by Karl Eilebrecht. #SoftwareArchitecture #DesignPatterns #Engineering

    Photo by Amsterdam City Archives on Unsplash

  15. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the #InfoQ20 campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

    #ComputerScience #SoftwareEngineering #SoftwareArchitecture #TechHistory

  16. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

  17. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  18. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

  19. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  20. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  21. Most teams ask the wrong question about AI deployment. 🤖 Instead of obsessing over SOTA benchmarks, we need to ask: what’s actually good enough for the task?

    Part 1 of our series breaks down the architecture driving pragmatic choices. It’s the map for everything ahead. Don’t get lost in feature bloat.

    Read the full analysis: post.kapualabs.com/p4tycsm7

    #ArtificialIntelligence #EnterpriseAI #SoftwareArchitecture

  22. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  23. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  24. 🎉 The BaselOne 2026 Program is taking shape!

    Our Program Committee has selected a fantastic lineup of international experts covering #SoftwareArchitecture, #Java, #cloud, #AI, #Security, #DevOps and more.

    Curious who’s taking the stage in Basel this October?

    👉 baselone.org/en/baselone-2026-

    Which speaker are you looking forward to most?

    🎟️ Regular tickets are available now!

    See you at the Markthalle Basel on 14-15 October 2026.

    #BaselOne26 #Basel #softwareEngineering

  25. 𝐈𝐟 𝐲𝐨𝐮 𝐡𝐚𝐝 𝐭𝐨 𝐰𝐚𝐭𝐜𝐡 𝐨𝐧𝐥𝐲 𝐨𝐧𝐞 𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐭𝐚𝐥𝐤 𝐢𝐧 𝐲𝐨𝐮𝐫 𝐥𝐢𝐟𝐞𝐭𝐢𝐦𝐞, 𝐰𝐡𝐚𝐭 𝐰𝐨𝐮𝐥𝐝 𝐢𝐭 𝐛𝐞?

    As part of #InfoQ20, we’ve been revisiting the ideas that shaped modern software architecture.

    It’s no surprise that 𝐑𝐢𝐜𝐡 𝐇𝐢𝐜𝐤𝐞𝐲’𝐬 𝟐𝟎𝟏𝟏 𝐭𝐚𝐥𝐤 “𝐒𝐢𝐦𝐩𝐥𝐞 𝐌𝐚𝐝𝐞 𝐄𝐚𝐬𝐲” remains the #𝟏 𝐦𝐨𝐬𝐭-𝐰𝐚𝐭𝐜𝐡𝐞𝐝 𝐩𝐫𝐞𝐬𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧 𝐢𝐧 𝐈𝐧𝐟𝐨𝐐 𝐡𝐢𝐬𝐭𝐨𝐫𝐲.

    💡 Core idea that still resonates:
    ⇨ Simple is often mistaken for easy.
    ⇨ “Easy” means familiar or at hand.
    ⇨ “Simple” is the opposite of complex - i.e., intertwined or tied together.

    𝐒𝐢𝐦𝐩𝐥𝐞 ≠ 𝐞𝐚𝐬𝐲❗

    Worth rewatching - whether you’re early in your career or making architecture decisions.

    🔗 Watch now: bit.ly/3XQ5zFl

    #SoftwareArchitecture

  26. 𝐈𝐟 𝐲𝐨𝐮 𝐡𝐚𝐝 𝐭𝐨 𝐰𝐚𝐭𝐜𝐡 𝐨𝐧𝐥𝐲 𝐨𝐧𝐞 𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐭𝐚𝐥𝐤 𝐢𝐧 𝐲𝐨𝐮𝐫 𝐥𝐢𝐟𝐞𝐭𝐢𝐦𝐞, 𝐰𝐡𝐚𝐭 𝐰𝐨𝐮𝐥𝐝 𝐢𝐭 𝐛𝐞?

    As part of , we’ve been revisiting the ideas that shaped modern software architecture.

    It’s no surprise that 𝐑𝐢𝐜𝐡 𝐇𝐢𝐜𝐤𝐞𝐲’𝐬 𝟐𝟎𝟏𝟏 𝐭𝐚𝐥𝐤 “𝐒𝐢𝐦𝐩𝐥𝐞 𝐌𝐚𝐝𝐞 𝐄𝐚𝐬𝐲” remains the #𝟏 𝐦𝐨𝐬𝐭-𝐰𝐚𝐭𝐜𝐡𝐞𝐝 𝐩𝐫𝐞𝐬𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧 𝐢𝐧 𝐈𝐧𝐟𝐨𝐐 𝐡𝐢𝐬𝐭𝐨𝐫𝐲.

    💡 Core idea that still resonates:
    ⇨ Simple is often mistaken for easy.
    ⇨ “Easy” means familiar or at hand.
    ⇨ “Simple” is the opposite of complex - i.e., intertwined or tied together.

    𝐒𝐢𝐦𝐩𝐥𝐞 ≠ 𝐞𝐚𝐬𝐲❗

    Worth rewatching - whether you’re early in your career or making architecture decisions.

    🔗 Watch now: bit.ly/3XQ5zFl

  27. 𝗶𝗦𝗔𝗤𝗕 𝗮𝗻𝗱 𝗜𝗦𝗧𝗤𝗕 𝗝𝗼𝗶𝗻 𝗙𝗼𝗿𝗰𝗲𝘀 𝘁𝗼 𝗦𝘁𝗿𝗲𝗻𝗴𝘁𝗵𝗲𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 🤝 On June 16, Dr. Guido Gryczan (#iSAQB) and Dr. Klaudia Dussa-Zieger (#ISTQB) signed a Memorandum of Understanding, marking the beginning of a closer collaboration between our organizations.

    Together, we'll strengthen the connection between #SoftwareArchitecture and #SoftwareTesting by aligning certification schemes, curricula, and terminology.

    Watch the short video to learn why this partnership matters: t1p.de/ebjdo

  28. 𝗶𝗦𝗔𝗤𝗕 𝗮𝗻𝗱 𝗜𝗦𝗧𝗤𝗕 𝗝𝗼𝗶𝗻 𝗙𝗼𝗿𝗰𝗲𝘀 𝘁𝗼 𝗦𝘁𝗿𝗲𝗻𝗴𝘁𝗵𝗲𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 🤝 On June 16, Dr. Guido Gryczan (#iSAQB) and Dr. Klaudia Dussa-Zieger (#ISTQB) signed a Memorandum of Understanding, marking the beginning of a closer collaboration between our organizations.

    Together, we'll strengthen the connection between #SoftwareArchitecture and #SoftwareTesting by aligning certification schemes, curricula, and terminology.

    Watch the short video to learn why this partnership matters: t1p.de/ebjdo

  29. #CaseStudy: How Delivery Hero successfully retired Google Analytics and migrated to an internal user-tracking platform.

    In this #InfoQ video, Alina Krasavina shares how a simple, highly scalable architecture enabled the team to handle 10× more load while capturing 97% of tracking data.

    Learn about:
    • Architectural decisions
    • Development challenges
    • Lessons learned

    🔗 Watch now: bit.ly/43W2hCN

    #SoftwareArchitecture #DataAnalytics

  30. : How Delivery Hero successfully retired Google Analytics and migrated to an internal user-tracking platform.

    In this video, Alina Krasavina shares how a simple, highly scalable architecture enabled the team to handle 10× more load while capturing 97% of tracking data.

    Learn about:
    • Architectural decisions
    • Development challenges
    • Lessons learned

    🔗 Watch now: bit.ly/43W2hCN

  31. A practical breakdown of 12 Laravel fixes that cut VPS memory usage from 90%+ to a stable 65–80% range. hackernoon.com/how-i-cut-vps-m #softwarearchitecture

  32. A practical breakdown of 12 Laravel fixes that cut VPS memory usage from 90%+ to a stable 65–80% range. hackernoon.com/how-i-cut-vps-m #softwarearchitecture

  33. Inside #Atlassian’s Forge Billing Architecture: a platform designed to support usage-based pricing across its cloud app development ecosystem.

    It processes large-scale usage events with correct attribution, deduplication, and aggregation using a streaming pipeline, idempotent processing, and layered storage.

    The result? Precise billing, near real-time visibility, and reliable reconciliation across distributed services.

    🔗 Dive into the architectural breakdown: bit.ly/4eGoEB2

    #InfoQ #SoftwareArchitecture #EventDrivenArchitecture #DistributedSystems

  34. Inside ’s Forge Billing Architecture: a platform designed to support usage-based pricing across its cloud app development ecosystem.

    It processes large-scale usage events with correct attribution, deduplication, and aggregation using a streaming pipeline, idempotent processing, and layered storage.

    The result? Precise billing, near real-time visibility, and reliable reconciliation across distributed services.

    🔗 Dive into the architectural breakdown: bit.ly/4eGoEB2

  35. Two decades of cutting-edge tech trends! Celebrate #InfoQ20 with us by leveling up your stack.

    Today, we’re offering a comprehensive guide to #CellBasedArchitecture.

    It delivers the key principles, practical implementation strategies, and architectural insights needed to successfully apply a cell-based approach to both existing and new systems.

    📥 Download your FREE copy: bit.ly/3Sgw4Rb

    #SoftwareArchitecture #SociotechnicalArchitecture #DDD #ArchitectureDesign #DistributedSystems

  36. Two decades of cutting-edge tech trends! Celebrate with us by leveling up your stack.

    Today, we’re offering a comprehensive guide to .

    It delivers the key principles, practical implementation strategies, and architectural insights needed to successfully apply a cell-based approach to both existing and new systems.

    📥 Download your FREE copy: bit.ly/3Sgw4Rb

  37. From payment spikes to market volatility, elasticity enables FinTech platforms to scale resources automatically and deliver reliable, high performance services while optimizing infrastructure costs.

    #FinTech #Elasticity #Scalability #Payments #Microservices #Engineering #SoftwareArchitecture

  38. AI can generate hundreds of lines of code in seconds.

    𝐁𝐮𝐭 𝐝𝐨𝐞𝐬 𝐢𝐭 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝 𝐲𝐨𝐮𝐫 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞?
    𝐃𝐨𝐞𝐬 𝐢𝐭 𝐟𝐨𝐥𝐥𝐨𝐰 𝐲𝐨𝐮𝐫 𝐩𝐚𝐭𝐭𝐞𝐫𝐧𝐬?
    𝐃𝐨𝐞𝐬 𝐢𝐭 𝐜𝐫𝐞𝐚𝐭𝐞 𝐦𝐚𝐢𝐧𝐭𝐚𝐢𝐧𝐚𝐛𝐥𝐞 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬?

    On June 25, Tomáš Herceg will build a real feature live and show how to guide AI toward code you actually want in production.

    No theory. No hype. Just real development.

    Get more info and register now at hypeless-ai.updateconf.net

    #AI #SoftwareArchitecture #SoftwareDevelopment

  39. 🚀 NEW on We ❤️ Open Source 🚀

    AI is becoming a valuable tool for software architecture, especially when creating quick proofs of concept. But it still requires human guidance and domain expertise.

    Avindra Fernando discusses where AI code reviews add value, where they struggle, and why community remains essential for growth and learning.

    allthingsopen.org/articles/ai-

    #WeLoveOpenSource #AI #OpenSource #SoftwareArchitecture

  40. Mapping dynamic JSON objects to `google.protobuf.Struct` in your Go APIs? You might actually be hurting your performance. Unstructured Protobuf loses the compression benefits of static schemas, meaning a simple key and value can take up nearly double the space of compact JSON.

    I wrote about the hidden structural costs and what the wire format actually looks like under the hood: kmcd.dev/posts/hidden-cost-of- #go #protobuf #performance #softwarearchitecture