The document outlines a method for deploying web APIs using an all-in-one platform, emphasizing the differences between do-it-yourself (DIY) approaches and Platform as a Service (PaaS). It details a typical lifecycle for creating and managing web APIs, which includes building a data source, creating the API, deploying it, and promoting it, all with a focus on speed and efficiency using PaaS solutions. The final goal is to simplify the API creation process, making it accessible and manageable, akin to platforms like WordPress for web content.

1. DEPLOY A WEB API IN 15’
All-in-one platform for Web APIs
http://apispark.com
Jérôme LOUVEL
jlouvel@restlet.com
CEO
October 24, 2013

2. WEB API PROJECT
TYPICAL LIFE CYCLE
1) Do It Yourself (DIY)
long, risky, expensive but highly flexible
Create
Host
Manage
Use
2) Platform as a Service (PaaS)
integrated, fast, cost effective
Promote

3. Step 1
BUILD YOUR DATA SOURCE

4. DIY APPROACH
 Select a database technology
 that scales
 Specify the schema
 tables / sets, keys / queries, indexes
 Setup the database
 On premise or in the Cloud
 Ensure security, high availability and
performances
 From days to weeks

5. PAAS WAY
SOCIAL LOGIN

6. PAAS WAY
YOUR DASHBOARD

7. PAAS WAY
ENTITY STORE CREATION

8. PAAS WAY
DATABASE AS A SERVICE

9. Step 2
CREATE YOUR WEB API

10. DIY APPROACH
 Select an API framework that
 Lets you be productive and gets you on the way
 Leverages your skills
 Ensures your web API will scale and be secure
 Write the code
 Code, debug, unit tests
 Read, write, update your data
 Package the code
 From days to weeks

11. PAAS WAY
WEB API CREATION

12. PAAS WAY
FULLY AUTOMATED

13. Step 3
DEPLOY YOUR WEB API

14. DIY APPROACH
 Choose a deployment target
 Private hosting with firewall / DMZ
 Public hosting : Cloud / Dedicated
 Select an API management solution
 Build your own from Open source, third
party products
 Leverage an API management service :
plug it in tasks and side effects
 Guaranty your SLA
 Test, QA, iterate, benchmark…
 From days to weeks to get started

15. PAAS WAY
INSTANT DEPLOY AND AUTO SCALE

16. Step 4
PROMOTE YOUR API

17. DIY APPROACH
 Write your API documentation
 Annotated your API code and generate ?
 Use HTML tooling ?
 Maintenance costs (versions sync)
 Write your client SDKs
 Write first SDKs or use a generator
 Hope for community contributions for others ?
 Test, QA, iterate, etc.
 From days to weeks to get started

18. PAAS WAY
GENERATE CLIENT SDKS

19. PAAS WAY
BUILT-IN ANALYTICS

20. HOW MANY APIS ?
TO BUILD AND MAINTAIN
Browser
HTTP
Connected
devices
Pages + API
Smart
environment
Web Site
Business
Partners
Internal IT

21. FINAL THOUGHTS
 How to build 1 million API in 2017 ?
– with radically simpler PaaS for Web APIs
– an equivalent of Wordpress.com & Tumblr for APIs
– truly democratize Web APIs !
Source: Wired / June 2013

22. KEEP IN TOUCH!
http://apispark.com
http://blog.restlet.com
Twitter: @apispark
jlouvel@restlet.com
Research report written by Kin Lane
for GigaOM, undersigned by Restlet