Essential API Facade Patterns - Composition (Episode 1)

6,276 views

Published on

Published in: Devices & Hardware
1 Comment
10 Likes
Statistics
Notes
No Downloads
Views
Total views
6,276
On SlideShare
0
From Embeds
0
Number of Embeds
3,573
Actions
Shares
0
Downloads
173
Comments
1
Likes
10
Embeds 0
No embeds

No notes for slide
  • Creative Commons Attribution-Share Alike 3.0 United States License
  • Fewer Network calls from a device
  • Plug in a different service provider without having to change the app
  • Essential API Facade Patterns - Composition (Episode 1)

    1. 1. Essential API Facade PatternsEpisode 1 - CompositionSantanu Dey@Santanu_DeyBrian Mulloy Apigee@landlessness @apigee
    2. 2. groups.google.com/group/api-craft
    3. 3. slideshare.net/apigee
    4. 4. youtube.com/apigee
    5. 5. @Santanu_Dey @landlessness Santanu Dey Brian Mulloy
    6. 6. Webcast Series: API Facade PatternsEpisode 1CompositionEpisode 2Session ManagementEpisode 3One Phase to Two Phase ConversionEpisode 4Synchronous to Asynchronous
    7. 7. Episode 1 : Composition Pattern Problem Solution Benefits Considerations
    8. 8. Problem
    9. 9. Scenario: Mash-up App Service 1 Service 2Client Appon device Service 3
    10. 10. ProblemEstablish device connection to three hostsNegotiate API/Service security each timeNormalize data format inside the app logic on the device
    11. 11. Multiple Service Mash-up Service 1 Network connection, negotiate security, data format & parsing Service 2Client Appon device Service 3
    12. 12. Solution
    13. 13. API Service Layer Service 1 API Service Service 2 Layer Client Service 3
    14. 14. An Example Service 1 Book a Cab App API 2. Book Cab Service Service 2 Layer Client Service 3
    15. 15. Benefits
    16. 16. One-time authentication by the device.
    17. 17. Fewer network calls from a device.
    18. 18. Plug in a different service provider withouthaving to change the app.
    19. 19. Validate and control before the requests reachthe backend.
    20. 20. Request payload manipulation.
    21. 21. Opportunity to use Backend-as-a-Service withno additional expense to the application logic.
    22. 22. Generate analytics.
    23. 23. Other Considerations
    24. 24. Few other scenariosParallel calloutsCompensationChatty Services
    25. 25. Parallel Callouts Service API Book a Cab App from Service present location Layer Client Service
    26. 26. Another Example: Chatty Services 1. Get user attributes Service 2. Get recommended topics Provide r 3. Get recommended books Client
    27. 27. Solution: Reduce Chattiness 1. Authenticate by API key API 2. Get relevant user topics Service Get a recommended Service 2 book for a user Layer 3. Get recommended books Client
    28. 28. Questions?
    29. 29. THANK YOUSubscribe to API webcasts at:youtube.com/apigee
    30. 30. THANK YOUQuestions and ideas to:groups.google.com/group/api-craft
    31. 31. THANK YOUContact us at:@apigee@Santanu_Dey@landlessness

    ×