RefCard API Architecture Strategy

In a Nutshell

To facilitate and accelerate design and development of your APIs, we share our vision and beliefs with you in this Reference Card. They come from our direct experience on API projects.

Retour

Description.

As soon as we start working on an API, architecture issues arise. Many mistaken common beliefs turn out to be fiction in this area. A poorly designed API architecture will lead to misuse or – even worse – not be used at all by its intended clients: application developers.

This Reference Card pinpoints everything you should be cautious about while designing your API Architecture Strategy.

Which API strategy to choose? Why an API strategy?

Au menu :

> Which API strategy to choose? Why an API strategy?

> API big picture architecture: from SOA to WOA

> SOAP vs REST

> API architecture stakes

> API security

> API team organization

> API management

> API integration patterns

Please fill out the informations requested below to receive a download link of the ebook by email.

Name*

Votre nom est obligatoire

First name*

Votre prénom est obligatoire

E-mail*

Exemple : [email protected]

Title*

Votre titre est obligatoire

Company*

Votre société est obligatoire

*Champs obligatoires

I love what you do! Keep me posted.

Sure

No, thanks

By submitting this form, you agree that the data entered will be used by the OCTO teams to contact you as part of the request made via this form.

Vous devez accepter les conditions

Merci

Votre demande a bien été envoyée,
veuillez consulter la boîte de réception de votre messagerie.