This document discusses FRAPI, a framework for building RESTful APIs. It provides both a management panel and developer-facing API for creating RESTful services. FRAPI aims to solve issues like laziness, performance problems, and long development times. It emphasizes building APIs with performance as a primary goal and without unnecessary complexity or "magic". The document outlines some of FRAPI's key features such as management, authentication, database support, content negotiation, code generation, and documentation. It also provides examples of projects using FRAPI and discusses development considerations.

1. RESTful APIs and FRAPI
a matter of minutes
@davidcoallier

2. FRAPI
Oh. My. Day!

3. What is it?
Management panel & developer facing API

4. History
When? Where? Why? How?

5. Solves?
Laziness, Performance Issues, Humans, TTM

6. It’s live
Production system examples

7. FLUD
Your iPad app newsreader

8. Vodafone
Facebook apps

9. Open Source
Projects using FRAPI for their APIs

10. web2project
spaz

11. Enterprise
http://echolibre.com

12. Performance
Built with performance as primary goal.

13. Magic-less
Fuck magic. There’s enough code out there

14. Few Setups
A few examples of possible FRAPI setups

20. Management
Where it all begins...

25. Authentication
HTTP Digest, reasons and modification

26. Databases
RDBMS, NoSQL, DBAL, ORM, etc.

27. Negotiate
Content Negotiation and extensions

28. Synchronize
Generation of your code.

29. Documentation
Your consumers need documentation

30. Development
Decisions, business logic, software development

31. Q&A