Matt RaibleMatt Raible is a Java Champion and Developer Advocate at Okta. developer.okta.com

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

EhCache Project Busy this Summer

The EhCache project appears to be having a very busy summer. EhCache 1.5.0 (a major new version) was released on July 12th. In addition, a new (SOAP-based) EhCache Server was released at the end of July. You might ask yourself why you'd need such a beast. I think Greg explains it best:

Why am I doing this? There are lots of theories that have made their way on to the ehcache mailing list. The prosaic truth is that a large US corporate using ehcache for their Java apps on 200+ servers also wants to use it for their C++ apps. And they are prepared to sponsor development. The Web Services API lets them do it. That's it.

As to the larger question of how interesting this is to the world at large, my view is not very. However having to jump through all the hoops to get a server infrastructure done, I thought that the world at large may be interested in a RESTful, resource oriented ehcache server.

The next day, Greg announces EhCache for JRuby on Rails. A few days later, RESTful, resource-oriented caching becomes available in ehcache-server.

I guess this helps answer the question about OSCache vs. EhCache. OSCache hasn't had a release in over a year and EhCache is pumping out new releases and new products. Well done, Greg!

At LinkedIn, we use EhCache for many of our caching needs. However, it's likely we'll be moving to Memcached in the future. Since I'll be part of the team that implements Memcached, it'll be interesting to see which one performs better.

Posted in Java at Aug 10 2008, 09:12:31 PM MDT 7 Comments
Comments:

We're currently testing Memcached here at Rutgers for use with multiple CAS servers as the ticket backend and I have to say we're pretty impressed with the performance! We're actually using memcached with the repcache patch so we don't need a longer-term data store.

Posted by Scott on August 10, 2008 at 09:36 PM MDT #

Would be very helpful if you could list a few reasons why you guys are moving away from Ehcahce to memcached. thanks!

Posted by John on August 10, 2008 at 10:09 PM MDT #

I'm also curious on why you are moving to memcached and if you considered using terracotta (http://terracotta.org/) and if so why memcached was chosen over it.

Posted by Marcus on August 10, 2008 at 10:23 PM MDT #

Same here, I would love to see why you might prefer Memcached over Ehcache.

Currently I have implemented a Memcached solution at a client just because there core system is PHP + Memcached, so I have some experience with Memcached.

Pro's Ehcache:
- java native, which allows for both local in-memory as remote caching
- client libraries are better than Java clients for Memcached (whalin lib in no maven repository yet!).

Pro's Memcached:
- used in very scalable web sites (Facebook etc.)
- simple

Posted by Dirk de Kok on August 11, 2008 at 04:24 AM MDT #

@Marcus - Terracotta doesn't do much for us since we use a stateless architecture and don't cluster our servers. You can read more about the current architecture here.

If I can get approval, I'll try posting our reasons for choosing Memcached. I'll also try to post on how it performs after we put it into production.

Posted by Matt Raible on August 11, 2008 at 06:56 PM MDT #

Have you guys taken a look at Oracle Coherence? its the leading distributed memory cache provider amongst investment banks and offers a-lot more then just caching. Although it is pretty pricey

Posted by Douglas on August 15, 2008 at 06:18 PM MDT #

I talked to folks this week about Ehcache vs. Memcached. It turns out the reason we're moving to Memcached is we already have many existing systems using it and it's been working very well as a distributed caching system. We've also written our own Java API and have used it in production for quite some time.

Posted by Matt Raible on August 15, 2008 at 08:10 PM MDT #

Post a Comment:
  • HTML Syntax: Allowed