InfoQ1d ago

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: https://bit.ly/4eGoEB2

#InfoQ #SoftwareArchitecture #EventDrivenArchitecture #DistributedSystems

InfoQ2d ago

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: https://bit.ly/3Sgw4Rb

#SoftwareArchitecture #SociotechnicalArchitecture #DDD #ArchitectureDesign #DistributedSystems

Show threadHoldMyType3d ago
Might you have the time?
No but I have an opinion
#distributedsystems
https://vinitshahdeo.substack.com/p/why-clocks-lie-distributed-systems
Kanishka Naik5d ago

Building fintech systems that scale means designing for millions of users, real time transactions, strong consistency, and zero downtime. Event driven architecture, microservices, caching, and auto scaling are key. 🚀

#FinTech #Scalability #SystemDesign #DistributedSystems #SoftwareEngineering

Nicolas Fränkel 🇪🇺🇺🇦🇬🇪Jun 16

#Cache Stampede Prevention: Distributed Locking, Pub/Sub, and Request Coalescing

https://engineeringatscale.substack.com/p/cache-stampede-distributed-locking

#DistributedSystems

Stop Cache Stampedes with Distributed Locking

A practical guide to preventing cache stampedes — covering distributed locking, async Pub/Sub, and request coalescing with code examples.

Engineering At Scale
Show threadsqlrushJun 16
5/ I wrote the four hard problems up, broken down to code level (with links into the real source). Run RAC or any shared-storage cluster? I want your "this breaks under X."
Deep-dive: https://dev.to/sqlrush/rebuilding-oracle-racs-core-machinery-on-postgresql-the-four-problems-that-fight-back-2dhl
Repo (⭐): https://github.com/sqlrush/pgrac
#distributedsystems
Rebuilding Oracle RAC's core machinery on PostgreSQL — the four problems that fight back

pgrac is an attempt to build many of Oracle RAC's core capabilities — shared-everything storage,...

DEV Community
Hacker NewsJun 15

21 years and counting of 'eight fallacies of distributed computing' (2025)

https://blog.apnic.net/2025/12/08/21-years-and-counting-of-eight-fallacies-of-distributed-computing/

#HackerNews #Tech #DistributedSystems

21 years and counting of 'eight fallacies of distributed computing' | APNIC Blog

Eight long held and common beliefs about the network have been shown, time after time, to be false. What are they, and what do they mean?

APNIC Blog
Kanishka NaikJun 11

When the SRP is violated in a distributed fintech system, unrelated concerns become entangled. A change in one business rule forces retesting and redeployment of unrelated functionality—increasing risk and slowing delivery across the system.

#SOLID #FinTech #DistributedSystems

Kanishka NaikJun 11

Robert C. Martin defines SRP as: gather together things that change for the same reasons; separate things that change for different reasons. In fintech microservices, this rule determines where one service ends and another begins.

#SOLID #FinTech #DistributedSystems

Kanishka NaikJun 11

The Single Responsibility Principle (SRP), defined by Robert C. Martin, states a module should have one, and only one, reason to change. Applied to distributed systems, each service should encapsulate a single business concern.

#SOLID #FinTech #DistributedSystems