Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Bringing javax.cache'ing To Your Spring Applications

DZone's Guide to

Bringing javax.cache'ing To Your Spring Applications

A presentation from SpringOne2GX 2015 on the features of a new standardized caching API for Java, and how to use it in Spring Apps.

· Java Zone ·
Free Resource

How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

Recorded at SpringOne2GX 2015.

Speakers: Jeff Brown, OCI Web

Slides: http://www.slideshare.net/SpringCentral/bringing-javaxcacheing-to-your-app

10 years in the making and finally JSR-107 has been finalized. We now have a standardized Caching API for the Java Platform. And that’s all ready for you to use in your Spring apps. But what does it really enable for you? What’s with these optional features? No transaction support? How do you efficiently make use of this new API to solve real world problems in your application today? We’ll look into how get you best started introducing caching into your Spring application to solve real world problems. And, as we explore the javax.cache API in much more details, we’ll see how to push the specifications to its limits and… beyond. Whether implicitly through frameworks (like Spring and Hibernate), or explicitly (cache-aside, cache-through, …). And how to abstract yourself from a given provider when you require more than what the specifications cover (e.g. transactional caches). We’ll also cover some implementer specifics you might want to account for when choosing an implementation, especially if you plan to push the spec to the extreme, like when going distributed and caching terabytes of data.


How do you break a Monolith into Microservices at Scale? This ebook shows strategies and techniques for building scalable and resilient microservices.

Topics:
spring ,java ,caching ,api

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}