InfoQ Homepage Case Study Content on InfoQ
-
Painful Success - Lessons Learned while Scaling Up
Jesper Richter-Reichhelm shares lessons learned from failures while scaling Wooga games to millions of daily users.
-
How a Graph Database Allows Shutl to Deliver Even Faster
Volker Pacher explains why Shutl chose Neo4j when faced with the need of building a new API meant to support business growth, the challenges met during implementation and solutions applied.
-
Architecture of the Triposo Travel Guide
Jon Tirsen and Douwe Osinga tell Triposo’s story from a small hobby project to the large architecture of today. Triposo is a mobile phone travel guide.
-
Trying out Kanban at Comcast
Trevor Lalish-Menagh shares his experience introducing Kanban, what has worked and what hasn’t.
-
How We Scaled Songkick for More Traffic and More Productive Development
Marc Pacheco tells how Songkick made radical changes to increase the performance of the site while retaining a productive development team.
-
Inside Lanyrd's Architecture
Andrew Godwin tells Lanyrd’s story, covering the technology stack, tricks used, and what they would do differently if they could start afresh.
-
The Strangler Pipeline: Winning over Hearts and Minds
Steve Smith shares some of the change patterns used to establish continuous delivery at Sky Network Services over the past 2 years, and how they fit into an optimal cycle time strategy.
-
The Process, Technology and Practice of Continuous Delivery
Dave Farley introduces the ideas of Continuous Delivery as a practical everyday process, using some of the techniques and technologies from a real world project as an example.
-
Developing the FT Web App
Robert Shilston demoes an FT app, discussing: layout and interactions,native wrappers,testing and QA, and how to manage regular, reliable and successful deployments of an offline cached application.
-
Building a PaaS in Clojure
Allen Rohner shares the difficulties encountered and the lessons learned building a PaaS in Clojure.
-
Lessons from Building and Scaling LinkedIn
Jay Kreps discusses the evolution of LinkedIn's architecture and lessons learned scaling from a monolithic application to a distributed set of services, from one database to distributed data stores.
-
Can Technology Innovation Save The New York Times?
Marc Frons discusses the New York Times’ digital subscription model. Rajiv Pant shares their experiences transitioning to continuous delivery, and using NodeJS, Scala, cloud and big data.