Day: February 16, 2018

Content negotiation is one of those quality-of-life improvements you can add to your REST API to make it more user-friendly and flexible. And when we design the API, isn’t that what we want to achieve in the first place?

There are many things to keep in mind when designing a REST API and we’ve written recently about it in our top rest API best practices article. Content negotiation is an HTTP feature which has been around for a while, but for one reason or another, may be a bit underused. https://goo.gl/3DRMge #DataIntegration #ML

ICYDK: Mule’s object store is a convenient way to store objects for later retrieval by key, essentially a key-value store. By default, this is in-memory, but it can also be easily changed to persist to file.

Below is the list of available operations supported by the Object store. The object store connector can perform various operations like Contains, Dual store, Remove, Retrieve, Retrieve all keys, Retrieve, and Store and Store. https://goo.gl/frst2r #DataIntegration #ML

ICYMI: This is one of my talks from APIDays Paris 2018. Here is the abstract: The modern API toolbox includes a variety of standards and methodologies, which centers around REST, but also includes Hypermedia, GraphQL, real-time streaming, event-driven architecture, and gRPC. API design has pushed beyond just basic access to data, and also can be about querying complex data structures, providing experience rich APIs, real-time data streams with Kafka and other standards, as well as also leveraging the latest algorithms and providing access to machine learning models. The biggest mistake any company, organization, or government agency can make is to limit their API toolbox to be just about REST. Learn about a robust and modern API toolbox from the API Evangelist, Kin Lane.

Diverse Toolbox

After eight years of evangelizing APIs, when I participate in many API conversations, some people still assume I’m exclusively talking about REST as the API Evangelist – when in reality I am simply talking about APIs that leverage the web. Sure, REST is a dominant design pattern I shine a light on, and has enjoyed a significant amount of the spotlight over the last decade, but in reality on the ground at companies, organizations, institutions, and government agencies of all shapes and sizes, I find a much more robust API toolbox is required to get the job done. REST is just one tool in my robust and diverse toolbox, and I wanted to share with you what I am using in 2018. https://goo.gl/GbNiN2 #DataIntegration #ML