The Sacramento Java User Group meets
every month to discuss and discover new technologies that involve
Java and other electronic information systems. The group has been
meeting every month since the Java was released to the public back
in 1996. We are a volunteer group and the meetings are free to the
public. The hard work of its members and support of its sponsors
are the back bone of the group's success and longevity. We
recognize and appreciate those who have shared with the group
informative presentations and insightful discussion. It is those
members and guests who help make our meetings more enjoyable,
exciting and informative. Java is the language we speak and Java is the
language we love!
For those who are new or want to know details about the new
meeting location, SacJUG meetings are held at 6:00 p.m., on the
2nd Tuesday of the month at the ExitCertified office building.
ExitCertified is located at:
8950 Cal Center Drive
Suite 110, Bldg. 1
Sacramento, CA 95826
Members are encouraged to subscribe to
the SacJUG mailing lists. Outside of
our monthly meetings, our discussion list is the best place to
find out what's going on, to ask a question, or to meet new
Recruiters, here's how to get your job posting read at our monthly meeting,
or you can visit our announcement page
to post it electronically.
September 11, 2018
Tyler Van Gorder - Build.com
Evolving Your Distributed Cache In a Continuous Deployment World
A distributed cache can play a critical role in high volume, transaction environments. This talk will cover some of the unexpected challenges you may encounter with a distributed cache when multiple versions of your application are attempting to access the cache. We will discuss the caching problems we encountered as we moved our application from a monolithic deployment model to a continuous delivery model.
This will include a live demo (in Java) showing how multiple versions of the same object are cached within Redis and how a version can be promoted to different versions of the application if the structure of the object being cached has not changed.