Greg founded Ehcache in 2003. He regularly speaks at conferences, writes and codes. He has also founded and maintains the JPam and Spnego open source projects, which are security focused. Prior to joining Terracotta in 2009, Greg was Chief Architect at Wotif.com where he provided technical leadership as the company went from a single product startup to a billion dollar public company with multiple product lines. Before that Greg was a consultant for ThoughtWorks with engagements in the US and Australia in the travel, health care, geospatial, banking and insurance industries. Before doing programming, Greg managed IT. He was CIO at Virgin Blue, Tempo Services, Stamford Hotels and Resorts and Australian Resorts. He is a Chartered Accountant, and spent 7 years with KPMG in small business and insolvency. Greg holds a Bachelor of Commerce and a Masters in Information Technology.
I have talked to a lot of people about Ehcache over the years. What people find most valuable, and what stays with them, is the underlying caching theory - you can see the light bulb go on.
In this talk we will start with a performance problem and lead you through solving it with caching, discovering a long the way the problems of distributed caching and their solution. This will equip you with the tools to analyse a performance situation and to see whether a cache will help and what type of cache to apply.
Topics include:
- Why caching works
- Standalone cache performance and effectiveness
- Tiered Cache Design
- N * Problem
- Cache Cluster topologies
- Cache Coherency Problem
- CAP and PACELC constraints
- Overcoming Java’s limitations with BigMemory
- Useful Cache Patterns
In this session Greg Luck, founder of Ehcache and spec lead for JSR107 will walk you through this important new caching standard, which will form part of Java EE 7. You will learn:
- Getting started
- What caching is and when to apply it.
- Abstract your caching implementation with javax.cache
- Core API features
- Optional features and how they are handled by implementers and users
- Use the new caching annotations
- Concurrency and consistency
- Use the API before Java EE 7 is released within the Java SE, Java EE 6, and Spring environments
- Demo using the Ehcache 3.0 implementation
