Why use RAC for an OpenFire database? We use RAC to provide high availability and database session load balancing in our environment. If the application can be built out for high availability using clustered application servers, why not complete the configuration by making your database highly available as well?
In implementations where the availability of a suite of applications is considered critical to the operation of your business, RAC fills this gap very nicely and the database is no longer a single point of failure for the application suite. If the application layer can further leverage the additional features of RAC, such as FCF (Fast Connection Failover) or TAF (Transparent Application Failover), even better as the end user experience will not be impacted as much, if at all, in the event of the failure of a database server.
The other benefit of RAC is that we have the ability to make the most of our hardware resources - we don’t have servers sitting idle as we do in an active/passive cluster configuration. We can distribute the incoming database sessions across the RAC cluster transparently to the application.
I agree that since OpenFire is using Oracle’s JDBC driver that it is possible to use RAC for OpenFire’s database. There’s been at least one implementation of it thus far detailed on this board (referenced in my earlier post). At this point, I would be interested in hearing others’ experience, lessons learned, etc… with this particular configuration.
Just my $.02.