You give REST a bad name

Special shout out to Dan H. for directing me to this video.  It does outline some of the things folks do that make REST difficult.  I want to see a music video done for SOAP, trying to figure out a music track for it.

 

 

 

HTTP request and Node, so many solutions, so little time.

Making HTTP requests is a core functionality for modern languages and one of the first things many developers learn when acclimating to new environments. When it comes to Node.js there are a fair amount of solutions to this problem both built into the … more

If you’re using Node to develop applications or servers you will need to handle HTTP requests.  The standard Node HTTP library is good but there are some options including promises, Super Agent and Ajax to name a few.  While it’s not rocket science this article comes from the experiences with NASA.

via HTTP Requests in Node.js — JSFeeds

Play with Lego’s again…. Build great API’s

Great-APIs-Are-Like-Lego-Bricks.png

Most of us have fond memories of playing with Lego as kids. The real attraction of Lego is that, even though most sets came in boxes with pictures on the front, it really didn’t matter if what you built ended up looking the same as that picture.

To quote a previous article featured on this blog, “Many API talks start off by explaining that APIs are like these [Lego] bricks. They can be combined in innovative and creative ways beyond their originally intended purpose.”

Think small.  Each of your API’s is a small single Lego block.  If they are built right they plug into each other to make bigger blocks which in turn can make bigger things.  One of the things I learned in business intelligence is that you can’t predict what the next question is going to be.  What you built your API for may not be what is gets fame and glory for, Ok at least some recognition for it.

This is a great article with plenty of useful tips and things I’ve never thought of before.  The video was also quite educational.

via: Nordic APIS 

 

API Gateways, the Rosetta Stone for data

Services in a microservices architecture share some common requirements regarding authentication and transportation when they need to be accessible by external clients. API Gateway s provide a shared layer to handle differences between service protocols and fulfills the requirements of specific clients like desktop browsers, mobile devices, and legacy systems. Click to see all chapters…

API Gateways are the middle man in the Application-Data relationship.  They serve as a community hall where folks go to meet and talk to one another.  This community hall has a universal translator like on Star Trek that makes data understood by all the people in the room.   Developers don’t worry about XML/JSON because the gateway understands them both.   DBA don’t worry about formatting the data because the gateway loves to format stuff.

Have you ever been fustrated with Sri, OK Google or Alexa?  Gateway quality varies from one vendor to another.  Write your own in Node may be an alternative, I don’t know.  Let’s talk.

via Building an API Gateway using Node.js — RisingStack Engineering

GraphQL an alternative method to develop REST API’s

Facebook may not be the favorite company of the open web community, for some good reasons. But when it comes to open source, most developers take advantage of their tools, libraries, and frameworks in one way or another. In particular, Javascript (Node.js) and PHP have advanced by leaps and bounds largely thanks to Facebook’s contributions. […]

GraphQL is an alternative method of developing API’s to can use traditional SQL databases and the “Exotic” (1)  noSQL databases.  Like everything new, there is a learning curve.  There is an excellent course on YouTube from Traversy Media that covers the basics to intermediate use of GraphQL

This library has support for JavaScript, PHP, React and many other environments.  It’s worth a look-see, you never know.

(1) In a meeting recently where the prospect said this.  Along with “noSQL is not a standard and is not considered secure.”

via GraphQL, the future of APIs — AltPlatform

30 Second API mock servers using JSON-Server and Node, Quick and Dirty.

In the UK we have a chef called Jamie Oliver and over the years he has created lots of TV episodes and also a book on how to make a complete family meal in 30 Minutes – The premise of this, is that time doesn’t have to be an excuse not to make healthy food […]

There are times when you need a mock server for a REST API that returns JSON results and you need it now!!  This article goes over the process to create one on your local system which could be transferred to a server.    You create a JSON file, simple text file,  with the data in it and JSON-Server writes a full API service around it.  It can do all the CRUD you want and support queries.

There are a few restrictions like having a key field requirement in each table with the identical name.  (IE: _id) .  Most of my work requires using the key that was already in the database (ie: benficiaryID, providerNumber, DiagCode).  Moving this to a server will require some technical talent that many companies don’t have.

I have used Mockable IO to provide mock API services that are server based and need to be accessed by developers outside of a corporate firewall.  The free version is enough for most projects to get started.

No matter which mock server you use be prepared to take a considerable amount of time to mock up the results sets you expect the API service to provide.

 

 

 

 

 

via 30 Second APIs… — Danny Dainton

How to talk about an API in a way everyone understands

Andrew Seward presents tips on how to talk about an API and how to create an ubiquitous language for that. By Andrew Seward

I have fallen into the trap Andrew describes where I try to impress the end-user of the technology behind how my wonderful API works.  Most end-users just don’t care, they just want it to work.  His suggestion?  Come up with a simple vocabulary that everyone understands.

Audio Transcript

Copy of Andrews slides API Paris2016-How to talk about APIs

via Presentation: How to Talk About APIs — InfoQ

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