An excellent article on the what, why and how of AJAX. It’s not just for XML.
JSON Schema is a powerful tool for validating the structure of JSON data. However, learning to use it by reading its specification is like learning to drive a car by looking at its blueprints. You don’t need to know how an internal combustion engine fits together if all you want to do is pick up the groceries. This book, therefore, aims to be the friendly driving instructor for JSON Schema. It’s for those that want to write it and understand it but maybe aren’t interested in building their own car—er, writing their own JSON Schema validator—just yet.
This is a web based book on JSON and the practical usage of the JSON Schema. It starts out with the trike and training wheels and moves all the way up to a racing bike. I learned something in each chapter I read. I also see the connection between the JSON schema and the Swagger/OAS definitions. If you have used WSDL for the schema definition in an XML web service you will appreciate how much simpler and easier it is to read a JSON schema.
I did a post a little while ago about a JSON editor that can take advantage of a JSON schema if it’s available.
There is a print version of this book at the following link.
via: Understanding JSON Schema
I have used D3 in concert with C3 to create a data visualization front end to a data warehouse. D3 has a ton of features but is difficult to use out of the box for the novice user. The C3 library puts a layer of smarts on top of D3 making it much easier to get started in graphic visualizations. I’ve also used CData product to get an ODBC connection to Google sheets in order to analyze and transfer results from a Google form survey to a data warehouse. CData products are very good just be willing to pay for that excellence.
This article is a good read because it combines the two to assemble a REST service and use it to provide the data feed to D3.
via Building Dynamic D3.js Web Apps With Database Data — DZone Web Dev Zone
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
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
(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
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
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 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
In short, json-server is a Node module, running an Express server, that lets you specify a JSON file to act as a data source for your mock REST API.
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