Blog

Luis Majano

November 06, 2019

Spread the word


Share your thoughts

Connect, Code and Scale!

v1.4.0 released!

 

We are very excited to bring you another release for our Redis Lucee Extension. This is a minor release and it sports quite a few updates, improvements and Lucee compatiblity updates.

Overview

The Redis Lucee Extension allows you to natively connect to a Redis Server cluster and leverage it for distributed caching, session/client storage and distribution, cluster RAM file systems, and much more. It can allow your Lucee servers to scale and extend easily by leveraging Redis Server as the platform of choice for session/cluster managements, caching and virtual file-systems.

If you have ever asked yourself these questions, then our Lucee Extension can help you:

  • Want to use round-robin balancing instead of sticky sessions?
  • How do you deal with session/client information when you have more than 1 server in your cluster?
  • How can I scale my Lucee servers when I am running out of RAM?
  • Do you want your users to still be logged in even if a server in my cluster dies or is restarted?
  • Do you want to have a cluster-wide file system?
  • Are you using a container based deployment and need off heap peristence?
  • Do you want to be able to cache data in a distributed and elastic fashion?

 

We have been working with Redis Server for many years and it has been a true pleasure to not only build scalable farms with it, but also it is incredibly responsive when it comes down to key-value storage and caching transactions.


v1.4.0 Release Notes

Bugs

  • [LRE-14] - Compat with Lucee 5.29+ due to a Lucee issue introduced that skips default values from the driver forms.

New Features

  • [LRE-13] - Add a log4j bridge to all sdk and local logs can be added

Improvements

  • [LRE-12] - Throw runtime exceptions on connection issues so they are highly visible
  • [LRE-15] - Added all members of the RedisConnection class to be public/static so they can be inspected and reused
  • [LRE-16] - Added a getConnectionKeys() in the RedisConnection class to see which caches are configured and how they are configured
  • [LRE-17] - Added RuntTimeExceptions and IOExceptions whenever a Redis connection cannot be made to improve error management
  • [LRE-18] - Added more context when exceptions happen to the error messages to pinpoint failures
  • [LRE-19] - Converted all connection pool access to try's with resources for auto-closing and better code visibility
  • [LRE-20] - Coverted all valueList() and entryLIst() methods to leverage parallel streams for performance

 

Purchase Extension


Resources

Please visit our Extension page for all the necessary resources.

Add Your Comment

Recent Entries

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Luis Majano
Luis Majano
March 13, 2026
Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

  • internal banking workflows
  • reporting systems
  • client portals
  • data integration platforms
  • compliance and risk management tools

In many cases, thes...

Cristobal Escobar
Cristobal Escobar
March 13, 2026
Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Cristobal Escobar
Cristobal Escobar
March 12, 2026