GraphQL 🔥

A query language for your API 💎

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.

GraphQL provides a complete and understandable description of the data in your API,
gives clients the power to ask for exactly what they need and nothing more,
makes it easier to evolve APIs over time,
and enables powerful developer tools.

http://graphql.org/
https://scaphold.io/
〰〰〰〰〰〰
#GraphQL #API
@ProgrammingTip

JSON Server 🔥

Get a full fake REST API with zero coding in less than 30 seconds (seriously) 🙋🏻‍♂️

Created with ♥️ for front-end developers who need a quick back-end for prototyping and mocking. 🛠

https://github.com/typicode/json-server

Fake Online REST API for Testing and Prototyping :
http://jsonplaceholder.typicode.com/

#API #JSON #Mocking
@ProgrammingTip

Master Your API Workflow with Postman 🔸

They’re doing a great job by providing an integrated environment for different components of an API, like authorization, testing, documentation, versioning. 💎

https://www.sitepoint.com/master-api-workflow-postman/

#API #Postman
@ProgrammingTip

API Feature Folders ⚡️

In ASP.NET Core (and unlike ASP.NET 5 / Web API 2), Web API controllers are just controllers. 🗂

You don’t need to inherit from a different base type or anything like that. ❌

What’s more, your API controllers should be returning DTOs that are separate from your underlying domain or data model. ↔️

What I’ve found to be a better organization is to do away with the Controllers folder (or keep it around if you’re using view-based controllers) and instead use feature folders for your APIs. 💎

I’m partial to having a root level API folder but if you’d prefer to put your features in the root of the project that would work, too. 👍🏻

Within each feature folder, you include the controller along with any model types it needs to work with, like this 👾 :

https://t.me/pgimg/124

Obviously one benefit of this approach is that it’s more cohesive. ✅

Things that change together are located physically next to one another, and the friction involved in moving between different folders with too many files in them is greatly reduced. ✂️

Another nice thing about this approach is that it just works. Unlike view-based controllers, you don’t need to change anything about how ASP.NET Core is configured to have this organization structure work for you. ✨


[ Article ] : bit.do/apif

〰〰〰〰〰〰
#AspMvc #Core #API
@ProgrammingTip

Auto Rest ✨

OpenAPI (f.k.a Swagger) Specification code generator. 💎

Supports C#, Go, Java, Node.js, TypeScript, Python, Ruby and PHP. 🔥

The AutoRest tool generates client libraries for accessing RESTful web services. ⚡️

Input to AutoRest is a spec that describes the REST API using the OpenAPI Specification format. ✅


https://t.me/pgimg/187

[ Introduction ] : kutt.it/ares
[ Github ] : github.com/Azure/autorest

〰️〰️〰️〰️〰️〰️
#Rest #API #OpenAPI #Swagger
@ProgrammingTip

Newsletter 🗞

In this newsletter, we will talk about the following:

• Retry patterns ♻️

• Evolution of the Netflix API architecture 🔝

• How does stop loss work❓

• Chaos Engineering 🤯


[ Article ] : https://kutt.it/newsletter1

〰️〰️〰️〰️〰️〰️
#Newsletter #Retry #Chaos_Engineering #API_Gateway
@ProgrammingTip