#distributed-systems — Public Fediverse posts

AI agents need durable execution, recovery, and provenance. DBOS may offer a practical database-backed runtime inside agent sandboxes. https://hackernoon.com/ai-agents-may-be-the-workload-dbos-was-waiting-for #distributedsystems

EDA is recommended for microservices. Then a real business process turns up, and inventory, payment and shipping must move together.

The usual reach is a workflow engine or the Saga pattern. A coordinator sends commands and waits for replies. But that is request-response, even over Kafka. Command-driven, not event-driven.

A requirement, or a habit carried over from monoliths? My code.talks talk makes the case for choreography.

Hamburg, 5 Nov.

#EventDrivenArchitecture #DistributedSystems

What happens when architectural assumptions collide with global reality?

In this #InfoQ talk, Kasia Trapszo breaks down how #Netflix evolved its commerce platform over a decade of global hypergrowth - from a monolithic U.S. credit-card system to a resilient, globally distributed architecture.

The core takeaway: Great systems don't survive because they were perfectly designed. They survive because they keep evolving as reality changes.

🍿 Watch the full talk: https://www.infoq.com/presentations/netflix-commerce-architecture-evolution/

#SoftwareArchitecture #SystemDesign #DistributedSystems #EngineeringLeadership

Publish-Subscribe (pub/sub) is a messaging pattern that decouples publishers from subscribers through a broker. Publishers send messages without knowing who receives them; subscribers get only messages matching their interests.

#PubSub #DistributedSystems #Fintech

RE: https://mastodon.gamedev.place/@Brahvim/117173199873033837

Any Networking and Distributed Systems people
who'd like to slap some actual intellect into
my blabber please <3?

#distsys #distributed #systems #system #distributedsystems #distributed_systems #network #engineering #radio #telecom #internet #infrastructure

Wes Chow (Mini) on Tiered Replication: A Cost-effective Alternative to Full Cluster Geo-replication (2016)

https://www.youtube.com/watch?v=JMmV4wwXvCs

#TiredReplication #DistributedSystems #CopySets

Distributed system failures often mirror structural engineering collapses: a single local weakness can trigger a catastrophic cascading failure.

Drawing on real-world examples, Sam Newman examines the mechanics of progressive failure - and outlines 3 key strategies for building resilient architectures:
• Reduce hazards
• Strengthen components
• Reduce interconnection

🎬 Watch now: https://bit.ly/4xrGmjZ

#SoftwareArchitecture #DistributedSystems #SystemResilience #InfoQ

GAAS - Git as a Storage

Im sure im not the first consider this approach, but i would like to share a demo for clarity and transparancy. No need to debug, its far from finished and there is much to do.

Im working on a P2P messaging app and generally up until recently i thought in such a system, if a peer is offline, you cant send a message... It wouldnt be "decentralized" if there was some central queue of messages.

It took embarassingly long, but then it hit me... git... just regular git is a decentralized database. Github/Forgejo isnt decentralized, but git can have multiple remotes that can act as redundencies.

In my setup i need the ability for others to be abe to read and only i should be able to write to it. That functionality is out-of-the-box in git.

Git is also pretty standardized so there are many providers if users want to move away from Github.

The storage requirements for my project are fairly small. Typically small text messages. The data itself thats publicly readable would be encrypted (aiming to keep aligned to Kerkhoffs principles).

Code: https://github.com/positive-intentions/git

Demo: https://positive-intentions.github.io/git/demo/gui/git/storage

There is much more to improve and consider there for things like encrypting the data at rest.

I have concerns around if providers like GitHub, Codeberg and Gitlab might see the way my app works as fundamentally violating their terms-of-service. I'll have to consider providing a backend service for this which I've generally tried to avoid.

IMPORTANT DISCLAIMER: This is open source for transparency, testing and demo purposes only. it is still a work in progress and far from finished. You should not use it on any sensitive repositories. There WILL BE breaking changes. Use responsibly.

#Git #Decentralized #OpenSource #Cryptography #Privacy #SoftwareArchitecture #DistributedSystems

I found Flamme in r/Quarkus because its author asked people to test it and send feedback. Fair enough.

I moved one component in a four-stage Quarkus pipeline from local memory to NATS with configuration. The Java code and JAR stayed the same.

Then I added a second worker, forced a component failure, and stopped NATS. The happy path worked. Replica and failure semantics need more attention.

https://www.the-main-thread.com/p/quarkus-flamme-deployment-topologies

#Java #Quarkus #NATS #DistributedSystems

Michael Pigott on Toward a Generic Fault Tolerance Technique [PWL NYC] (2021)

https://www.youtube.com/watch?v=W55mk2CivJo

#computerscience #distributedsystems #networks

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

This week at SIGCOMM, Inho Choi will present a paper about a fast TCP migration and load balancing system called Capybara, which means it’s time for… another episode of Distributed Systems Explained by ̶C̶a̶t̶s̶ Capybaras!

L4 load balancers are fast, scalable, and widely used in cloud systems: when a new connection arrives, the load balancer picks a server for it. For our purposes, connections are birds and servers are capybaras.

This bird has been assigned to a server.

[🧵, 1/9]

#distributedsystems #networking #capybara #sigcomm #distributedsystemsexplainedbycats

PWLSF - 08/2014 - Peter Alvaro: Using Reasoning about Knowledge to Analyze Distrtibuted Systems (2014)

https://www.youtube.com/watch?v=7U0qPmEpbSI

#ReasoningAboutKnowledge #distributedsystems #Software

This pattern also has to plan for cancellation, retries, and cleanup, not just the happy path of request, poll, and result.

#Fintech #DistributedSystems

On local networks, Fire-and-Forget messages can travel over UDP, while most messaging systems, such as JMS-compliant brokers, provide this style by default.

#Fintech #DistributedSystems

How Netflix redesigned its Service Topology pipeline to scale real-time service mapping:
🔹 Separates resolution from enrichment & persistence
🔹 Propagates backpressure to Kafka (zero record drops)
🔹 Swaps gRPC for SSE on high-volume internal transfers

📖 Read the full deep dive on #InfoQ ⇨ https://bit.ly/4x0Hrzc

#DistributedSystems #SoftwareArchitecture #Kafka #Microservices

ATProto for Distributed Systems Engineers

https://atproto.com/articles/atproto-for-distsys-engineers

Comments: https://news.ycombinator.com/item?id=49202912

#HackerNews #ATProto #DistributedSystems #Engineers #TechInnovation #SoftwareDevelopment #Networking

What I’ve been reading (and watching) week ending 9 August https://jchyip.medium.com/what-ive-been-reading-and-watching-week-ending-9-august-1ab6b2dde859 #AI #DistributedSystems #science #engineering #SoftwareEngineering #cybersecurity #ProductManagement