home.social

#distributedsystem — Public Fediverse posts

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

fetched live
  1. Reliability.
    Consistent results under load.

    #SiteReliabilityEngineering.
    ..

    Your team is a #DistributedSystem.
    Language is the transport layer.
    And truth is local.
    (Site.)

    #TechDebt slows down delivery.
    Decisions are unowned.
    And people burn out.
    (Reliability.)

    Divergent realities are a primary (in)variant of human systems.
    Linguistic precision counters entropy accruing ambiguity.
    And coherence is regulative.
    (Engineering.)

    ..

    Intrigued?
    I write about language, technology and #HumanSystems.
    👉 systemic.engineering/trauma-aw

    #SystemicEngineering #SocioTechSRE #SREforHumans #SRE

  2. Reliability.
    Consistent results under load.

    #SiteReliabilityEngineering.
    ..

    Your team is a #DistributedSystem.
    Language is the transport layer.
    And truth is local.
    (Site.)

    #TechDebt slows down delivery.
    Decisions are unowned.
    And people burn out.
    (Reliability.)

    Divergent realities are a primary (in)variant of human systems.
    Linguistic precision counters entropy accruing ambiguity.
    And coherence is regulative.
    (Engineering.)

    ..

    Intrigued?
    I write about language, technology and #HumanSystems.
    👉 systemic.engineering/trauma-aw

    #SystemicEngineering #SocioTechSRE #SREforHumans #SRE

  3. What are the 3 fundamental ideas every developer should know if they're unfortunate enough to have to work on a #DistributedSystem?

    In this #InfoQ video, Sam Newman breaks down the essentials:
    1️⃣ Timeouts – “giving up”
    2️⃣ Retries – “trying again”
    3️⃣ Idempotency – “making it all a bit safe”

    🎥 Watch the video to dive deeper: bit.ly/41dPAm0

    📄 #transcript included

    #SoftwareArchitecture #Microservices #Resilience

  4. What are the 3 fundamental ideas every developer should know if they're unfortunate enough to have to work on a ?

    In this video, Sam Newman breaks down the essentials:
    1️⃣ Timeouts – “giving up”
    2️⃣ Retries – “trying again”
    3️⃣ Idempotency – “making it all a bit safe”

    🎥 Watch the video to dive deeper: bit.ly/41dPAm0

    📄 included

  5. ⚙️ Building resilience in distributed systems just got easier.

    Our latest blog explores durable computing—a powerful approach to managing state, failure recovery and consistency in the cloud-native world.

    🔗 Read more: ter.li/xfw1oa

    #Tech #AI #DistributedSystem #DistributedComputing

  6. ⚙️ Building resilience in distributed systems just got easier.

    Our latest blog explores durable computing—a powerful approach to managing state, failure recovery and consistency in the cloud-native world.

    🔗 Read more: ter.li/xfw1oa

    #Tech #AI #DistributedSystem #DistributedComputing

  7. - Divulged into the conception and making of a visual book on software architecture in this episode: ter.li/ooqott

    - Learned about new approaches and techniques to successfully run through a distributed system in this episode: ter.li/nza3zq

    2/2

    #DistributedSystem #SoftwareArchitecture #SoftwareDevelopment

  8. - Divulged into the conception and making of a visual book on software architecture in this episode: ter.li/ooqott

    - Learned about new approaches and techniques to successfully run through a distributed system in this episode: ter.li/nza3zq

    2/2

    #DistributedSystem #SoftwareArchitecture #SoftwareDevelopment

  9. CW: Birdsite

    I've seen a lot of confusion on Twitter regarding the risk for it going down permanently.

    Thing is: #Twitter is a huge #DistributedSystem. Systems like these have a near infinite number of possible states they can be in - some of them well understood and stable but most unknown and varying degrees of broken.

  10. CW: Birdsite

    I've seen a lot of confusion on Twitter regarding the risk for it going down permanently.

    Thing is: #Twitter is a huge #DistributedSystem. Systems like these have a near infinite number of possible states they can be in - some of them well understood and stable but most unknown and varying degrees of broken.

  11. People are sometimes afraid of ’s complexity because it’s a .

    But client-server is a many-to-one relationship, so servers are naturally bottlenecks. Scaling them quickly becomes a distributed system of shared state with complexity equal to or greater than any p2p design.

  12. Funny observation: the design of #ActivityPub is very close to X.500 (ITU-T directory standard first published 1988).

    #DistributedSystem: if it looks like a 🦆 , talks like a 🦆 , ...