This site uses affiliate links as a means of monetization.
Following on from the recent release of dotCMS Enterprise Cloud, dotCMS has unveiled version 3.3 of their platform.
dotCMS is a platform with a track record in the enterprise market, and can be utilized either on-premise or via the cloud. It was also the winner of the 2014 Critics' Choice Award for Best Cloud CMS for SMB.
Here's what's new with dotCMS 3.3.
Cold Hard Cache
With 3.3, dotCMS has seriously revamped the way it handles caching.
First and foremost, the new advanced caching schemes with external cache are designed for use in high availability and low latency situations.
Here's a breakdown of the new features, which aim to keep systems running better, faster and with fewer downtimes.
- Supports four caching providers: Guava, H2 (disk), Timed Memory, Redis (external cache service)
- Supports multi region caching
- Ability to add/define your own cache providers via plugin
- Configurable cache chains
- View cache region settings by name in dotCMS: System -> Maintenance and press the Refresh Stats button
- Note that configuration of cache chains and providers are available only in dotCMS Enterprise licensed editions. DotCMS Community editions use the default GuavaCache provider
dotCSMS Enterprise customers will find that, with dotCMS 3.3, a Redis Cache Provider is now included out of the box. Redis allows offloading cache to networked servers or a cluster of servers.
The benefits of this approach include:
- Redis caching servers can be scaled independently and at runtime in order to add or remove cache capacity and can improve performance
- External caching with Redis removes the dotCMS cache from the Java heap, which lowers the dotCMS memory requirement and may significantly speed up Java GC
- Cache “puts” and “removes” are network-wide
- There is no external syncing mechanisms that can fail
- dotCMS servers can be restarted with their caches fully loaded which is really cool, and speeds restarts which is most welcome in most situations.
- Supports master/slave environments – read from one, write to another
dotCMS 3.3 also brings about added stability to the platform's push publishing feature, thanks to a range of bug and use-case fixes.
The integrity checker has also been enhanced and the dotCMS team has added the ability to directly push languages and add languages to bundles.
So all in all, it's an update that's highly focused on improving the caching capbilities of dotCMS, which enterprise customers will be happy to hear about.