Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Some thoughts on evolving Edge Architectures

707 views

Published on

A presentation discussing: http://philcalcado.com/2015/09/18/the_back_end_for_front_end_pattern_bff.html

Published in: Software
  • Be the first to comment

Some thoughts on evolving Edge Architectures

  1. 1. Phil Calçado - @pcalcado philcalcado.com Some thoughts on evolving Edge Architectures
  2. 2. Phil Calçado - @pcalcado philcalcado.com Some thoughts on evolving Edge Architectures
  3. 3. (disclaimer)
  4. 4. what’s this 'edge' anyway?
  5. 5. MobileWeb Application Database Internet
  6. 6. Application Client-side
  7. 7. What about • Authorisation • Authentication • Rate-limiting • Geo-location • Session handling
  8. 8. Application Edge Client-side
  9. 9. the 1st few iterations
  10. 10. from monoliths to microservices is a well- documented process
  11. 11. Public API MobileWeb Application Database Internet
  12. 12. Application Database Mobile Web
  13. 13. when if you hit a wall
  14. 14. start off by making sure no new code goes in the monolith
  15. 15. Application Database Mobile Web Service A Service C Service B
  16. 16. then strangle the hell out of old stuff
  17. 17. Service A Service B Public API Web Mobile Application Database
  18. 18. when if you have edge performance problems
  19. 19. Service A Service C Service B Public API Web Mobile
  20. 20. GET /tracks/1234.json GET /tracks/1234/related.json GET /users/86762.json GET /users/me.json
  21. 21. Mobile Service A Service C Service B Mobile BFF Web Web BFF
  22. 22. GET /user-profile/123.json
  23. 23. be careful about duplicated logic
  24. 24. Mobile Service A Service C Service B Mobile BFF Web Web BFF User Profile Service
  25. 25. but if nothing else: do not start with an over-complicated architecture!
  26. 26. ?

×