Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Highly available, distributed & resilient softw...

Yohan Lasorsa
November 25, 2020

Highly available, distributed & resilient software... team

Design patterns for building distributed, resilient, and scalable web applications are well known today. However, setting up a project organization to build them effectively remains a challenge, especially when the team itself is distributed. The "human" factor is a source of problems that are difficult to predict.

What would happen if you could take inspiration from the architecture of your applications to improve the communication of your teams?

Microservices, message queues, load balancers, caches, sharding, decoupling... These architectural concepts are designed to improve digital exchanges within our apps, and above all to anticipate and manage failures.
By modeling the exchanges within your team as software architecture, we will see how these design patterns can also be effective in solving our communication issues, very human this time.

Yohan Lasorsa

November 25, 2020
Tweet

More Decks by Yohan Lasorsa

Other Decks in Technology

Transcript

  1. Highly available, Highly available, Highly available, distributed distributed distributed &

    resilient software... & resilient software... & resilient software... team team team | Yohan Lasorsa | @sinedied
  2. What this talk is (really) about What this talk is

    (really) about What this talk is (really) about @sinedied
  3. Who am I? Yohan Lasorsa Web tech geek, OSS maintainer,

    DIY lover @sinedied [ Cloud Developer Advocate @ ]
  4. CDN / Cache Aggregation Centralization T ransaction All hands, Recordings,

    Minutes nohello.com Emails w/ Conte xt Knowledgebase (wiki) Meetings PM, T eam Lead, Manager PM, T eam Lead, Manager Backlog @sinedied
  5. Scaling Microservices Small teams Recruitment, New teams Sharding Map/Reduce Autonomy

    Decoupling T eam specialty Manager "Ask Me Anything", Minutes, Debriefs T eam-specific OKRs @sinedied
  6. Load balancing / failover Backup Health checks Teammates Teammates :)

    Queue Monitoring Retry Status reports, Pings, Surveys, eNPS, 1:1 Manager, Teammates OKRs, Shared dashboard, Transparency! Backlog, Todo list Time zones, Docs, Pair prog., Sharing Knowledgebase, Docs Handover emails Follow-up, Try different channels Leadership team @sinedied