This document discusses publishing SQL data as web APIs. It introduces the presenter and their background working with REST APIs and web frameworks. It then outlines three common use cases for exposing SQL data via REST APIs: allowing citizens to integrate data, opening data to other applications, and providing global access. The document raises concerns about caching, latency, scalability, and querying that APIs may need to address and provides examples of API caching and high availability solutions. It also briefly describes some existing API framework and platform options for building APIs with different levels of control, cost, and time to deployment.

1. Publish your
SQL Data
as Web APIs
Presented by Jérôme Louvel, Chief Geek

2. About me
● Created Restlet Framework, first REST framework in 2004
● Contributor to “RESTful Web Services” (O’Reilly, 2007)
● Member of the JAX-RS 1.0 expert group (2007 - 2009)
● Co-author of “Restlet in Action” (Manning, 2012)
● InfoQ editor covering Web APIs since 2014
● CEO & Founder of Restlet, Web API platform vendor

4. DATA

5. Citizen
Integrator

6. 1 | Use Case: Citizen Integrator
SQL
data

8. 2 | Use Case: Open Data
Other
DB
SQL
data

9. Global
Access

10. 3 | Use Case: Global Access
United States
Australia
Germany
Japan
United Kingdom
Brazil
India
Canada
SQL
data

12. Synchronize
SQL to the cloud ?

14. 1 | Use Case: Citizen Integrator
SQL
data
REST
API

15. 2 | Use Case: Open Data
SQL
data
REST
API
Other
DB

16. 3 | Use Case: Global Access
SQL
data
REST
API
United States
Australia
Germany
Japan
United Kingdom
Brazil
India
Canada

17. Let’s
build our
own API!

18. CONCERNS
caching
latenc
HA
scalability
paging,
sorting,
filtering,
querying...

19. Too much traffic?
API caching!

20. Latency,
you said?

21. 5 nine high availability

22. Scalability

23. paging
queries
filtering
sorting

24. Generic API Custom API

26. IPs API

27. Secure
tunnel

28. cloud &
enterprise,

29. Some Products Available
API frameworks
● open source
● high level of control
● need skills / time
Enterprise API Product
● powerful / complex /expensive
● on-premises deployment
● longer time to deployment
API PaaS
● self-service / cloud based
● built-in API [and DB] hosting
● shorter development cycle

30. APISpark - Project creation

31. APISpark - Entity Store

32. APISpark - Web API exported

33. DATA

34. Thank you
Q&A