
In our first two posts, we covered how to install Couchbase server

In our first two posts, we covered how to install Couchbase server

In our first two posts, we covered how to install Couchbase server and get a cluster up and running. In this post we are going to put that cluster of yours to use and show you how to configure it as an ORM secondary cache provider for your ColdFusion applications.
Please remember that the installation instructions are pretty much the same for Adobe ColdFusion and Railo CFML.
If your “cluster” is still just a single server, don’t worry. The size and configuration of a Couchbase cluster is seamlessly invisible to the connecting client. Meaning you can grow and scale your cluster without changing your setup/connection code.
At this point in time, there is no Couchbase-specific library for a Hibernate secondary cache, but luckily for us, Couchbase is compatible with the memcached protocol, so we can use the memcached library. The only drawback is that if you are connecting on the standard port of 11211 to Couchbase, the library will only be able to connect to the “default” bucket. To use a named bucket for your ORM Secondary cache, you will need to assign the Couchbase bucket you create to a unique port number with NO password when you create it in Couchbase Administrator application.

Today we are releasing an open source Couchbase provider for our CacheBox library whether you use it standalone or within a ColdBox application. We have been working with Couchbase NoSQL server and have been absolutely loving it. This provider will allow you to leverage Couchbase Server from any CFML application that leverages CacheBox for your caching needs. We have created two providers in our initial release: 1) For standalone Couchbase integration in any CFML application, 2) For ColdBox applications. The latter will allow you to hook up Couchbase to your ColdBox applications and even allow you to use it for event and view caching alongside data caching. We also take care of serializations and Java inter-operability for Adobe ColdFusion and Railo CFML as well. You can also leverage the Couchbase ColdBox provider for Flash RAM capabilities as well. As with anything we do here at Ortus, this provider is fully documented and professionally supported.

This is our second part of our Couchbase and CFML series that we started last week. In our first post, “Installation and Introduction to Couchbase” we talked about Couchbase Server, how to install it, and how it can help create a fast and scalable caching layer for your applications. Today we’re going to talk about setting up a Couchbase cluster and look at our first use for it: as a Hibernate secondary cache for ColdFusion ORM.

In our previous post we set up a very simple cluster of only one node. Let’s look at how Couchbase lets you expand your cluster horizontally as your needs increase. A cluster can have as many nodes as you want, seriously! All nodes in a cluster will be exact copies of each other in regards to their buckets and even their configuration. When you set up the first node, you will choose how much RAM you want for each node in that cluster to allocate itself. You can only add a new node to the cluster if it has enough RAM to allow for the node size specified in the cluster at setup. Therefore, the total amount of RAM in the entire cluster will be the node size times the number of nodes.

Caching is an important layer in today's applications that require high availability in clustered environments. Caching demands require fast performance, lots of storage, and the ability to scale horizontally so your cache infrastructure can grow with your needs. We take caching seriously which is why we've built tools like CacheBox which is not only a caching engine, but an aggregator and API for other caches. In-process caches which run on the JVM alongside your application and share the same heap space are convenient and easy to set up, but they have limitations. This is why we've spent time learning about other out-of-process caching strategies.
ContentBox Modular CMS v1.1.5 has now been released sporting over 40 closed issues and enhancements. Check out our engineering blog for an in-depth o...
We are announcing the release of ContentBox v1.5.5 which includes over 40 different issues closed and updated. You can either download the updates or use our auto-update panel to upgrade. The updates are now cumulative for the 1.5.X series only as well, so you can upgrade from any 1.2 version or higher.
You can read our very detailed release notes in our archive page. Below we will cover the major enhancements this release brings to the table a part from all the improvements and bugs that where squashed.
It has been a busy past few months here at Ortus Solutions and we have some cool new stuff to share with the world today. We have updates for all our major open source libraries this week. Some are minor releases and some are cool enhancement releases thanks to everybody's feedback and contributions. You can find much more about the releases in our ColdBox engineering blog or in our online documentation wiki:
For some reason our Google+ Page dissapeared, but we are back in business. So check it out and stay informed!
The Form Builder Module has been updated to support the latest version of ContentBox.
We have included lots of bug fixes and enhancements so you can create forms and easily deploy them to your pages or blog entries. Try it out and give us your feedback. Feel free to file bugs on the GitHub issues pages.
Forgebox Link: http://www.coldbox.org/forgebox/view/ContentBox-FormBuilder-Module