FRAPI is an API management panel and developer-facing API that was created to address issues like laziness, performance problems, and the involvement of humans in API development. It allows developers to build APIs that are automatically generated and synchronized based on configurations in the management panel. FRAPI aims to improve performance and reduce complexity by removing unnecessary code and providing tools for authentication, content negotiation, database integration, and documentation generation.

1. Building APIs with FRAPI
@davidcoallier

2. Who are you?
Experiences, usage, etc.

3. Who am I?
Work, experiences, usage, etc.

4. The Talk!
Recap of why you are here...

5. FRAPI
Oh. My. Day!

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

7. Management Front-Facing API

8. History
When? Where? Why? How?

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

10. It’s live
Production system examples

11. Vodafone
Facebook apps

12. Open Source
Projects using FRAPI for their APIs

13. web2project
spaz

14. Enterprise
http://echolibre.com

15. Performance
Built with performance as primary goal.

16. Magic-less
There’s enough code out there

17. Few Setups
A few examples of possible FRAPI setups

23. Management
Where it all begins...

28. Authentication
HTTP Digest, reasons and modification

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

30. Negotiate
Content Negotiation and extensions

31. Synchronize
Generation of your code.

32. Documentation
Your consumers need documentation

33. Development
Decisions, business logic, software development

34. Important

35. Collections
http://api.com/friends

36. Resources
http://api.com/friends/david

37. Good URIs
Your URI is everything

38. Sentences
“What if we make every URL a sentence?”
@shiflett

39. Be Consistent

40. Scenario

46. Difference?
Leveraging the architecture, no more ugliness

47. Demo
Let’s take a real look :-)

48. Q&A