Don't pretty print your API's JSON response body (3 mins read).
Why pretty-printing JSON responses in your APIs is a waste of resources, and you should stop it.
by 
Jamie Tanna
.
#api
#json
#rest.
Tag rest
Liked
a post on Twitter
Post details
Moving from a GraphQL product to a REST based product is the prime time for noticing all the things that are GoodActually™ about GraphQL
Joe Hart 🏳️🌈 (@JoeHart)Wed, 30 Mar 2022 10:16 +0000
by Jamie Tanna
.
#graphql
#rest.
Use a (JSON) Schema for the Interface Portion of your RESTful API (3 mins read).
Why you should be using a well-defined (JSON) Schema for the data classes that your API consumers will need to utilise.
by Jamie Tanna
.
#api
#json-schema
#rest.
Liked
a post on Twitter
Post details
The biggest difference between REST and GraphQL is that when you build GraphQL API nobody tells you "well, actually this is not GraphQL".
Maciej Walkowiak 🍃 (@maciejwalkowiak)Fri, 08 Oct 2021 00:57 +0000
by Jamie Tanna
.
#rest
#graphql.
Why I Consistently Reach for Server-Driven Content Negotiation (For Versioning) (5 mins read).
Why I use server-driven content negotiation for APIs to allow for versioning and allowing different representations of APIs.
by Jamie Tanna
.
#api
#content-negotiation
#rest
#web
#versioning
#version-pinning.
Bookmarked
https://github.com/typicode/json-server/
.
I've used this server before to get a simple RESTful API up and running, and it's really useful.
by Jamie Tanna
.
#tools
#rest.
You're currently viewing page 1 of 1, of 8 posts.