CacioWeb – The Java Deployment Solution of the future
November 1, 2011 9 Comments
In this post, I would like to give an overview of what CacioWeb is, what we plan to do with it in the near future, and how you can participate.
What is it now?
What are we planning for the future?
There are several features that we plan to implement and offer as a commercial product through LadyBug:
- Most importantly, we are implementing a web frontend for easy deployment and configuration of Java Swing applications to the CacioWeb nodes. This could be accomplished simply by uploading an executable JAR file containing the application to the server. This management service should also offer a way for automated deployments using common build tools like Ant or Maven.
- Another great feature we have in mind is a clustering service. It would be possible to host many CacioWeb nodes on each server, or even host several servers with several nodes each. The clustering service would distribute incoming sessions according to configurable rules. This will have significant advantages 1. load can be balanced across several nodes. 2. if one nodes goes down, sessions would be directed to other available nodes, thus increasing failover. 3. if you configure one session per node, you achieve maximum stability, if one user crashes one JVM, it will not take down other users. 4. If necessary, new nodes can easily be added by registering in the node manager. In short, this will greatly extend stability and scalability of CacioWeb.
- We are working to provide client side printing support using the standard Java printing APIs.
- Last but not least, the whole CacioWeb application will ship as a standard .ear file, ready to be deployed on any J2EE compatible server.
How do we get there?
The above features are currently not yet implemented. We are currently working on implementing the features, but currently don’t have the funding to do so in a timely manner. In LadyBug, we decided to not go after venture capital. Instead, we would like to try out some guerilla tactics to get going. The idea is this: If you (as a company or invididual) think a solution like outlined above would be a great thing to have, and would be interested in purchasing a license for, please contact us and tell us what would be your intended usage scenario. We would basically offer to buy a share of the development of such a product. Based on the feedback, i.e. number of interested parties, we would find out a price for such a share, and if we end up at a reasonable price and get enough support, we would start work on it. In return for the support, we would of course provide a license for the product once it’s done, within a timeframe of maximum 6 months, plus the chance to directly participate in the actual development, e.g. you could provide us the application that you intend to run for testing, etc. Please let us know what you think.