Mobile backend without REST

1. REST LESS APP MOBILE FIRST BACKEND
2. REST?
3. TEXT SHORT HISTORY OF REST ▸ 1996 - developing the pattern ▸ 2000 - formalizing the pattern ▸ 2010 - spreading around the world. http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
4. TEXT REST REQUIREMENTS ▸ Client - Server ▸ No client state ▸ No client session on a client ▸ Caching (CDN and HTTP powered) ▸ Resource by URL / URI http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
5. TEXT REST PROBLEMS ▸ Versioning ▸ Discoverability ▸ Dynamic API ▸ Assumption Driven Development
6. SERVER FIRST
7. MOBILE FIRST?
8. TEXT MOBILE NEEDS ▸ Multiple Environments ▸ Versioning (multiple versions in store) ▸ Minimum logic on client side ▸ Sessions ▸ Feature toggles ▸ API Spec
9. TEXT MICROSERVICES ▸ Multiple Instances ▸ More like distributed objects ▸ Composition enabled ▸ Feature oriented
10. TEXT MICROSERVICES ▸ Multiple Instances ▸ More like distributed objects ▸ Composition enabled ▸ Feature oriented
11. TEXT CONFIG SERVICE REQUEST "context": { "version": "1.0", "locale": "en_US", "bundle": "com.my.food-delivery", "device": "iPhone", "screen": { "width": 320, "height": 480 }, "uuid": "ABCD-1234-1242-1564", ... }
12. TEXT CONFIG SERVICE RESPONSE "config": { "menu": { "search": { "url": "https://m.com/menu/v1/search", "context": { "session": "ABCD-1234-1242-1564", "currency": "USD" } }, "popular": [ ... ], ... }, ... }
13. TEXT CONFIG SERVICE RESPONSE "error": { "kind": "temporal", "message": "We are updating our service, please wait up to 2 AM of tommorow." }
14. TEXT CONFIG SERVICE RESPONSE "error": { "kind": "permanent", "message": "Please download new version from App Store", "action": "app store page" }
15. TEXT SEARCH SERVICE REQUEST "search": { "term": "sushi", "context": { ... } }
16. TEXT SEARCH SERVICE RESPONSE "items": [ { "title": "Roll", "price": "18 USD", "markAsFavorite": { "url": "http://food.com/markAsFavorite", "context": { "id": 1990, "user": "ABCD-1234-1242-1564" } }, } ]
17. CODE IS DATA
18. TEXT NEXT STEPS ▸ Tell server about needed data ▸ GraphQL ▸ Remote code injection
19. TEXT CONFIG SERVICE REQUEST "context": { ... "menu": { "search": { "url": { "type": "$url" }, "json": { "type": "$object", "variables": ["$term"] } } } }
20. TEXT CONFIG SERVICE RESPONSE "config": { "menu": { "search": { "url": "https://food-delivery.com/menu/v1/search", "json": { "term": "$term", "session": "ABCD-1234-1242-1564", "currency": "USD" } } } }
21. GRAPH QL http://graphql.org
22. REACT NATIVE https://facebook.github.io/react-native/
23. SERVER APP LOGIC UI
24. SERVER APP LOGIC UI
25. WHY IT IS IMPORTANT?
26. PROJECTS ARE DEAD
27. TEXT PRODUCT TRAITS ▸ Dynamic set of functionality ▸ Data driven decisions ▸ Weekly updates
28. QUESTIONS? dalog@me.com