Martin Thompson discusses the major steps in the evolution of Java and how it contrasts to alternative technologies, and the challenges of pushing the limits of performance.
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.
Sponsored by Goldman Sachs. Java 8 has Streams, Scala has parallel collections, and GS Collections has ParallelIterables. Since we use parallelism to achieve better performance, it's interesting to ask: how well do they perform? We'll look at how these three APIs work with a critical eye toward performance. We'll also look at common performance pitfalls.
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.
Michael Dowden introduces JMeter and explains how to develop a data-driven methodology to determine some of the limits of a web application: max number of concurrent users, bottlenecks, etc.
In this solutions track talk, sponsored by Azul Systems, Gil Tene discusses common pitfalls encountered in measuring and characterizing latency, and ways to address them using some new open source tools.
Jonathan Worthington explains the garbage collection terminology, the trade-offs made by GC designers, and how to write GC-friendly code for better performance.
Dan North believes Agile scales if teams achieve contextual consistency through shared guiding principles, a clear vision and a common understanding.
Simon Marlow describes a concurrency-based system built with Haskell that allows front-end programmers to write business logic to access all the back-end services in a concise and consistent way.
Michael Nygard discusses several loopholes in the CAP theorem that can be used to engineer practical, real-world systems with desirable features.
Joe Armstrong describes the foundations of fault tolerant computation and the basic properties a system should have in order to be able to function in an adequate manner despite the occurrence of hardware and software errors, summarizing the key features of Erlang and showing how they can be used for programming fault-tolerant and scalable systems on multi-core clusters.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Featured Blog Posts
We get a lot of questions about our analytics-driven Application Performance Management (APM) collection and analysis technology. Specifically, people want to know how we capture so much detailed information while maintaining such low overhead levels. Read More.
Most technology folks have heard Marc Andreessen’s provocative statement, “Software is eating the world.” Whether you agree fully or not, you’re realizing that your business critical software applications increasingly drive both the top-line revenue growth and the bottom-line operational efficiency of your company – and often form the pillar of your business... Read More.
Wouldn’t do website load/performance testing any more without having an APM tool in place. Period. Full stop. End of story. I’ve been involved in website load testing for over 10 years, as a “end-user” when I was web operations manager for an online job board, as a team leader for a... Read More.
White Papers and Assets
|QCon SF||Nov 3-5|
|AppSphere 2014||Nov 3-5|