Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Criteria for Selecting Your REST Services Platform

DZone's Guide to

Criteria for Selecting Your REST Services Platform

· Integration Zone
Free Resource

The Integration Zone is brought to you in partnership with Cloud Elements. What's below the surface of an API integration? Download The Definitive Guide to API Integrations to start building an API strategy.

In the first two blogs in this series, we tackled the issue of how REST is a solution to a connected enterprise followed by discussions on What is REST. Then we discussed why use REST for database access. The last blog in this series addressed the following two key issues:

In this blog, we summarize the criteria for selecting your REST services platform – the criteria that was developed in the last blog. We also present how Espresso Logic meets this criteria and this document should serve as a template for you as you embark on vendor selection for REST services platform for your backend for mobile and web applications.

Requirements for REST Platform Espresso Logic Other Vendors
Implementation Services
REST service & database in the cloud Can connect to your database or provide a cloud database
REST service in the cloud, database on the premise Recommend a reverse SSH tunnel
REST service and database on the premise Offered as a VM Ware appliance
Database Services mapped to REST
Tables Yes
Views Yes
Stored Procedures Yes
Databases Supported MySQL, SQL Server, Azure, Oracle
Support for all REST functions
GET Yes
POST/PUT/DELETE for all operations Yes
Built-in Enterprise Class Features
Automatic pagination Yes
Filtering and ordering Yes
Optimistic locking Yes
Custom REST endpoints
Aliasing column names Yes
Automated SQL handling Yes
Projection – selecting fields to display Yes
Build resource endpoints from external services Yes
Security and Access Control
Default table level security Yes
Role based security derived from your Authentication Yes
Assign privileges by REST endpoints Yes
Row and column level access Yes
API Logic
JavaScript object model Yes
Reactive Rules Yes
Built-in testing and debugging
Interactive REST Lab Yes
Ability to log logic execution Yes
Interactive debugger Yes
Other Service Integration
Able to call any web service Yes

Your API is not enough. Learn why (and how) leading SaaS providers are turning their products into platforms with API integration in the ebook, Build Platforms, Not Products from Cloud Elements.

Topics:

Published at DZone with permission of Val Huber, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}