CData Data Today: A Developer's Dilemma

The State of Data Today
A Developer’s Dilemma

See the World as a Database
Agenda
• Introduction
• A Sample Company’s Data
• The Problem: Disparate APIs & SDKs
• The Solution: Common Interfaces
• Code Samples

• Over 2 decades of experience
(since 1994) in building
integration components.
• 80+ Data Sources
• ‘See the World as a Database’
About CData Software
• Started: 1994
• Location: Chapel Hill, NC
• CData Software (formerly
RSSBus), a spin-off of
/n software.

A Sample Company’s Data
QuickBooks (Accounting & PoS)
Exact Online (Warehousing & Logistics)
HubSpot (CRM)
Microsoft Project (Project/Scheduling)
On-premises & cloud-based MySQL databases
Facebook & Twitter (Social Media data)

Accessing A Sample Company’s Data
REST APIs
XML APIs
SDKs
Authentication
Basic & OAuth

The Problem: Disparate APIs & SDKs
REST/SOAP APIs & SDKs model data differently
SDKs are language-dependent
Changes break existing tools
Lack of data-centric functionality

The Solution: A Common Interface
Built using established standards
Developers learn a single protocol
Data-centric model
Power of SQL (JOINs, filtering, aggregation)
Easily browse data
API/SDK/data model changes are covered

Digging In: How Do They Work?
Mapping APIs & SDKs to a relational model
Tables and Views correspond with resources
One resource per row
Nested values represented as JSON
Sub-collections are treated as related tables
SQL queries roughly match HTTP verbs
Stored procedures are used for other operations

Digging In: How Do They Work?
INSERT means more than creating a resource
Major SQL features supported across sources
Complex queries utilize API/SDK calls and memory
Bulk operations are supported, where possible
Advanced queries utilize API/SDK functionality

When are SDK/APIs better?
Data streaming
Event-driven applications
Language-centric development

Code Sample: Reading MySQL Data
using System.Data.CData.MySQL;
String connectionString =
"User=myUser;Password=myPassword;Database=myDatabase;Server=myServer;Port=3306;";
using (MySQLConnection conn = new MySQLConnection(connectionString)) {
MySQLCommand cmd = new MySQLCommand("", conn);
MySQLDataReader rdr;
cmd.CommandText = "SELECT * FROM Orders";
rdr = cmd.ExecuteReader();
while (rdr.Read()) {
//process results
}
}

Code Sample: Updating QuickBooks Data
using System.Data.CData.QuickBooks;
String connectionString = "User=test;Password=test;URL=http://localhost:8166;";
using (QuickBooksConnection conn = new QuickBooksConnection(connectionString)) {
QuickBooksCommand cmd = new QuickBooksCommand("", conn);
cmd.CommandText = "UPDATE Customers SET Name='Hook, Captain' WHERE Id = @myId";
cmd.Parameters.Add(new QuickBooksParameter("myId", "12345678-9876543210"));
cmd.ExecuteNonQuery();
}

Calling Stored Procedures
Stored procedures represent non-CRUD actions
Called using name and passing appropriate parameters
Results can be read, stored, and processed

Code Sample: Upload Media to Twitter
using System.Data.CData.Twitter;
String connectionString = "OAuthAccessToken=...;OAuthAccessTokenSecret=...;" +
"OAuthClientId=...;OAuthClientSecret=...;";
using (TwitterConnection conn = new TwitterConnection(connectionString)) {
TwitterCommand cmd = new TwitterCommand("UploadMedia", conn);
cmd.CommandType = CommandType.StoredProcedure;
cmd.Parameters.Add(new TwitterParameter("MediaFilePath#1", "path/to/file1"));
TwitterDataReader rdr = cmd.ExecuteReader();
while (rdr.Read()) {
//process results
}
}

Desktop/Server apps call the Stored Procedure:
GetOAuthAccessToken
Web apps call the Stored Procedures:
GetOAuthAuthorizationUrl
GetOAuthAccessToken
Optional: allow the Drivers to manage OAuth flow
Performing OAuth Authentication

Code Sample: Exact Online OAuth Flow
using System.Data.CData.ExactOnline;
string connectionString = "Region=’United States’;OAuthClientId=...;OAuthClientSecret=...;";
string accessToken, refreshToken, expiresIn;
accessToken = refreshToken = expiresIn = string.Empty;
using (ExactOnlineConnection conn = new ExactOnlineConnection(connectionString)){
ExactOnlineCommand cmd = new ExactOnlineCommand("GetOAuthAccessToken", conn);
cmd.CommandType = CommandType.StoredProcedure;
cmd.Parameters.Add(new ExactOnlineParameter("CallBackUrl", "https://localhost:7777"));
ExactOnlineDataReader reader = cmd.ExecuteReader();
if(reader.Read()){
accessToken = (string)reader["OAuthAccessToken"];
refreshToken = (string)reader["OAuthRefreshToken"];
expiresIn = (string)reader["ExpiresIn"];
}
}
connectionString += "OAuthAccessToken=" + accessToken + ";OAuthRefreshToken=" + refreshToken + ";";

Data Sources

Thank You!
In Conclusion
Learning Disparate APIs/SDKs are Costly
Common Interfaces Provide Easy Access to Data
Questions?

CData Data Today: A Developer's Dilemma

More Related Content

What's hot (20)

Viewers also liked (11)

Similar to CData Data Today: A Developer's Dilemma (20)

Recently uploaded (20)

CData Data Today: A Developer's Dilemma

Editor's Notes