network based architectures
play

Network-based Architectures Fowler, Fielding, and Haussmann The - PowerPoint PPT Presentation

Eric Horesnyi | streamdata.io Network-based Architectures Fowler, Fielding, and Haussmann The Digital gap @StreamdataIO #JAXLondon Haussmann & Fielding 1853, Paris 2000, Irvine @StreamdataIO #JAXLondon Haussmann Fielding and


  1. Eric Horesnyi | streamdata.io Network-based Architectures Fowler, Fielding, and Haussmann

  2. The « Digital » gap @StreamdataIO #JAXLondon

  3. Haussmann & Fielding 1853, Paris 2000, Irvine @StreamdataIO #JAXLondon

  4. Haussmann Fielding and Fowler CHALLENGES IN PARIS,1853 @StreamdataIO #JAXLondon

  5. High Dropout Cholera, 1832 – 19,000 dropout @StreamdataIO #JAXLondon

  6. Congestion 1hab/sq mt density @StreamdataIO #JAXLondon

  7. Slow & Unsecure Security threats: No inspection possible obscure streets No patches to remove viruses and threats lack of air circulation Poor latency: slow access lines narrow streets Street in Ile de La Cité Early XIXth

  8. Unstable system Full reboot 1789, 1815, 1830, 1848 … No backward compatibility No service desk Restricted vote DDOS in small access lines Barricades Liberty Leading the People, July 28th, 1830' by Delacroix

  9. Haussmann Fielding Fowler INHERITED FEATURES HTTP//PARIS 1789-1853 @StreamdataIO #JAXLondon

  10. Inherited Properties @StreamdataIO #JAXLondon

  11. DNS .gov, .com and .fr follow same scheme Seine is .root Streets start there Right/even Left/Uneven Paris street numbering, 1805

  12. Famous heritage Napoleon, France 1804 Tim Berners-Lee, CERN ‘90 Comment: // limited to ability to establish basic rules. I do not admire Napoleon for anything else.

  13. Separation of concerns Client Server @StreamdataIO #JAXLondon

  14. Stateless All clients are treated equal, no special treatment, no segregation Palais de Justice, Ile de la Cité

  15. Stateless Client access server via a network call

  16. Haussmann Fielding Fowler SELECTION OF PROPERTIES FIELDING // HAUSSMANN REST // PARIS @StreamdataIO #JAXLondon

  17. Mission Network performance throughput, small overhead, bandwidth User-perceived performance latency, and completion Network-efficiency avoid using the street too much. Homeworking Napoleon III describing his mission to Haussmann, 1853

  18. KPIs Haussmann // Fielding Scalable make it possible for Paris to grow Simple no need for a city-user manual, Modifiable ability to evolve in the future through change Extensible add new neighborhood Customizable specialize a building without impacting others Configurable easily modify a building post-deployment Reusable building can host a bakery then a cremerie Visible to provide best security and auditability Portable style should work well in other regions Reliable susceptible to failure (no single event could stop water, gas or circulation for citizens) @StreamdataIO #JAXLondon

  19. P1: Low-Entry Barrier A popular neighborhood in Paris @StreamdataIO #JAXLondon

  20. P2: Extensibility Streaming = Paris Metro/Subway, 1900 @StreamdataIO #JAXLondon

  21. P3: Distributed Hypermedia @StreamdataIO #JAXLondon

  22. P4: Anarchic Scalability Paris Metropole today, 10m+ people @StreamdataIO #JAXLondon

  23. P6: Independant Deployment Ile de La Cité restructured, embedding legacy/sacred Notre Dame @StreamdataIO #JAXLondon

  24. Haussmann Fielding Fowler WHY HAUSSMANN DECIDED TO MAKE PARIS RESTFUL @StreamdataIO #JAXLondon

  25. REST=LCODC$SS&UI CSS=Client-Server-Stateless @StreamdataIO #JAXLondon

  26. Layer 1: sewage & gas @StreamdataIO #JAXLondon

  27. Layer 2: street & boulevards @StreamdataIO #JAXLondon

  28. Layer 3: roofs @StreamdataIO #JAXLondon

  29. Layered Networks Within a layer, a component connects to its neighboor Between two layers, gateways allow for interaction Each layer is autonomous @StreamdataIO #JAXLondon

  30. Cache 700 concurrent clients 80,000 in cache 2m records St Geneviève Library, 1850 @StreamdataIO

  31. Cache Opera, a server with cache #Tech2Day

  32. Code On Demand Les Halles, setting the tone for all restaurants in the City @StreamdataIO #JAXLondon

  33. Uniform Interface = Genious Codified UI, by floor (header), with token/key, proxy, cache @StreamdataIO #JAXLondon

  34. Uniformity = beauty inside Uniformity in APIs brings harmony in UX @StreamdataIO #JAXLondon

  35. Uniformity = pattern beauty Uniformity brings fractal harmony: still there from a distance @StreamdataIO #JAXLondon

  36. Continuous Delivery & Microservices HAUSSMANN // FOWLER AS URBANISTS @StreamdataIO #JAXLondon #Tech2Day

  37. Continuous Delivery Resilient Water Induction, requiring aqueducts and reservoirs @StreamdataIO #JAXLondon

  38. Continuous Delivery Reservoir, Arcueil Aqueduct, Arcueil @StreamdataIO #JAXLondon

  39. Microservices Not too big Autonomous components Own API Standard protocol Scalable @StreamdataIO #JAXLondon

  40. Zoning Quartier Panthéon, a zone dedicated to “The Big Men”

  41. Lead by example Opera, an Hypermedia API > great UX >>> traction for API owners

  42. Cut Corners Haussmann corners: Most difficult piece & beautiful

  43. Polyglot XVIII architecture encapsulated, if API complies @StreamdataIO #JAXLondon

  44. Sustainable systems? PARIS 160 YEARS LATER HTTP REST 16 YEARS LATER @StreamdataIO #JAXLondon

  45. UX performance City of Lights: 20m unique visitors a year

  46. Reproductible Chicago after the Burnham Plan, designed in 1909

  47. Durable Courneuve, 1986, 20y lifespan Monolith

  48. Evolvable Tour Eiffel under construction, evolution built years after Haussmann had left office

  49. Haussmann Fielding Fowler DAYTODAY LIFE IN A RESTFUL CITY @StreamdataIO #JAXLondon

  50. Incomplete Protocol: Velib Leverage reusable assets Share same layer as existing traffic But incomplete protocol: collisions, missing RFC for cars Rate-limited API, realtime difficult @StreamdataIO #JAXLondon

  51. Error Handling in your code Gare Montparnasse, 1895 –HTTP or REST does not prevent from good error handling, contrib @rit

  52. Haussmann Fielding Fowler HTTP//PARIS DICTIONARY, MAPS & RESSOURCES @StreamdataIO #JAXLondon

  53. Glossary Code Civil HTTP Utilities Cloud/PaaS Paris Web Annonces Parisiennes Criteo Boulevards Internet Backbone Grands Magasins Amazon Streets Access Lines Opera Deezer Street Numbers URI Theaters Netflix Light in the streets Authentication Prefecture NSA Concierge Proxy Bibliotheque Nat. Wiki Library Cache Senat W3C Carriage Request/Response Assemblee Nationale IETF Subway/Metro Streaming Louvre Pinterest Homeworking Diff update// JSON Patch Bois de Boulogne MineCraft Pierre de Carrière JSON Bois de Vincennes Facebook Compagnon du Devoir API Developer Bon Marché Ebay Haussmann Architect Eiffel Tower Twitter Beaux Arts JS Developers Latin Quarter Udacity, Coursera Façade API Left bank spirit Android Haussmann Façade RESTful API Right bank spirit Apple iPhone @StreamdataIO #JAXLondon

  54. Resources Paris Architecture & Urbanism: Musée Carnavalet, Cité Chaillot Haussmann: Haussmann à Paris : Architecture et urbanisme Seconde moitié du XIXe siècle, Book, 2012 HTTP: Tim Berners-Lee & Team, Cern, 1990 REST: Network-Based Architecture Style, Thesis, Fielding 2000 Continuous Delivery : Farley & Humbl, 2010 Microservices : Microservices in a Nutshell, Fowler & Lewis, Thoughtworks, 2014 Web Corp Organization: How Google Works, Eric Schmidt, 2014 Design & UX : Jonathan Ive, Apple by The New Yorker, 2015 Microservices Building Microservices, Sam Newman, O’Reilly Book, 2015

Recommend


More recommend