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.
NYT faбrikTimesOpen – 12 September 2012
Who Architect Infrastructure Group Previous   –   US Army   –   Harvard   –   Tech companies   –   United Nations      ...
What we’ll cover A story faбrik overview Code and demo                    3
Takeaways Application Developer   – Demand „events‟ (no polling, no thanks, been there, done that)   – Demand infrastruct...
The Story: Harvard U, 1986+ Bad:  –   No Internet (pre-web)  –   data locked in mainframe  –   large central clerical sta...
The Story: Harvard U, 1986+ Solution:   –   Relational database (decouple data from application)   –   Email backbone (de...
faбrik – Why?                ?                    7
NYT MissionEnhance society by creating, collecting anddistributing high quality news, information andentertainment- Distri...
faбrik Asynchronous Messaging Framework For client devices as well as our apps Enabled by:   – Websockets   – Robust me...
faбrik – solve the problem!                  App                              10
faбrik – basic                                   App                  Message Broker                                      ...
faбrik – basic                              Amazon Web Services                                   App                  Mes...
faбrik – basic++                                            App                Service                                    ...
faбrik: Current Implementation Open source  –   Erlang/OTP  –   RabbitMQ  –   Nodejs  –   Sockjs (websockets +)  –   Pyth...
faбrik – active/active cluster                       Region Wherever            Zone „a‟                     Zone „b‟     ...
faбrik – active/active cluster                       Region Wherever            Zone „a‟                     Zone „b‟     ...
faбrik         17
faбrik         18
faбrik         19
faбrik – Layers                  20
faбrik – Layers                  21
faбrik – Layers                  22
faбrik – Layers                  23
24
25
Pub / Sub            26
Pub / Sub            27
Pub / Sub            28
Pub / Sub            29
Pub / Sub            30
Gather / Analyze                   31
Gather / Analyze                   32
Gather / Analyze                   33
Gather / Analyze                   34
Gather / Analyze                   35
Gather / Analyze                   36
Gather / Analyze                   37
faбrik Demo Code         App               38
Upcoming SlideShare
Loading in …5
×

Faбrik - TimesOpen: Sockets and Streams - Sept. 2012

914 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Faбrik - TimesOpen: Sockets and Streams - Sept. 2012

  1. 1. NYT faбrikTimesOpen – 12 September 2012
  2. 2. Who Architect Infrastructure Group Previous – US Army – Harvard – Tech companies – United Nations 2
  3. 3. What we’ll cover A story faбrik overview Code and demo 3
  4. 4. Takeaways Application Developer – Demand „events‟ (no polling, no thanks, been there, done that) – Demand infrastructure that scales and you don‟t have to worry about Infrastructure Engineer – Decouple, flatten, simplify – Outsource complexity 4
  5. 5. The Story: Harvard U, 1986+ Bad: – No Internet (pre-web) – data locked in mainframe – large central clerical staff – monolithic central systems Good: – Vision of an Information Utility – desire to innovate – lots of desktop computers (30,000) – email everywhere although over diverse networks and technologies 5
  6. 6. The Story: Harvard U, 1986+ Solution: – Relational database (decouple data from application) – Email backbone (decouple producers from consumers) – Event-driven desktop applications (flatten) – Identical code on mainframe (simplify) Result: – Data warehouse unlocked (before the term was coined) – Central clerical staff functions upgraded/dispersed – Old central systems replaceable and, ultimately, replaced – Happy users! 6
  7. 7. faбrik – Why? ? 7
  8. 8. NYT MissionEnhance society by creating, collecting anddistributing high quality news, information andentertainment- Distributing: publish / subscribe- Collecting: gather / analyze- High Quality: fast, reliable, accurate 8
  9. 9. faбrik Asynchronous Messaging Framework For client devices as well as our apps Enabled by: – Websockets – Robust message handling software – Amazon Web Services Focusing on simple, common services 9
  10. 10. faбrik – solve the problem! App 10
  11. 11. faбrik – basic App Message Broker App App 11
  12. 12. faбrik – basic Amazon Web Services App Message Broker • EC2 • S3 App • Identity & App Access Mgt • DynamoDB • Route 53 … 12
  13. 13. faбrik – basic++ App Service Buddy Buddy Message Broker “Retail” Message Broker“Wholesale” Service Buddy Other App 13
  14. 14. faбrik: Current Implementation Open source – Erlang/OTP – RabbitMQ – Nodejs – Sockjs (websockets +) – Python (gevent, select/epoll, tornado, futures, …) – ZeroMQ (new) Automated build/deployment 14
  15. 15. faбrik – active/active cluster Region Wherever Zone „a‟ Zone „b‟ Service Service Buddy Buddy „a‟ „b‟ 15
  16. 16. faбrik – active/active cluster Region Wherever Zone „a‟ Zone „b‟ Service Service Buddy Buddy „a‟ „b‟ 16
  17. 17. faбrik 17
  18. 18. faбrik 18
  19. 19. faбrik 19
  20. 20. faбrik – Layers 20
  21. 21. faбrik – Layers 21
  22. 22. faбrik – Layers 22
  23. 23. faбrik – Layers 23
  24. 24. 24
  25. 25. 25
  26. 26. Pub / Sub 26
  27. 27. Pub / Sub 27
  28. 28. Pub / Sub 28
  29. 29. Pub / Sub 29
  30. 30. Pub / Sub 30
  31. 31. Gather / Analyze 31
  32. 32. Gather / Analyze 32
  33. 33. Gather / Analyze 33
  34. 34. Gather / Analyze 34
  35. 35. Gather / Analyze 35
  36. 36. Gather / Analyze 36
  37. 37. Gather / Analyze 37
  38. 38. faбrik Demo Code App 38

×