home.social

#distsys — Public Fediverse posts

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

fetched live
  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 」

    process-one.net/blog/matrix-an

    #matrix #xmpp #distsys

  2. 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
  3. Predicting the Future of Distributed Systems.
    [Object storage and new programming models 🤔]
    blog.colinbreck.com/predicting
    #DistSys

  4. Are you interested in and posting on topics like: , , , , , , OSS business models or anything related?
    Let us know by Like of Repost... We want to follow you! :) :vernemq:

  5. Just discovered Radicle (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 (git-scm.com/about/distributed).

    Radicle authors are answering this question in their FAQ (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.

    #git #distsys

  6. 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

    petereliaskraft.net/blog/epoxy

    #distsys

  7. Are you interested in messaging, message brokers, , and (distributed systems) in general?
    Like or re-post to let us know... we want to connect and learn from you! :) :vernemq:

  8. hello fedimortals, what are the most beautiful computer things to you — whether in the realm of #software, #hardware, #networks, #distsys, etc.?

    what pleases your aesthetic senses? what feels poetic? what fills you with awe, wonder, or excitement?

    serious answers preferred 🖤

  9. Sometimes, the devil's lies in the details. Having a capable of diagnosis itself is such a relieve 🤩
    ```
    Performance limited by process: Storage server performance (storage queue)
    ```
    Thanks

  10. never was a specification for distributed messaging. Its origins date back to when a server was one server with one CPU. Modern brokers like VerneMQ offer distributed messaging, but there are always decisions & tradeoffs.
    A fascinating topic to us! :)

  11. I got nerdsniped by @tef & @sushee to demonstrate how relatively easy it is to build a CRAQ (timilearning.com/posts/mit-6.8) system atop @couchdb — Showing that as much as CouchDB is a distributed database in itself, it is also a very nice toolkit to build other kinds of distributed databases with it :)

    The demo is in Node.js with some private JS/HTTP API glue that is not relevant to the demo: gist.github.com/janl/d0ba35446

    Let me know if you ahave any questions.

    #CouchDB #DistSys #Databases #NoSQL #CRAQ

  12. I just published github.com/lant/maelstrom-java in the central maven repository.

    This project is a simple java wrapper over the Maelstrom distributed system workbench. (github.com/jepsen-io/maelstrom)

    If you want to play with Maelstrom using JVM languages, this library will hopefully take away the pain of writing tons of boilerplate.

    #distsys

  13. @quinn @causalislands

    paging @muratdemirbas an intertwined bunch of different musical, art, and philosophical references, to then go deep on #distSys ;) original !!!

  14. I just completed challenge 3 (a-e) and I've got some nice code that works but I'm not happy with it. I'm also not happy with the grading mechanism being number of messages not size of messages. I feel like I've cheated.

    The challenge is to keep X number of nodes in sync with these numeric broadcast messages that go to random nodes, so it with network partitions and do it without flooding your network. Eventual consistency.

    #distsys

  15. Follow-up poll w.r.t. unique identifier generation in distributed systems... What other properties of the identifiers are important to you?

    #distsys

  16. Your preferred method for generating unique identifiers in a medium to large distributed system?

    #uuid
    #ULID
    #snowflakeid
    #hashids
    #nanoid
    #distsys

  17. Next week is the February 2022 edition of Fission's #distsys reading group hosted by @expede.

    The paper being reviewed is "Metastable Failures in Distributed Systems”, presented at Hot Topics in Operating Systems (HotOS ’21) last year.