Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "API Gateway REST vs. HTTP API: What Are The Differences?" | Hashnode

Feed/

Discussion

API Gateway REST vs. HTTP API: What Are The Differences?

How do these two versions of the same technology differ? A quick rundown of whether REST or HTTP APIs represent the best investment.

Feb 1, 2022·8 min read·tinystacks.hashnode.devUpdated Jun 14, 2022Read the article

#aws
#rest-api

#backend

#cloud

#serverless

Written by

Jay Allen

@jayallen · Tokyo, Japan

View profile

Technical Writing, Technical Content Marketing

Technical Writing & Content Marketing Manager at ercule. I've created technical content for over two decades for Amazon Web Services, Microsoft, and many others. Specialties include cloud computing, DevOps, data engineering, and analytics engineering.

Responses1

Markdown supported · ⌘↵ to post

Sebastian M

Mar 24, 2022

Thanks! Great article! There is another difference that you mentioned, and I was wondering if you didn't mention because you use other alternative: REST APIs enable the ability to use an API key for enhanced security....does it sound a good feature, or you don't use it at all? Thanks!

Jay Allen

Mar 24, 2022

That's a good point! I personally don't tend to use API keys because they can be implemented in a lazy and insecure manner (e.g., plain text GET query strings). So I tend to prefer OAuth for added security.