CohesiveFT embarks today on an exciting extension to our existing business - the launch of our "Elastic Server On-Demand" service. Our new service which launches in Private Beta today, is the beginning of the realization of our vision of "making middleware accessible, manageable, and affordable".
As our company has grown we have noticed a key customer need - customers now want multi-sourced, loosely-coupled, vertically-aware middleware solutions. No longer is a "one size fits all" stack of computing capabilities acceptable. As a result, we are introducing our on-demand service with its ability to create "Elastic Servers™".
Elastic Servers are customer-configured, multi-sourced middleware stacks built dynamically in virtualization-ready formats and made available for download. Dynamic deployment capabilities to services like Amazon EC2 are coming quite soon.
Why do we call them "Elastic Servers"? Basically we are out to let customers build the stack they want - with no more - no less in it - and deployed in new dynamic forms like virtualization containers. Also, we are creating the ability for the server components to flexibly link to each other, as well as other environmental services. We call these linkages "rubberbands". Over the next weeks as our beta rolls out, we will publish the formats needed to make components interact with services like our control panel or firewall.
We know we won't have a monopoly on interesting linkages, so end-user tools for creating components and rubberbands are high on our list. If you are already on the Private Beta you have seen the home directory of ESOD (elastic server on-demand) and its "microsites". These component-themed sites are just the beginning. End-user microsite tools are coming soon. In the mean time lets us know what components you would like made available, and what types of microsites are of interest to you.
What can these initial servers do? Right now we are beta testing the packaging, VM output formats, and user experience for ESOD. The middleware servers you create could have component conflicts, since for now we are building what you ask for - without checking a rulebase of compatibility information. When you download and launch, your packages are there, but we haven't necessarily started their processes. To describe these first dynamically created servers as "Inert" middleware probably doesn't give us enough credit, "production ready" would give us too much. As our "rubberbands" come on line, and we get more of your feedback of what is needed, we will distance ourselves from the former description and move decisively towards the latter.
Take a look at the Elastic Server On-Demand roadmap at http://www.cohesiveft.com/esroadmap/ and please take the feature poll to help us understand your needs.
This is "your middleware". Let us know what you want to do with it and how we can help.
