Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Deliver Secure SQL Access for Enterprise APIs - August 29 2017

116 visualizaciones

Publicado el

This is a webinar we ran on August 29, 2017. 700+ users have registered for this webinar. In this webinar, Dipak Patel and Dennis Bennett talk about how companies can build SQL Access to their enterprise APIs.

Abstract:
Companies build numerous internal applications and complex APIs for enterprise data access. These APIs are often based on protocols such as REST or SOAP with payloads in XML or JSON and engineered for application developers. Today, however the enterprise data teams are trying to access this data for analytics which requires standard query capabilities and ability to surface metadata. As enterprises adopt new analytical and data management tools, a SQL access layer for this data becomes imperative. Many such enterprises from the Financial Services, Healthcare and Software industries are relying on our OpenAccess SDK to build a custom ODBC, JDBC, ADO.NET or OLEDB layer on top of their internal APIs and hosted multi-tenant databases.

Watch this webinar to learn:
1. Use cases for providing SQL access to your enterprise data
2. Learn how organizations provide SQL Access to its APIs
3. See a demo using DataDirect OpenAccess SDK to provide SQL Access for a REST API
4. Pitfalls and Best Practices to building a SQL Access

Publicado en: Tecnología
  • Sé el primero en comentar

Deliver Secure SQL Access for Enterprise APIs - August 29 2017

  1. 1. Deliver Secure SQL Access for Enterprise APIs Dipak Patel, Principal Product Manager and Co-founder of OpenAccess, Progress Dennis Bennett, Principal Sales Engineer, Progress
  2. 2. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.2 Audio Bridge Options & Question Submission
  3. 3. Deliver Secure SQL Access for Enterprise APIs Dipak Patel, Principal Product Manager and Co-founder of OpenAccess, Progress Dennis Bennett, Principal Sales Engineer, Progress
  4. 4. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.4 Agenda  Background and Use cases for SQL Access  How to deliver SQL Access for REST APIs?  Demo  Best Practices
  5. 5. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.5 How Have BI Solutions Evolved?
  6. 6. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.6 SQL Is a Common Approach
  7. 7. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.7 SQL Is a Common Approach
  8. 8. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.8 How Do We Get Back to 3rd Wave?
  9. 9. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.9 OpenAccess Gets You Back to 3rd Wave
  10. 10. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.10 Survey Question 1: Which Enterprise BI tools are you using in your organization today? • Oracle Business Intelligence (OBIEE) • Microsoft Business Intelligence (SSIS, SSAS, SSRS) • SAP Business Objects • IBM Cognos • Other (Please share through comments)
  11. 11. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.11 Survey Question 2: What solutions are you leveraging to develop your Enterprise API layer? • CA API Management • IBM API Management • Oracle API Manager • Mulesoft • Other (Please share through comments)
  12. 12. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.12 SQL Standards remain popular for access data 728 569 571 551 412 206 281 176 184 137 0 100 200 300 400 500 600 700 800 900 1000 ODBC REST SOAP JDBC ADO.NET API Landscape Currently Use Plan to use in the next 2 years Source: 2017 Data Connectivity Outlook Survey
  13. 13. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.13 Application / Business Logic • Business Logic Layer: CRM, Finance and other applications are integrated Abstraction • Expose single interface distributed across large objects in NoSQL database vs transactional records stored in SQL database Support Multi-Tenancy • Enterprises offer multi-tenant architecture • Our customers are using our SDK to enforce tenant level security at the driver level without touching the hosted architecture. Other popular use cases we see need for virtual SQL access
  14. 14. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.14 Survey Question 3: Which of the following do you need SQL Access to? • Enterprise API Layer / Data Access Layer • Business Logic Layer • Single/Multiple Data Stores • Multi-Tenant Architecture • Other (Please share through comments)
  15. 15. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.15 Agenda  Background and Use cases for SQL Access  How to deliver SQL Access for REST APIs?  Demo  Best Practices
  16. 16. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.16 Customized SQL Connectivity OpenAccess SDK provides the majority of the code needed to SQL enable a data source. You generate the small amount of code (IP) residing between the SQL engine and your data store. This code processes the results generated by the SQL engine. Custom Code (IP) Implement just 12 functions in C/C++, Java or .NET It is the same code whether you are supporting ODBC, OLE DB, JDBC or .NET. The IP can be written in C, C++, Java or .NET. Interface Provider (IP)
  17. 17. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.17 Steps to Implement a Driver Design • Define the view of API data – schema • Determine how API will interact with SQL engine – row-based or query- based Setup • Determine features you will support – CRUD? • Implement the IP API functions by starting with template or one of our examples Test • Test sample queries through provided ODBCISQL application • Package for redistribution
  18. 18. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.18 OpenAccess can plug in to your enterprise security Image source: https://docs.oracle.com/cd/E55956_01/doc.11123/administrator_guide/content/admin_existing.html
  19. 19. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.19 Translating between SQL and REST ipExecute REST Call {JSON} IP CODE
  20. 20. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.20 SQL Support Broad SQL92 and SQL99 support • DDL – Create / Alter / Drop Tables, Views and Indexes • DML – Select, Insert, Update, Delete • Stored procedures – Call • Joins, unions, nested queries • Order By, Group By, Scalar Functions Join options • Push down to the server • SQL Engine performs Joins • Multiple Join Order options
  21. 21. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.21 A large Financial Company is using OpenAccess for ODBC, JDBC Access  Technology Needs: • BI team needed access to the data access layer from Microstrategy and IBM Cognos. • New applications need to be authorized by internal authentication and security layer.  Challenge: • They developed an in-house custom JDBC driver that wasn’t performing well. The driver had compatibility issues and maintenance was very expensive. • Now, they also need an ODBC driver to support a new BI tool within a strict timeline.  Solution: • With OpenAccess, they could deploy both an ODBC and JDBC driver in one go. • OpenAccess worked seamlessly with all of their 3rd party authentication and security tools. • Their alternative was to find an ODBC expert, develop the ODBC driver from scratch
  22. 22. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.22 Agenda  Background and Use cases for SQL Access  How to deliver SQL Access for REST APIs?  Demo  Best Practices
  23. 23. Demo
  24. 24. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.24 Agenda  Background and Use cases for SQL Access  How to deliver SQL Access for REST APIs?  Demo  Best Practices
  25. 25. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.25 Best Practices: Support Multiple APIs – ODBC, JDBC, ADO.NET  Some BI/Data Integration tools are Java and use JDBC, others are Native and use ODBC  Having to implement and test single interface layer saves in cost of ownership  Compatibility with enterprise BI and Data Integration tools – not all drivers are created equal JDBC Client ODBC Client OpenAccess SDK Interface Provider in Java Data Access Service API ADO.NET Client SQL
  26. 26. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.26 Best Practices: Authentication  Where to include code to integrate with IAM provider  How to handle OAuth flows and UI?  Authentication happens at execution time with REST APIs JDBC Client ODBC Client OpenAccess SDK Interface Provider in Java Data Access Service API ADO.NET Client SQL Authentication?
  27. 27. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.27 Best Practices: How to create data model from APIs  How to handle dynamic vs static metadata in API  Map API and fields to relational schema  Handling metadata for semi structured JSON responses JDBC Client ODBC Client OpenAccess SDK Interface Provider in Java Data Access Service API ADO.NET Client SQL Mapping metadata
  28. 28. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.28 Best Practices: Optimize Query Performance  Design enterprise API to allow search push- down, paging results, meta-data access  Push down filtering and other operations, possibly joins  Perform iterative design – simple to more complex  Implement rich SQL support because BI and ETL tools can generate very complex SQL queries JDBC Client ODBC Client OpenAccess SDK Interface Provider in Java Data Access Service API ADO.NET Client SQL Push-down search
  29. 29. © 2017 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.29 Next Steps 1. Schedule a meeting with our Product team [www.progress.com/company/contact] 2. Or Learn More: • OpenAccess Overview Guide • Download 30-day trial of OpenAccess • Tutorial to Build a Custom Driver over a REST API under 2 hours

×