AsyncAPI provides a specification that allows you to define Message-Driven APIs in a machine-readable format. It’s protocol-agnostic, so you can use it for APIs that work over MQTT, AMQP, WebSockets, STOMP, etc. The spec is very similar to <a href="https://github.com/OAI/OpenAPI-Specification" target="_blank" rel="noopener">OpenAPI/Swagger</a> so, if you’re familiar with them, AsyncAPI should be easy for you.
<a href="#A-basic-example" data-scroll=""><h2></h2></a>

async api 

AsyncAPI provides a specification that allows you to define Message-Driven APIs in a machine-readable format. It's protocol-agnostic, so you can use it for APIs that work over MQTT, AMQP, WebSockets, STOMP, etc. The spec is very similar to OpenAPI/Swagger so, if you're familiar with them, AsyncAPI should be easy for you.

artificialintelligence

Artificial Intelligence

Introduction - AsyncAPI


Teams must employ appropriate communication techniques, including deprecation
and turn-down notices, to ensure awareness of changes to microservice
contracts

depreciation notice

One of the most important aspects of microservices-based applications is the
ability to deploy microservices completely independent of one another. To
achieve this independence, each microservice must provide a versioned,
well-defined contract to its clients, which are other microservices.
Each service must not break these versioned contracts until it's known that no
other microservice relies on a particular, versioned contract.

contract versions

It's important to understand the difference between a breaking change and a
non-breaking change. Breaking changes are often subtractive, meaning they take
away some part of the request or response document. Changing the shape of the
document or changing the name of the keys can introduce a breaking change. New
required arguments are always breaking changes. Breaking changes can also occur
if the behavior of the microservice changes.

Non-breaking changes tend to be additive. A new optional
request argument, or a new additional section in the response document are
non-breaking changes. In order to achieve non-breaking changes, the choice of
on-the-wire serialization is essential. Many serializations are friendly to
non-breaking changes: JSON, Protocol Buffers, or Thrift. When deserialized,
these serializations silently ignore extra, unexpected information. In
dynamic languages, the extra information simply appears in the deserialized
object.

breaking=subtractive non-breaking=additive

Google Cloud delivers secure, open, intelligent, and transformative tools to help enterprises modernize for today's digital world.

Contracts, Addressing, and APIs for Microservices

<li>It doesn’t share database tables with another service</li><li>It has a minimal amount of database tables</li><li>It’s thoughtfully stateful or stateless</li><li>Its data availability needs are accounted for</li><li>It’s a single source of truth</li>

a well designed microservice

If you've read about microservices, you've no doubt come across advice on what makes a well-designed service. Simply put: high cohesion and loose coupling. While sound advice, these concepts are quite abstract. I've spoken with dozens of CTO's on this topic to learn from them on how they've drawn their microservice boundaries, and I've distilled down some of the underlying characteristics for you below.

computerscience

Computer Science

Microservice boundaries: five characteristics to guide your design

There’s been a number of these different communities that have been growing over time and demonstrating that this approach to building software is a viable one for production and almost when you start to look at companies of the scale of Netflix, then almost like a necessity as they grow income. Edgemont Kotcroft is on record as saying the reason they build systems in this way is because they wanna be able to go as fast as possible. They wanna be able to make changes as fast as possible.

microservices = go fast

What a circuit breaker in your software does is provides you a level of safety when you’re talking to external systems. So in my code I’ll implement a circuit breaker such that if the downstream system that I’m integrating with becomes slow or goes away and, of course, as we all know, there is essentially no difference between being slow and not being there at all.

circuit breaker

Johannes Thönes talks to James Lewis, principal consultant at ThoughtWorks, about microservices. They discuss microservices' recent popularity, architectural styles, deployment, size, technical decisions, and consumer-driven contracts. They also compare microservices to service-oriented architecture and wrap up the episode by talking about key figures in the microservice community and standing on the shoulders of giants.

Introduction - AsyncAPI

Contracts, Addressing, and APIs for Microservices

Microservice boundaries: five characteristics to guide your design

Episode 213: James Lewis on Microservices

Bogdan Lucaciu