From e3fc73979af804abe8a58afb882e9ff3023e5379 Mon Sep 17 00:00:00 2001 From: Anthony Randall Date: Fri, 16 Apr 2021 14:11:27 -0600 Subject: [PATCH] Update README.md Updated doordash link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1fdd26e..9ab2a8f 100644 --- a/README.md +++ b/README.md @@ -393,7 +393,7 @@ Pact is an appropriate solution when both consumer(s) and provider can establish ### Does Pact only support synchronous HTTP/REST-based communication? -No, it is not restricted to HTTP/REST. Pact version 3.0 introduces messages for [services that communicate via event streams and message queues](https://github.com/Pact-foundation/Pact-specification/tree/version-3#version-30). There is also a blogpost by the makers of Pact, describing [Contract Testing Serverless and Asynchronous Applications](https://medium.com/@DoorDash/contract-testing-with-Pact-7cf108ced8c4). +No, it is not restricted to HTTP/REST. Pact version 3.0 introduces messages for [services that communicate via event streams and message queues](https://github.com/Pact-foundation/Pact-specification/tree/version-3#version-30). There is also a blogpost by the makers of Pact, describing [Contract Testing Serverless and Asynchronous Applications](https://doordash.engineering/2018/11/05/contract-testing-with-pact/). ### How can I deal with optional attributes/fields?