#distsys — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #distsys, aggregated by home.social.
-
Choreographing multi-agent interactions 🤖💃
I’ve been thinking about multi-agent systems less as prompt chains and more as distributed systems. Once the workflow stops being toy-sized, the hard part is no longer getting a response from a model. It is making the whole topology behave predictably.
I wrote a draft about how I’m using choreographic programming and strong types to make agent interactions more predictable. It traces a path from UniChorn (my port of HasChor) to a Ralph-loop experiment leveraging the new research-backed CP libraries like
choreography-ts, a small Pi-based library for schema-constrained turns, and a NATS transport for running the choreography across locations.This is just the initial post, and I will write more as I am working on more interesting stuff on top of this foundation.
-
💬 Matrix and XMPP: Thoughts on Improving Messaging Protocols – Part 1
｢ If the Matrix network were to scale massively, with many nodes and conversations, it would encounter the same growth challenges as blockchain protocols. Each node must store a copy of the conversation, and the amount of replication depends on the number of conversations and nodes globally. As these numbers grow, so does the replication factor ｣
https://www.process-one.net/blog/matrix-and-xmpp-thoughts-on-improving-messaging-protocols-part-1/
-
💬 Matrix and XMPP: Thoughts on Improving Messaging Protocols – Part 1
｢ If the Matrix network were to scale massively, with many nodes and conversations, it would encounter the same growth challenges as blockchain protocols. Each node must store a copy of the conversation, and the amount of replication depends on the number of conversations and nodes globally. As these numbers grow, so does the replication factor ｣
https://www.process-one.net/blog/matrix-and-xmpp-thoughts-on-improving-messaging-protocols-part-1/
-
💬 Matrix and XMPP: Thoughts on Improving Messaging Protocols – Part 1
｢ If the Matrix network were to scale massively, with many nodes and conversations, it would encounter the same growth challenges as blockchain protocols. Each node must store a copy of the conversation, and the amount of replication depends on the number of conversations and nodes globally. As these numbers grow, so does the replication factor ｣
https://www.process-one.net/blog/matrix-and-xmpp-thoughts-on-improving-messaging-protocols-part-1/
-
💬 Matrix and XMPP: Thoughts on Improving Messaging Protocols – Part 1
｢ If the Matrix network were to scale massively, with many nodes and conversations, it would encounter the same growth challenges as blockchain protocols. Each node must store a copy of the conversation, and the amount of replication depends on the number of conversations and nodes globally. As these numbers grow, so does the replication factor ｣
https://www.process-one.net/blog/matrix-and-xmpp-thoughts-on-improving-messaging-protocols-part-1/
-
💬 Matrix and XMPP: Thoughts on Improving Messaging Protocols – Part 1
｢ If the Matrix network were to scale massively, with many nodes and conversations, it would encounter the same growth challenges as blockchain protocols. Each node must store a copy of the conversation, and the amount of replication depends on the number of conversations and nodes globally. As these numbers grow, so does the replication factor ｣
https://www.process-one.net/blog/matrix-and-xmpp-thoughts-on-improving-messaging-protocols-part-1/
-
🔀 Categorizing How Distributed Databases Utilize Consensus Algorithms
— Adam Prout -
🔀 Categorizing How Distributed Databases Utilize Consensus Algorithms
— Adam Prout -
🔀 Categorizing How Distributed Databases Utilize Consensus Algorithms
— Adam Prout -
🔀 Categorizing How Distributed Databases Utilize Consensus Algorithms
— Adam Prout -
🔀 Categorizing How Distributed Databases Utilize Consensus Algorithms
— Adam Prout -
A three way light switch is one in which the wiring of a switch you didn't even know existed can render your own switch unusable.
#DistSys #HomeImprovement -
A three way light switch is one in which the wiring of a switch you didn't even know existed can render your own switch unusable.
#DistSys #HomeImprovement -
A three way light switch is one in which the wiring of a switch you didn't even know existed can render your own switch unusable.
#DistSys #HomeImprovement -
A three way light switch is one in which the wiring of a switch you didn't even know existed can render your own switch unusable.
#DistSys #HomeImprovement -
A three way light switch is one in which the wiring of a switch you didn't even know existed can render your own switch unusable.
#DistSys #HomeImprovement -
Predicting the Future of Distributed Systems.
[Object storage and new programming models 🤔]
https://blog.colinbreck.com/predicting-the-future-of-distributed-systems/
#DistSys -
Predicting the Future of Distributed Systems.
[Object storage and new programming models 🤔]
https://blog.colinbreck.com/predicting-the-future-of-distributed-systems/
#DistSys -
Predicting the Future of Distributed Systems.
[Object storage and new programming models 🤔]
https://blog.colinbreck.com/predicting-the-future-of-distributed-systems/
#DistSys -
Predicting the Future of Distributed Systems.
[Object storage and new programming models 🤔]
https://blog.colinbreck.com/predicting-the-future-of-distributed-systems/
#DistSys -
Predicting the Future of Distributed Systems.
[Object storage and new programming models 🤔]
https://blog.colinbreck.com/predicting-the-future-of-distributed-systems/
#DistSys -
Are you interested in and posting on topics like: #Messaging, #MQTT, #IoT, #OpenSource, #DistSys, #Erlang, OSS business models or anything related?
Let us know by Like of Repost... We want to follow you! :) :vernemq: -
Are you interested in and posting on topics like: #Messaging, #MQTT, #IoT, #OpenSource, #DistSys, #Erlang, OSS business models or anything related?
Let us know by Like of Repost... We want to follow you! :) :vernemq: -
Are you interested in and posting on topics like: #Messaging, #MQTT, #IoT, #OpenSource, #DistSys, #Erlang, OSS business models or anything related?
Let us know by Like of Repost... We want to follow you! :) :vernemq: -
Are you interested in and posting on topics like: #Messaging, #MQTT, #IoT, #OpenSource, #DistSys, #Erlang, OSS business models or anything related?
Let us know by Like of Repost... We want to follow you! :) :vernemq: -
Are you interested in and posting on topics like: #Messaging, #MQTT, #IoT, #OpenSource, #DistSys, #Erlang, OSS business models or anything related?
Let us know by Like of Repost... We want to follow you! :) :vernemq: -
Just discovered Radicle (https://radicle.xyz/), which is a peer-to-peer git forge. It has its own custom gossip protocol to propagate repo changes through the different instances.
Even if i LOVE gossip protocols, I'm still a little bit confused about all of these "distributed" forges, mainly because git is already distributed by default (https://git-scm.com/about/distributed).
Radicle authors are answering this question in their FAQ (https://radicle.xyz/faq):
```
While Git is designed in some way for peer-to-peer interactions, there is no deployment of it that works that way. All deployments use the client-server model because Git lacks functionality to be deployed as-is in a peer-to-peer network.For one, it has no way of verifying that the repository you downloaded after a git clone is the one you asked for, which means you need to clone from a trusted source (ie. a known server). This isn’t compatible with peer-to-peer in any useful way.
Radicle solves this by assigning stable identities to repositories that can be verified locally, allowing repositories to be served by untrusted parties.
```I'm still not convinced though, I think it's adding lots of complexity to an already complex system.
-
Just discovered Radicle (https://radicle.xyz/), which is a peer-to-peer git forge. It has its own custom gossip protocol to propagate repo changes through the different instances.
Even if i LOVE gossip protocols, I'm still a little bit confused about all of these "distributed" forges, mainly because git is already distributed by default (https://git-scm.com/about/distributed).
Radicle authors are answering this question in their FAQ (https://radicle.xyz/faq):
```
While Git is designed in some way for peer-to-peer interactions, there is no deployment of it that works that way. All deployments use the client-server model because Git lacks functionality to be deployed as-is in a peer-to-peer network.For one, it has no way of verifying that the repository you downloaded after a git clone is the one you asked for, which means you need to clone from a trusted source (ie. a known server). This isn’t compatible with peer-to-peer in any useful way.
Radicle solves this by assigning stable identities to repositories that can be verified locally, allowing repositories to be served by untrusted parties.
```I'm still not convinced though, I think it's adding lots of complexity to an already complex system.
-
Just came across Epoxy, a protocol that aims to allow transactions between different datastores. I haven't read the paper yet (but I will), as these are some serious allegations :D
-
Just came across Epoxy, a protocol that aims to allow transactions between different datastores. I haven't read the paper yet (but I will), as these are some serious allegations :D
-
Using Promise Theory to solve the distributed consensus problem.
https://mark-burgess-oslo-mb.medium.com/using-promise-theory-to-solve-the-distributed-consensus-problem-4cc2116f24e1
#PromiseTheory #DistSys #Consensus -
Using Promise Theory to solve the distributed consensus problem.
https://mark-burgess-oslo-mb.medium.com/using-promise-theory-to-solve-the-distributed-consensus-problem-4cc2116f24e1
#PromiseTheory #DistSys #Consensus -
Using Promise Theory to solve the distributed consensus problem.
https://mark-burgess-oslo-mb.medium.com/using-promise-theory-to-solve-the-distributed-consensus-problem-4cc2116f24e1
#PromiseTheory #DistSys #Consensus -
Using Promise Theory to solve the distributed consensus problem.
https://mark-burgess-oslo-mb.medium.com/using-promise-theory-to-solve-the-distributed-consensus-problem-4cc2116f24e1
#PromiseTheory #DistSys #Consensus -
Using Promise Theory to solve the distributed consensus problem.
https://mark-burgess-oslo-mb.medium.com/using-promise-theory-to-solve-the-distributed-consensus-problem-4cc2116f24e1
#PromiseTheory #DistSys #Consensus -
Sometimes, the devil's lies in the details. Having a #distsys capable of diagnosis itself is such a relieve 🤩
```
Performance limited by process: Storage server performance (storage queue)
```
Thanks #FoundationDB -
Sometimes, the devil's lies in the details. Having a #distsys capable of diagnosis itself is such a relieve 🤩
```
Performance limited by process: Storage server performance (storage queue)
```
Thanks #FoundationDB -
Sometimes, the devil's lies in the details. Having a #distsys capable of diagnosis itself is such a relieve 🤩
```
Performance limited by process: Storage server performance (storage queue)
```
Thanks #FoundationDB -
Sometimes, the devil's lies in the details. Having a #distsys capable of diagnosis itself is such a relieve 🤩
```
Performance limited by process: Storage server performance (storage queue)
```
Thanks #FoundationDB -
Sometimes, the devil's lies in the details. Having a #distsys capable of diagnosis itself is such a relieve 🤩
```
Performance limited by process: Storage server performance (storage queue)
```
Thanks #FoundationDB
