Think your service is fault tolerant? Well this talk is about proving it with protocol level test doubles. This talk will not be about in-process mocking, spying or stubbing. Instead, we will describe the benefits of using test doubles at the protocol level. When you are building a service, either monolithic or micro, you will have external dependences such as databases, message queues and/or HTTP services. The key idea is that in order to achieve fault-tolerance you must test failure scenarios across all your external dependencies and, crucially, network failures that may occur between your application and these other services
YOU MAY ALSO LIKE:
Think your software is fault tolerant? Prove it
Christopher is a Senior Engineer at Lightbend. He is currently on the core Akka team responsible for developing Akka (https://akka.io/), Akka Http, Akka Streams, Reactive Kafka and Alpakka (https://github.com/akka/alpakka). He has previously built trading systems, online television platforms and worked extensively with Apache Cassandra. Likes: Scala, Java, the JVM, Akka, distributed databases, XP, TDD, Pairing. Dislikes: Untested software and code ownership.