Contract Driven Development – Deploying your MicroServices independently without integration testing
@@ -355,14 +355,14 @@
Presentation summary<
-
Tired of dealing with seemingly innocuous data type mismatches, missing parameters, etc. in API signature that wreak havoc on MicroServices deployments late in the development cycle?
Join us in this talk where we will share our experience about how we leverage API Specification Standards such as OpenAPI to identify such compatibility issues early in the development cycle and in the process effectively eliminating integration tests. We will also be sharing our journey about how necessity drove us to come up with the “Contract Driven Development” approach and Specmatic, an open source tool that embodies the same to promote collaboration among teams, lower cycle time and deploying services independently.
Contract Driven Development – Deploying your MicroServices independently without integration testing
@@ -355,14 +355,14 @@
Presentation summary<
-
Tired of dealing with seemingly innocuous data type mismatches, missing parameters, etc. in API signature that wreak havoc on MicroServices deployments late in the development cycle?
Join us in this talk where we will share our experience about how we leverage API Specification Standards such as OpenAPI to identify such compatibility issues early in the development cycle and in the process effectively eliminating integration tests. We will also be sharing our journey about how necessity drove us to come up with the “Contract Driven Development” approach and Specmatic, an open source tool that embodies the same to promote collaboration among teams, lower cycle time and deploying services independently.
Contract Driven Development – Deploying your Microservices Independently without Integration Testing
@@ -355,7 +355,7 @@
Presentation summary<
-
Our largest hurdle in deploying a MicroService was the Integration Testing stage. Just one incompatible API was enough to break the integration environment and block the path to production for all services.
While adopting OpenAPI helped address some of the communication gaps in API specs between teams, the deviations during implementation continued to persist. We needed an approach that changed the way teams collaborated on API Specs and also remove the need for integration testing.
To fill this need we came up with Contract Driven Development which consists of 1. Contract as Test – Contract (Example: OpenAPI) translated to Test Scenarios against the API implementation. Ensures that Provider (API implementation) adheres to Contract. 2. Smart Service Virtualisation – Verify Stub Data against OpenAPI Spec. Ensures the Consumer (API Client) is compatible with Provider’s Contract. 3. Backward Compatibility Testing – OpenAPI vs OpenAPI (no code) to check if versions are backward compatible. Helps teams analyse if a change will break integration.
Being able to develop, test and easily deploy a single microservice is a key indicator for a successful transition to a microservice style architecture. The challenge arises when determining how the new microservice will interact with your existing system meaning that they need to undergo comprehensive integration testing before deployment. This slows down the path to life and highlights problems at a much later point in the microservice lifecycle. Contract Driven Development helps you to shift left and identify compatibility issues earlier in the development life cycle when they are easier to catch and fix.
Contract-Driven Development – Turn your API Specification into Executable Contracts
@@ -360,14 +360,14 @@
Presentation summary<
-
Being able to develop, test and easily deploy each of your microservice independently is a key indicator of a successful transition to a microservice style architecture. The challenge arises when a new microservice that interact with your existing system has to undergo comprehensive integration testing before deployment. This slows down the path to production and highlights problems at a much later point in the microservice’s lifecycle. Contract Driven Development helps you to shift left and identify compatibility issues earlier in the development life cycle when they are easier to catch and fix.
Naresh is also speaking at YOW! Con in Sydney (8 Dec).
Kafka and JMS Mocking with AsyncAPI using Specmatic
@@ -356,7 +356,7 @@
Presentation summary<
-
AsyncAPI allows us to articulate communication channels between services clearly. What if I told you that we can leverage the same AsyncAPI specification to quickly spin up mock topics and queues to test our services in isolation?
That is exactly what Specmatic is able to achieve by leveraging AsyncAPI specifications to give us early feedback on our local machines and in our CI pipelines when our service implementations deviate from the API specifications.
In this talk I will be going over below points with live demos.
@@ -367,7 +367,7 @@
Being able to develop, test, and easily deploy a single microservice is a key indicator for a successful transition to a microservices-style architecture. The challenge arises when determining how the new microservice will interact with your existing system, meaning that it needs to undergo comprehensive integration testing before deployment. This slows down the path to life and highlights problems at a much later point in the microservices lifecycle. Naresh Jain explains how contract-driven development helps you shift left and identify compatibility issues earlier in the development lifecycle, when they’re easier to catch and fix.
Turn Your OpenAPI Specifications into Executable Contracts — The Gory Details
@@ -355,14 +355,14 @@
Presentation summary<
-
Today, with the explosion of microservices and a plethora of protocols, ensuring in an automated manner that the API implementations actually adhere to their contracts is almost impossible. And on the other side, the consumers of these APIs have to hand-code the API stubs (poor man’s service virtualization), with no guarantee that the stubs actually adhere to their OpenAPI specifications. All of these gaps manifest as integration bugs late in the cycle. If these problems sound familiar, then this session is for you to understand how to leverage the very same OpenAPI specifications, so that they can be turned into contract tests and stubs without writing a single line of code.
As an author of an OpenAPI spec, you would like to ensure that the API developer who will implement this API is adhering to the contract. Learn how to author OpenAPI specs which can verify that the API is implemented correctly. As a consumer you often need to stub out your API dependencies while developing and testing your component. Learn how to set expectations that actually adhere to the contract, and thereby avoid late integration issues.
