1355 Market Street, Suite 900, San Francisco, CA
*PLEASE NOTE: This event has been postponed (due to presenter's family emergency). We invite you to come to the event on JavaEE7/WildFly8 scheduled for the same date.
Since its inception in 2007, OpenJDK has always been a bit confusing - living a parallel life to its "official" cousin, the Sun/Oracle JDK. Some parts were missing, others did not work as well, but in 2011 it become the reference implementation of Java SE. Yet, to this day, most Java shops tend to stick with the tried-and-true, and avoid using OpenJDK in production.
When Twitter switched from Ruby/Rails to Java, it needed something that would scale to 10,000s requests/sec per VM, and OpenJDK fit the bill perfectly. Not only did it prove production-ready, but its openness enabled Twitter engineers to extend it and deploy it internally to run its data centers with huge advantages for both developer support and system efficiency.
Join David Keenan who offered to tell us why and how Twitter develops and deploys OpenJDK. The talk will also discuss Twitter's future plans with contributing its work back to the OpenJDK community.
For those of you interested in the massive scale with the JVM, check out the video of Kaushik Srenevasan who talked about about Tracing and Profiling Java applications in production back in November.
About David Keenan
David Keenan (@dagskeenan) runs the Managed Runtimes and Performance Engineering team at Twitter. He is also the chair of the Java subcommittee at SPEC.org, and spent 15 years at Oracle/Sun working on the performance of the Java platform.