Caitie McCaffrey is a Backend Brat and Distributed Systems Diva. She currently is the Architect & Developer Manager of the Azure Sphere Security Services. She’s been with the Azure Sphere project since it’s early days in Microsoft Research, and has had the great privilege of building out the services and the team to help secure IoT. Caitie has spent her career building large scale services and systems at Twitter, 343 Industries, Microsoft Game Studios, and HBO. Caitie has credits on several video games including Gears of War 2, Gears of War 3, Halo 4, and Halo 5. She maintains a blog at “CaitieM.com”:https://caitiem.com/ and frequently discusses technology on Twitter https://speakerdeck.com/caitiem20 2015-09-27 14:04:10 -0400 Microservices have become the defacto architecture pattern for building services. However separating business logic into small services that operate with a single logical data set has introduced consistency challenges. Previous attempts to solve this problem like two phase commit have not been widely adopted due to availability and liveness issues. Instead developers implement feral concurrency control mechanism. This technique can be error prone, and often results in “Death Star” architectures which rely on chained calls to enforce application invariants. These architectures become more complicated over time, and are difficult to modify and extend, and often don't correctly handle all failure scenarios. In this talk I propose a new solution for this problem, Distributed Sagas, a protocol for coordinating requests among multiple micro services, while ensuring application invariants. Microservices have become the defacto architecture pattern for building services. However separating business logic into small services that operate with a single logical data set has introduced consistency challenges. Previous attempts to solve this problem like two phase commit have not been widely adopted due to availability and liveness issues. Instead developers implement feral concurrency control mechanism. This technique can be error prone, and often results in “Death Star” architectures which rely on chained calls to enforce application invariants. These architectures become more complicated over time, and are difficult to modify and extend, and often don't correctly handle all failure scenarios. In this talk I propose a new solution for this problem, Distributed Sagas, a protocol for coordinating requests among multiple micro services, while ensuring application invariants. Fri, 19 May 2017 00:00:00 -0400 https://speakerdeck.com/caitiem20/distributed-sagas-a-protocol-for-coordinating-microservices https://speakerdeck.com/caitiem20/distributed-sagas-a-protocol-for-coordinating-microservices Mon, 24 Apr 2017 00:00:00 -0400 https://speakerdeck.com/caitiem20/the-path-towards-simplifying-consistency-in-distributed-systems https://speakerdeck.com/caitiem20/the-path-towards-simplifying-consistency-in-distributed-systems Fri, 20 Jan 2017 00:00:00 -0500 https://speakerdeck.com/caitiem20/argus-papers-we-love https://speakerdeck.com/caitiem20/argus-papers-we-love Given at YOW Sydney December 2016 References: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem Given at YOW Sydney December 2016 References: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem Thu, 08 Dec 2016 00:00:00 -0500 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-3 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-3 Given at Women Who Code Sydney IT meetup Resources: https://github.com/CaitieM20/Talks/tree/master/SoWeHearYouLikePapers Given at Women Who Code Sydney IT meetup Resources: https://github.com/CaitieM20/Talks/tree/master/SoWeHearYouLikePapers Wed, 07 Dec 2016 00:00:00 -0500 https://speakerdeck.com/caitiem20/we-hear-you-like-papers-eventual-consistency https://speakerdeck.com/caitiem20/we-hear-you-like-papers-eventual-consistency YOW Brisbane References & Credits: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem YOW Brisbane References & Credits: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem Mon, 05 Dec 2016 00:00:00 -0500 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-2 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-2 YOW 2016: Melbourne References: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem YOW 2016: Melbourne References: https://github.com/CaitieM20/Talks/tree/master/TheVerificationOfADistributedSystem Wed, 30 Nov 2016 00:00:00 -0500 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-1 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system-1 Given at CodeMesh 2016 Given at CodeMesh 2016 Thu, 03 Nov 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/a-brief-history-of-distributed-programming-rpc https://speakerdeck.com/caitiem20/a-brief-history-of-distributed-programming-rpc Slides from Scaling Stateful Services Talk given at Nike Tech Talk 8/11/16 Slides from Scaling Stateful Services Talk given at Nike Tech Talk 8/11/16 Fri, 12 Aug 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/building-scalable-stateful-services-1 https://speakerdeck.com/caitiem20/building-scalable-stateful-services-1 Detection of Mutual Inconsistency in Distributed Systems Detection of Mutual Inconsistency in Distributed Systems Tue, 28 Jun 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/papers-we-love-pdx https://speakerdeck.com/caitiem20/papers-we-love-pdx Sun, 26 Jun 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/tackling-alert-fatigue https://speakerdeck.com/caitiem20/tackling-alert-fatigue Tue, 14 Jun 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/pwl-ny-simple-testing-can-prevent-most-critical-failures https://speakerdeck.com/caitiem20/pwl-ny-simple-testing-can-prevent-most-critical-failures Distributed Systems are difficult to build and test for two main reasons: partial failure & asynchrony. These two realities of distributed systems must be addressed to create a correct system, and often times the resulting systems have a high degree of complexity. Because of this complexity, testing and verifying these systems is critically important. In this talk we will discuss strategies for proving a system is correct, like formal methods, and less strenuous methods of testing which can help increase our confidence that our systems are doing the right thing. Distributed Systems are difficult to build and test for two main reasons: partial failure & asynchrony. These two realities of distributed systems must be addressed to create a correct system, and often times the resulting systems have a high degree of complexity. Because of this complexity, testing and verifying these systems is critically important. In this talk we will discuss strategies for proving a system is correct, like formal methods, and less strenuous methods of testing which can help increase our confidence that our systems are doing the right thing. Tue, 14 Jun 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/qcon-newyork-2016-the-verification-of-a-distributed-system https://speakerdeck.com/caitiem20/qcon-newyork-2016-the-verification-of-a-distributed-system Goto Chicago 2016 References: https://github.com/CaitieM20/TheVerificationOfDistributedSystem Goto Chicago 2016 References: https://github.com/CaitieM20/TheVerificationOfDistributedSystem Tue, 24 May 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system https://speakerdeck.com/caitiem20/the-verification-of-a-distributed-system The Stateless Service design principle has become ubiquitous in the tech industry for creating horizontally scalable services. However our applications do have state, we just have moved all of it to caches and databases. Today as applications are becoming more data intensive and request latencies are expected to be incredibly low, we’d like the benefits of stateful services, like data locality and sticky consistency. In this talk I will address the benefits of stateful services, how to build them so that they scale, and discuss distributed and scalable services in the real world that implement these techniques successfully. The Stateless Service design principle has become ubiquitous in the tech industry for creating horizontally scalable services. However our applications do have state, we just have moved all of it to caches and databases. Today as applications are becoming more data intensive and request latencies are expected to be incredibly low, we’d like the benefits of stateful services, like data locality and sticky consistency. In this talk I will address the benefits of stateful services, how to build them so that they scale, and discuss distributed and scalable services in the real world that implement these techniques successfully. Fri, 29 Apr 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/craftconf-2016-building-scalable-stateful-services https://speakerdeck.com/caitiem20/craftconf-2016-building-scalable-stateful-services A talk about Sagas https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf And the application of them in Distributed Systems A talk about Sagas https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf And the application of them in Distributed Systems Fri, 18 Mar 2016 00:00:00 -0400 https://speakerdeck.com/caitiem20/papers-we-love-sf-sagas https://speakerdeck.com/caitiem20/papers-we-love-sf-sagas Every minute Twitter’s Observability stack processes 1.5+ billion metrics in order to provide Visibility into Twitter’s distributed microservices architecture. In this talk will focus on some of the challenges associated with building and running this large scale distributed system. We will also focus on lessons learned and how to build services that scale that are applicable for services of any size. Every minute Twitter’s Observability stack processes 1.5+ billion metrics in order to provide Visibility into Twitter’s distributed microservices architecture. In this talk will focus on some of the challenges associated with building and running this large scale distributed system. We will also focus on lessons learned and how to build services that scale that are applicable for services of any size. Wed, 21 Oct 2015 00:00:00 -0400 https://speakerdeck.com/caitiem20/of-the-order-of-billions-building-observability-at-twitter https://speakerdeck.com/caitiem20/of-the-order-of-billions-building-observability-at-twitter The Stateless Service design principle has become ubiquitous in the tech industry for creating horizontally scalable services. However our applications do have state, we just have moved all of it to caches and databases. Today as applications are becoming more data intensive and request latencies are expected to be incredibly low, we’d like the benefits of stateful services, like data locality and sticky consistency. In this talk I will address the benefits of stateful services, how to build them so that they scale, and discuss projects from Halo and Twitter of highly distributed and scalable services that implement these techniques successfully. The Stateless Service design principle has become ubiquitous in the tech industry for creating horizontally scalable services. However our applications do have state, we just have moved all of it to caches and databases. Today as applications are becoming more data intensive and request latencies are expected to be incredibly low, we’d like the benefits of stateful services, like data locality and sticky consistency. In this talk I will address the benefits of stateful services, how to build them so that they scale, and discuss projects from Halo and Twitter of highly distributed and scalable services that implement these techniques successfully. Sun, 27 Sep 2015 00:00:00 -0400 https://speakerdeck.com/caitiem20/building-scalable-stateful-services https://speakerdeck.com/caitiem20/building-scalable-stateful-services