Sign In

Plug & Play Integration

ParaSQL uses a Neo-Federated architecture built on top of open drivers to ensure the widest possible integration options. Below is a partial list of our off-the-shelf integration drivers.

Any JSON REST API (configurable)
Any XML REST API (configurable)
Any OData API (configurable)
Shopify
Magento
Salesforce
SendGrid
Twilio
MailChimp
Microsoft Azure/SQL Server
Oracle
SAP
PostgreSQL
MySQL
IBM DB2
Amazon Redshift
Microsoft Dynamics 365
Microsoft Dynamics GP
Zendesk
Service Now
Marketo
SharePoint
Microsoft Exchange
Office 365
Facebook
Twitter
LinkedIn
Email IMAP/POP
Google Apps
Google AdWords
Slack
SurveyMonkey
eBay
JIRA
BOX
LDAP Directory

What Is A "Neo-Federated" Architecture?

A traditional federated architecture treats multiple databases within a single company as a single logical database. ParaSQL's Neo-Federated architecture extends this concept to web APIs. This means you can treat third-party web APIs as an extension of your own database (and thereby an extension of your company), which radically simplifies integration and enables powerful new use cases.

First you configure a Federated Data Source for the API you want to use. Then you map the API end points to one or more virtual tables in your database. Both of these steps are point-n-click simple and require zero programming.

At this point your application screens and business logic can both read and write these virtual tables as though they were actual database tables. The reads and writes get translated dynamically into API calls to the remote system. You no longer have to hand code access, data type mapping, change tracking and posting of changes. It all happens automatically. The result is higher quality applications with fewer bugs in less time.

We think it's the future. And with ParaSQL, it's available today.

Request our upcoming White Paper on Next-Generation Federated Data Architectures and our Model-Driven, Data-Centric approach to application development.