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.
Mike Amundsen reviews patterns in developer practices and trends in services and libraries - from the increase in the number of client-side libraries such as EmberJS, Angular, and Bootstrap to the appearance of new "API composition" platforms such as Strong Loop - that give us a picture of why it's important to identify and leverage the growing sentiment that "Clients Matter, Services Don't".
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.
John Musser takes a look at some of the common mistakes made by API providers, providing advice on what can be done to avoid them.
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.
Roland Kuhn introduces the principles of reactive applications, providing guidance on how to create reactive systems.
Darren Hobbs shares lessons learned building polyglot systems, the technology choices made. mitigating risk and delivering value.
Didier Verna keynotes on the bonds between biology and computer science, how these bonds developed over the years, and how software could behave like living organisms.
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.