Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Network-Based Architectures: Paris // HTTP : Ha...

Network-Based Architectures: Paris // HTTP : Haussmann, Fielding, Fowler

erichoresnyi

October 14, 2015
Tweet

More Decks by erichoresnyi

Other Decks in Programming

Transcript

  1. 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
  2. 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
  3. 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
  4. DNS .gov, .com and .fr follow same scheme Seine is

    .root Streets start there Right/even Left/Uneven Paris street numbering, 1805
  5. 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.
  6. Stateless All clients are treated equal, no special treatment, no

    segregation Palais de Justice, Ile de la Cité
  7. 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
  8. Layered Networks Within a layer, a component connects to its

    neighboor Between two layers, gateways allow for interaction Each layer is autonomous @StreamdataIO #JAXLondon
  9. Code On Demand Les Halles, setting the tone for all

    restaurants in the City @StreamdataIO #JAXLondon
  10. Uniform Interface = Genious Codified UI, by floor (header), with

    token/key, proxy, cache @StreamdataIO #JAXLondon
  11. 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
  12. Error Handling in your code Gare Montparnasse, 1895 –HTTP or

    REST does not prevent from good error handling, contrib @rit
  13. Glossary Code Civil HTTP Paris Web Boulevards Internet Backbone Streets

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