home.social

#softwarearchitecture — Public Fediverse posts

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

  1. A large portion of my job is keeping the customer from overengineering their stuff.

    #softwarearchitecture #consulting

  2. How #Netflix boosted #ApacheDruid performance: by implementing interval-aware caching, they now serve 84% of analytics results from cache and have reduced query load by 33%.

    The secret? Decomposing rolling window queries into reusable time segments.
    ✅ Reduces scan volume
    ✅ Improves P90 latency
    ✅ Optimizes real-time analytics

    Details on #InfoQ: bit.ly/4uHG4DE

    #SoftwareArchitecture #DistributedSystems #DataAnalytics #TimeSeriesData #Caching #BigData #DataEngineering

  3. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  4. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  5. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  6. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  7. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  8. On DDD Europe I'm going to speak about Patterns👍 and Antipatterns👎 for Event-Driven Architecture. Come and see if you recognize patterns from your code base 👀. The conference starts in about four weeks, please spread the word! And if you don't have a ticket yet, use this link for a discount 💶: ti.to/on3/aardling26/discount/

    #eda #eventdrivenarchitecture #softwarearchitecture #conference #dddeurope

  9. On DDD Europe I'm going to speak about Patterns👍 and Antipatterns👎 for Event-Driven Architecture. Come and see if you recognize patterns from your code base 👀. The conference starts in about four weeks, please spread the word! And if you don't have a ticket yet, use this link for a discount 💶: ti.to/on3/aardling26/discount/

    #eda #eventdrivenarchitecture #softwarearchitecture #conference #dddeurope

  10. On DDD Europe I'm going to speak about Patterns👍 and Antipatterns👎 for Event-Driven Architecture. Come and see if you recognize patterns from your code base 👀. The conference starts in about four weeks, please spread the word! And if you don't have a ticket yet, use this link for a discount 💶: ti.to/on3/aardling26/discount/

    #eda #eventdrivenarchitecture #softwarearchitecture #conference #dddeurope

  11. On DDD Europe I'm going to speak about Patterns👍 and Antipatterns👎 for Event-Driven Architecture. Come and see if you recognize patterns from your code base 👀. The conference starts in about four weeks, please spread the word! And if you don't have a ticket yet, use this link for a discount 💶: ti.to/on3/aardling26/discount/

    #eda #eventdrivenarchitecture #softwarearchitecture #conference #dddeurope

  12. On DDD Europe I'm going to speak about Patterns👍 and Antipatterns👎 for Event-Driven Architecture. Come and see if you recognize patterns from your code base 👀. The conference starts in about four weeks, please spread the word! And if you don't have a ticket yet, use this link for a discount 💶: ti.to/on3/aardling26/discount/

    #eda #eventdrivenarchitecture #softwarearchitecture #conference #dddeurope

  13. What if your specification could drive the architecture, workflow, and implementation of your app directly?

    Tomorrow at 8 PM CEST, @SimonMartinelli and I will test that idea live by building a full Java application with the AI Unified Process.

    youtube.com/live/4Fw4Qne9z8E?f

    #Java #SpringBoot #Vaadin #SoftwareArchitecture #AI

  14. We’re building a full Java app live from prompt to production using the AI Unified Process.

    Spring Boot, Vaadin, JOOQ, Google Login, Fly.io, spec driven development, and live architecture decisions with @SimonMartinelli

    Wednesday, 8 PM CEST youtube.com/live/4Fw4Qne9z8E
    #Java #SpringBoot #Vaadin #AI #SoftwareArchitecture

  15. In my talks, I usually make it a point to argue for event-driven choreography. At least at the higher levels of your system, between different bounded contexts and teams.

    I came across this article that puts it very nicely: choreography promotes modularity.

    Read the latest addition to the "Awesome Event-Driven Architecture" list: Michelin's journey from BPM orchestration to event-driven choreography.

    👉blogit.michelin.io/choregraphy

    #eventdrivenarchitecture #eda #softwarearchitecture

  16. In my talks, I usually make it a point to argue for event-driven choreography. At least at the higher levels of your system, between different bounded contexts and teams.

    I came across this article that puts it very nicely: choreography promotes modularity.

    Read the latest addition to the "Awesome Event-Driven Architecture" list: Michelin's journey from BPM orchestration to event-driven choreography.

    👉blogit.michelin.io/choregraphy

    #eventdrivenarchitecture #eda #softwarearchitecture

  17. In my talks, I usually make it a point to argue for event-driven choreography. At least at the higher levels of your system, between different bounded contexts and teams.

    I came across this article that puts it very nicely: choreography promotes modularity.

    Read the latest addition to the "Awesome Event-Driven Architecture" list: Michelin's journey from BPM orchestration to event-driven choreography.

    👉blogit.michelin.io/choregraphy

    #eventdrivenarchitecture #eda #softwarearchitecture

  18. In my talks, I usually make it a point to argue for event-driven choreography. At least at the higher levels of your system, between different bounded contexts and teams.

    I came across this article that puts it very nicely: choreography promotes modularity.

    Read the latest addition to the "Awesome Event-Driven Architecture" list: Michelin's journey from BPM orchestration to event-driven choreography.

    👉blogit.michelin.io/choregraphy

    #eventdrivenarchitecture #eda #softwarearchitecture

  19. In my talks, I usually make it a point to argue for event-driven choreography. At least at the higher levels of your system, between different bounded contexts and teams.

    I came across this article that puts it very nicely: choreography promotes modularity.

    Read the latest addition to the "Awesome Event-Driven Architecture" list: Michelin's journey from BPM orchestration to event-driven choreography.

    👉blogit.michelin.io/choregraphy

    #eventdrivenarchitecture #eda #softwarearchitecture

  20. #LinkedIn has launched a unified integrations platform to standardize & reconcile hiring data across systems.

    • 72% faster onboarding
    • Improved data consistency and completeness
    • Scalable AI-driven hiring enabled via standardized schemas, orchestration workflows, and centralized data processing

    Learn more: bit.ly/48KFwof

    #SoftwareArchitecture #EvolutionaryArchitecture #DataPipelines #DataAnalytics #InfoQ

  21. 𝗖𝗹𝗮𝗿𝗶𝘁𝘆 𝗶𝗻 𝘁𝗵𝗲 𝗔𝗴𝗲 𝗼𝗳 𝗔𝗜 – 𝗪𝗵𝘆 𝗣𝗿𝗲𝗰𝗶𝘀𝗲 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 🗣️

    As #AI becomes part of everyday work, clear communication is turning into a critical skill. 🤖 In Part 2 of the #SoftSkills series by ITech Progress GmbH, we explore why precise prompts, cognitive framing, and critical thinking are becoming essential for software architects and tech professionals.

    Read the article on the #iSAQB blog 👉 t1p.de/su9io

    #SoftwareArchitecture #Communication #CriticalThinking #FutureSkills

  22. #OpenAI has launched a #WebSocket-based execution mode for its Responses API to improve the performance of agentic workflows used in coding agents and real-time AI systems.

    The Impact: early production use shows up to 40% latency reduction and improved throughput in high-concurrency scenarios.

    Learn more: bit.ly/3Pg3ZuS

    #InfoQ #SoftwareArchitecture #API #AIAgents #LowLatency

  23. #CaseStudy - Discover how #Figma replaced a fragmented caching stack with FigCache - an in-house #Redis proxy service.

    The result: what the company describes as six nines of uptime across its caching layer.

    🔗 Explore the architecture, the tradeoffs, and the lessons learned on #InfoQbit.ly/42SKf3L

    #DevOps #SoftwareArchitecture

  24. #Anthropic introduced auto mode in #ClaudeCode, enabling multi-step software development workflows with reduced manual intervention.

    It combines automated execution with layered safety mechanisms, including:
    ⇨ input filtering
    ⇨ action evaluation
    ⇨ two-stage classification
    … while keeping human approval checkpoints for sensitive operations.

    Dive deeper ⇨ bit.ly/4toxJE1

    #InfoQ #SoftwareArchitecture #AIarchitecture #AIcoding #AIAssistedCoding

  25. The movement for cloud computing was putting your data on someone else's computer. AI is letting someone else's code write your code. No general shade on cloud services or AI, they serve a purpose. Though when you're building, architect sustainably.
    #Tech #IndieDev #EthicsInTech #SustainableTech #Development #SoftwareArchitecture

  26. Java modernization estimates get weird when they start with line counts and end with a confident token budget.

    I wrote up a spiderweb model for AI-assisted modernization: scope, semantics, knowledge opacity, integration/data, feedback friction, and ops/governance. It is not a scoring machine. It is a way to remember the boring risks before they become expensive.

    the-main-thread.com/p/moderniz

    #Java #Modernization #SoftwareArchitecture

  27. #Dropbox cut its backend monorepo from 87GB → 20GB.📉

    In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.

    The impact:
    • Reduced clone times
    • Improved CI performance
    • Boosted developer velocity

    Learn more 👉 bit.ly/3R9pSfZ

    #InfoQ #SoftwareArchitecture #Git #Monorepo #Optimization

  28. #Dropbox cut its backend monorepo from 87GB → 20GB.📉

    In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.

    The impact:
    • Reduced clone times
    • Improved CI performance
    • Boosted developer velocity

    Learn more 👉 bit.ly/3R9pSfZ

    #InfoQ #SoftwareArchitecture #Git #Monorepo #Optimization

  29. #Dropbox cut its backend monorepo from 87GB → 20GB.📉

    In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.

    The impact:
    • Reduced clone times
    • Improved CI performance
    • Boosted developer velocity

    Learn more 👉 bit.ly/3R9pSfZ

    #InfoQ #SoftwareArchitecture #Git #Monorepo #Optimization

  30. #Dropbox cut its backend monorepo from 87GB → 20GB.📉

    In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.

    The impact:
    • Reduced clone times
    • Improved CI performance
    • Boosted developer velocity

    Learn more 👉 bit.ly/3R9pSfZ

    #InfoQ #SoftwareArchitecture #Git #Monorepo #Optimization

  31. cut its backend monorepo from 87GB → 20GB.📉

    In collaboration with , they fixed a massive bottleneck by optimizing Git delta compression.

    The impact:
    • Reduced clone times
    • Improved CI performance
    • Boosted developer velocity

    Learn more 👉 bit.ly/3R9pSfZ

  32. stupid : tomshardware.com/tech-industry

    Storing backups (cold data) on the same volume or in the exact same environment as the production database isn't a backup; it's just a local copy. It is therefore a lack of forethought that led to this situation.

    I have never seen a company that allows just anyone to work on production servers. No matter the company, someone hired 2 days ago does not work on production; they read, they read some more, and they keep reading to understand the big picture. This is something AI cannot do.

    The safeguard that prevents AI from running amok must be built by design, not through instructions in a .md file or a .yaml configuration. Furthermore, even if a person validates the commands by hitting the "authorize" button, they are not to blame. This is what we call Taylorized factory behavior. The natural tendency will be to validate blindly because mental fatigue will set in; there is a term for this: validation fatigue or alert fatigue. The concept of Taylorism lies in the fragmentation of skills and the absence of critical thinking in a production line. This is the programmer's job with AI nowadays.

    An AI must work on servers that have absolutely no impact on production or ongoing work, almost as if it were working in parallel within its own sandbox environment. No matter the language model, things will get broken.

    AI is a loose cannon... capable of impressive feats of productivity, but a liability that lacks any global vision.

    #AI #SoftwareEngineering #DevOps #SysAdmin #Programming #CyberSecurity #TechDebt #SoftwareArchitecture #LLM #Taylorism

  33. 𝗖𝗣𝗦𝗔®-𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗟𝗲𝘃𝗲𝗹 𝗠𝗼𝗱𝘂𝗹𝗲 𝗚𝗥𝗘𝗘𝗡 – 𝗖𝘂𝗿𝗿𝗶𝗰𝘂𝗹𝘂𝗺 𝟮𝟬𝟮𝟲.𝟭 𝗥𝗲𝗹𝗲𝗮𝘀𝗲𝗱

    The new version of the #CPSA Advanced Level module GREEN is here! 🌱 It introduces a dedicated chapter on #AI & #Sustainability, updated learning goals, and new topics like carbon intensity and #GreenOps.

    Explore what’s new and download the latest curriculum 👉 t1p.de/50f5n

    #GreenIT #GreenSoftware #SoftwareArchitecture #iSAQB

  34. Studyng concurrent programming is essential for software developers. I deeply studied Android Asynctask many years ago and I found it's an implementation of Half Sync Half Async concurrent design pattern. Fast forward to 2026, and the same pattern I have implemented using Julia. Here's my write-up.
    Read ON...
    som-itsolutions.blogspot.com/2







  35. #Structurizr seems to no longer be free as a read-only centrally hosted documentation. That's a pity, I really liked using it. It was a useful communication tool in my current project. The license costs are a bit steep for using it as a read-only, centrally shared documentation. May be worth it in environments where visual architecture documentation is more of a first-class citizen.

    #coding #SoftwareArchitecture #opensource

  36. #SoftwareArchitecture makes your system fast ➔ #Culture keeps it fast 💪

    Sub-100ms APIs come from disciplined design:
    • Latency budgets & async fan-out
    • Layered caching & circuit breakers
    • Observability

    Long-term performance requires teams that treat #performance as a continuous responsibility - tracking p99, monitoring drift, and managing thread pools.

    🔗 bit.ly/4stLXUI

    #InfoQ #LowLatency

  37. In this #InfoQ #podcast, Matthew Liste talks about the art of building & managing software platforms.

    Platform services are the foundation of modern dev, but to succeed, they must master the "3 Ss":
    ✅ Stable
    ✅ Secure
    ✅ Scalable

    Discover why scaling often breaks due to resource contention and how to avoid it.

    🎧 Listen now: bit.ly/4eE0XLe

    #transcript included

    #SoftwareArchitecture #AIarchitecture

  38. I'm not saying AI tooling can't help. But if we're not measuring actual outcomes, we're just confirming our own bias. Start measuring. Compare cycle times, defect rates, rework. Don't let a feeling of speed substitute for evidence of speed.

    And make sure you're not feeding the AI hype industry with false promises.

    #SoftwareArchitecture #AI #SoftwareDesign #CognitiveBias

  39. #EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.

    In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.

    🎬 Watch now: bit.ly/41NZqLe

    📄 #transcript included

    #SoftwareArchitecture

  40. #EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.

    In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.

    🎬 Watch now: bit.ly/41NZqLe

    📄 #transcript included

    #SoftwareArchitecture

  41. #EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.

    In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.

    🎬 Watch now: bit.ly/41NZqLe

    📄 #transcript included

    #SoftwareArchitecture

  42. #EventDrivenArchitecture promises scalability, traceability, and resilience—but in a regulated, cloud-native banking environment it also introduces real challenges.

    In this #InfoQ video, Chris Tacey-Green explains the key #patterns used to build a real-time payment system in Azure, including inbox patterns, event sourcing, idempotency, and observability.

    🎬 Watch now: bit.ly/41NZqLe

    📄 #transcript included

    #SoftwareArchitecture