Couchbase uses Swagger to tame the API Monster, so should you

Couchbase incorporated Swagger into our documentation a few months ago. “Swagger” refers to an ecosystem of tools and other resources for managing REST APIs. Core to Swagger is the Swagger specification. (The group behind Swagger donated the spec to … more

My business card states my title as “Technology Evangelist”. I learn technology, use it in solutions to the point where I can teach it to others then I preach it.  My audience is mostly people who probably think I’m a little crazy.  When it comes to REST and API’s the answer I recommend now is using Swagger and its toolset to design, manage and document your valuable API’s.  I scream every time I see Word/Excel/Email documents beings used to define API’s in large systems.   Using 20th-century tools to manage modern 21st-century processes like API’s doesn’t scale and helps contribute to some of the failures I have seen.

via Managing REST APIs with Swagger (video) — JSFeeds

Dropbox does a Take 2 on their API

Dropbox builds a dramatically different V2 of their API, built for scale. By Margot Krouwer

Some important takeaways from this article concern using REST and the REST “Standards” as they may exist.  In creating V2 of the Dropbox API, however, Dropbox went decidedly out off trend. Rather than utilizing the paradigms of REST, or GraphQL or even socket servers, Dropbox created their own custom JSON in JSON out API which largely ignores the guidelines of REST or even HTTP.

via Evolving APIs for Scale with Dropbox — InfoQ

10 Best Practices for Writing Node.js REST APIs

In this article we cover best practices for writing Node.js REST APIs, including topics like naming your routes, authentication, black-box testing & using proper cache headers for these resources. One of the most popular use-cases for Node.js is to write RESTful APIs using it. Still, while we help our customers to find issues in their…

Even if you’re not going to use Node.JS for your API engine, this article has some great tips for starting standards for your project or company.  RisingStack does have a set of Pay tools for Node.JS debugging and articles like this help direct traffic to them.  The articles are excellent reads.

via 10 Best Practices for Writing Node.js REST APIs — RisingStack Engineering

GeekMustHave is now on YouTube

Hello and welcome to Geek Must Have YouTube channel. Everyone once and awhile have you come across someone who you know, is going to try and build something cool… that’s me.  This channel is going to be the Geek’s musing about technologies like Electronic Gadgets that blink, buzz, talk, listen and keep you awake at night. Computers of all sizes from the tiny single chip ones all the way up to big servers in the cloud.  Coding from Cobol to JavaScript and everything in between.  Databases starting with the humble flat file, tried and true relational and Big Data, noSQL, REST and JSON.  Communications with wireless, GSM, Bluetooth and amateur radio.  Lots of cheap bits, bobs and do-dads from China.  This channel plans to have mailbags, project builds, deconstructions, reviews, recommendations, tools, and tips

Check out the champion blog at HTTP://GeekMustHave.COM

This a new channel and the Geek needs your help, please click on the subscribe button,
watch the videos and click on the like button, leave comments and questions.

The Geek is busy learning and building stuff, so don’t be upset if the response isn’t immediate.

Thank you and now ….“Let’s build something…”

SoapRest.jpg

I often had difficulties explaining to customers how the integration magic used to work and how it has changed.  Most didn’t care as long as their stuff kept working.  I have heard from government customers they use SOAP because it is more secure than REST.  Really?  Duncan has written this article which is an excellent introduction to the two protocols and should be given to anyone who asks “What is ….”.  I’ve been RESTing for awhile now, and I don’t plan on getting clean with SOAP anytime soon.