Why Standards-Based Drivers Offer Better API Integration
- 1. www.cdata.com See the World as a Database Data APIs Why Standards-Based Drivers Offer Better API Integration Jerod Johnson, Technology Evangelist @jeRodimusPrime @cdatasoftware
- 2. www.cdata.com 1.The State of Data Today 2.API Integration Options 3.Data APIs (Standard Drivers) 4.Case Study (Bouquet.ai) Agenda
- 3. www.cdata.com The State of Data Today • The number of public APIs, SDKs, and libraries continues to grow • Modern Enterprises are using: • At least 16 SaaS applications • Dozens of on-premise data stores and apps
- 4. www.cdata.com LEGACY TECHNOLOGY SaaS APPLICATION 2017 State of the SaaS-Powered Workplace SaaS is Now the System of Record. 58% of companies are running almost completely on SaaS
- 6. www.cdata.com Options for API Integration Direct Integration Developing or integrating directly with the API Software Development Kits Using embedded SDKs to connect to the API Integration Middleware Extracting or aggregating data to a single platform that works with APIs Standards-Based Drivers ??? API
- 7. www.cdata.com Direct Integration • Benefits • Greatest control • Simplified integration • Considerations • Longest time to integrate • Lifetime maintenance • Limited reuse across data sources API
- 8. www.cdata.com Software Development Kits API • Benefits • Tightly bound data access • Simplified integration • Considerations • Lack of shared data model • Limited vendor support • Limited reuse across data sources
- 9. www.cdata.com Integration Middleware API • Benefits • Abstract data connectivity • Shared data model • Considerations • High cost, complexity • Vendor lock-in • Least developer control • Limited data source integrations
- 11. www.cdata.com What is a Standards-Based Driver? • Historically used to integrate with database • Technologies include JDBC, ODBC, ADO.NET • Vendors now create driver for SaaS applications ADO.NET ODATAJDBCODBC
- 12. www.cdata.com Standards-Based Drivers API • Benefits • Low learning curve • Self-documenting • Common “data API” • Insulation from API changes • Considerations • Not suitable for event-based operations • Additional layer of abstraction
- 13. www.cdata.com Data APIs Modeling data access through SQL • Tables and views correspond with resource collections (Orders, Accounts, Pages, Users, etc.) • Individual elements correspond to a row • Sub-collection relationships are maintained (Orders and Order Line Items) • CRUD operations are translated to SQL statements • Operations and functions are implemented with stored procedures
- 14. www.cdata.com SQL-92 Compliant Queries The easiest way to build data-centric applications. Write standard SQL queries with support for JOINs, updates, aggregation, and more. SELECT Account.Id, Account.Name, Account.Fax, Opportunity.AccountId, Opportunity.CloseDate FROM Salesforce.Account INNER JOIN Salesforce.Opportunity ON Account.Id = Opportunity.AccountId SELECT WITH INNER JOIN UPDATE Account SET Name='John' WHERE Id = @myId UPDATE DATA SELECT State, AVG(AnnualRevenue) FROM Account GROUP BY State AGGREGATE FUNCTIONS using (SalesforceConnection conn = new SalesforceConnection("...")) { string select = "SELECT * FROM Leads"; SalesforceCommand cmd = new SalesforceCommand(select, conn); SalesforceDataAdapter adapter = new SalesforceDataAdapter(cmd); using (adapter) { DataTable table = new DataTable(); adapter.Fill(table); ... } } Standard Driver Interfaces Just like connecting with a typical RDBMS like SQL Server. Use standard components like Connection, Command, DataAdapter, DataReader, DataSource, etc. Simplify Developer Integration
- 15. www.cdata.com SOURCE: CDATA SOFTWARE Embedded in the leading BI, ETL, Data Integration, Data Virtualization, and Data Warehousing Tools Leading Vendors Using Data APIs
- 16. www.cdata.com Natural language AI platform, Aris extends data connectivity with CData and the power of SQL abstraction. Mapping natural language queries to SQL highlights the transformative power of a SQL data abstraction, as it would be nearly impossible to map these dynamic queries to SaaS data any other way. More Online: https://www.cdata.com/case-study/bouquet/ Case Study: Bouqet.ai
- 17. www.cdata.com The Takeaway • Choose an integration based on current and future use cases, time and budgetary constraints • Consider the role that citizen analysts, integrators, and 3rd party tooling may play in digital transformation • Explore data-centric integration based on established standards