Scaling and redis

2,079 views
2,017 views

Published on

Web applications, a lot of that expense and effort may be related to scaling, which is the capability of a system to handle an increasing amount of work gracefully or to be readily enlarged

Published in: Technology, Economy & Finance
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,079
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Scaling and redis

  1. 1. why background?App1 App2
  2. 2. why background?App1 App2
  3. 3. why background?App1 App2
  4. 4. why background?Frontend Daemo n
  5. 5. why background?Frontend DaemonFrontend Daemon
  6. 6. why background?Frontend DaemonFrontend CRASH! Daemon
  7. 7. why background?Frontend DaemonFrontend Daemon
  8. 8. why background?Frontend DaemonFrontend CRASH! Daemon
  9. 9. why background?Frontend Daemon Broker DaemonFrontend
  10. 10. why background?Fronten Fronten Daemon Fronten d Fronten d Fronten d Frontend d d Broker
  11. 11. why background? DaemoFronten Daemo Fronten Daemo n Fronten d Daemo n Fronten d Daemo n Fronten d Daemo n Frontend d Daemon n d n Broker
  12. 12. why background? DaemoFronten Daemo Fronten Daemo n Fronten d Daemo n Fronten d Daemo n Fronten d Daemo n Frontend d Daemon n d n Broker CRASH!
  13. 13. why background?Frontend DaemonFrontend Broker Daemon Staff Staff
  14. 14. why background?Frontend DaemonFrontend Broker Daemon CRASH! Staff Staff
  15. 15. why background? Broker DaemonFrontend Workflow DaemonFrontend Staff Staff
  16. 16. what we have ...1. various frontends2. backend daemons3. JSON messages
  17. 17. what we need1. a way to describe messageflow2. a easy flexible way to write andupdate it
  18. 18. what is workflow1. really only a path definitionthrough backends2. some sort of conditionmanagement3. a backend definition
  19. 19. { _id":"a7y9908898d5...k08b9351063","_rev": "6-688067711","name": "billing_info","type": "workflow","user": "adam","path": [ "logger", "billing","billing_jrcc_jw"] }
  20. 20. where are we it do?1. staff can call backends as before2. staff can call workflows via theworkflow queue3. staff can manage workflows inRedis
  21. 21. problem asynchronous callbacks1. staff starts a workflow2. staff calls some external API3. the external API somehow notifiesus (file attachment, email, URLcallback, ...) about progress4. staff needs to continue in theworkflow
  22. 22. how do staff correlate messages1. the backend daemon for thecallback polls a view in2. staff can search for any value inthe request they sent3. staff can search for the very valuethis external API uses as correlation_id

×