Adam Rocska discusses how to approach an enterprise web front-end architecture, including quality assurance, code documentation, deployment, architectural planning and task delegation.
Tim Fox discusses the design principles and motivation behind Vert.x and why the future is reactive.
Aviran Mordo introduces Wix's architecture, a highly available eventually consistent system, along with patterns for rendering many websites with a relatively small number of servers.
Jeff Hodges discusses tactics and strategy for creating distributed systems today and a little about what the future holds.
Jonas Bonér discusses four key traits of Reactive Apps: Event-Driven, Scalable, Resilient and Responsive, how they impact application design, how they interact, related technologies and techniques.
Paul Hill presents a case study of building an API with a short deadline using Node.js, WebSocket, MongoDB, JSON, Promises, Swagger, Memcached, Varnish and Hypermedia ReST.
Rajeev Borborah, Matthew Wilson discuss using NoSQL at WebMD -architecture, benefits, roadmap-, with details on caching and key-value storage implementation behind a few of the WebMD applications: Physician Finder, Symptom Checker and WebMD Runtime.
Oliver Wegner, Stefan Tilkov show how OTTO, Germany’s largest online fashion retailer, used a system-of-systems approach to enable modular, parallel development of its ambitious shop relaunch.
Adrian Cockcroft discusses strategies, patterns and pathways to perform a gradual migration from monolithic applications towards cloud-based REST microservices.
Randy Shoup describes KIXEYE's analytics infrastructure from Kafka queues through Hadoop 2 to Hive and Redshift, built for flexibility, experimentation, iteration, componentization, testability, reliability and replay-ability.
Tomas Petricek introduces F#’s capabilities in dealing with scientific data: type providers -CSV, XML, JSON, REST-, interactive development, data visualization libraries, integration with R or MathLab.
Ted Epstein shows how a shared canonical model can make life easier for API consumers, while still allowing the flexibility to expose different services, with different contextual requirements.