10 Steps to a Painless API Release
ICYMI: James Higginbotham, Executive API Consultant, shares his API and product release insights with a list of 10 essential steps to improve the next release of your API. If you’re interested in being a part of our next series, fill out this short form and we’ll get in touch with you for our next run.
It is exciting to release something new. The thrill of seeing an idea to completion is always an exciting time for software teams. But how do you know when an API is ready to release? What if you missed something that could result in increased support emails and calls? What if you broke existing internal or 3rd-party integrations?
This article provides a 10-point checklist to help ensure your next API release is as smooth as possible. https://goo.gl/fHZFFp #DataIntegration #ML
How Our CEQL Compares to SQL Queries
Our Elements are the root of what we do but don’t call them Connectors, it doesn’t do them justice. Their job is to provide a standard way to connect to endpoints, regardless of the nuances of each given endpoint, and frankly, is not as easy as it sounds.
One of these subtleties is with the query language required to filter data when retrieving it from an endpoint using API resources – it ranges from slight variations of SQL queries to OData or XML RPC filter queries. Some endpoints have their own, modified version of SQL queries (e.g. Bullhorn) in order to meet their specific search use cases, others use specialized query languages like SPARQL (e.g. Docustore). https://goo.gl/1wmLej #DataIntegration #ML
