SpringSource Launches Enterprise Java Cloud

Rod Johnson

Today, we make another significant announcement. SpringSource is launching an enterprise Java cloud—SpringSource Cloud Foundry.

This initiative is a logical extension of our integrated Build/Run/Manage approach to unifying the application lifecycle, extending our vision of simplifying enterprise Java beyond the traditional data center. As cloud computing becomes more important, we want to ensure that Java developers can take full advantage of it. We believe that our leadership in Java development, coupled with our strength in the runtime and management phases, enables us to provide a compelling solution that will benefit the developer community.

What’s in the Box?

SpringSource Cloud Foundry provides an easy-to-use self-service approach, enabling developers to deploy their applications in minutes using a simple web interface. It offers automation of common deployment blueprints and intelligent, SLA-driven resource allocation with automatic scaling and automatic infrastructure repair.

Cloud Foundry builds on familiar Java technologies that SpringSource leads or makes a significant contribution to. The core runtime is our tc Server product, built on and wholly compatible with Apache Tomcat. We use the Apache HTTP web server for load balancing, and integrate Hyperic technologies for monitoring and management. We also provide a relational database (MySQL). Cloud Foundry allows the user to specify the desired application server and database configuration through a web interface, concealing the complexity of achieving the desired result, ensuring that the required steps reflect the intent rather than the details, and that configuration and deployment is repeatable. We expect that most users will be deploying Spring or Grails applications, although Cloud Foundry is not limited to Spring and Grails applications.

Thus, the programming and deployment model is wholly built on open source. The Cloud Foundry service also builds on open source: the Cloud Tools project, founded and led by Chris Richardson, which provides a set of tools for deploying, managing and testing enterprise Java applications in a cloud environment.

This initial release runs on Amazon EC2 cloud infrastructure. However, one of the key elements of Cloud Foundry is the abstraction it provides over such infrastructure. As with the Spring Framework, we will work to enhance developer choice. In the future, Cloud Foundry will give developers a consistent experience over both public (off-premise) and private (on-premise) clouds, empowering organizations to make the most appropriate choices. Our conversations with customers make it clear that such a unified approach is a key need that is presently unmet in the industry. A key part of addressing this need will be Cloud Foundry also running on VMware vSphere infrastructure, which provides uniquely advanced on-premise cloud infrastructure.

Future Directions

Cloud Foundry is valuable to developers today, but what’s even better is that we’re only getting started!

The longer-term vision goes much farther. We’ll be enhancing the management and other features you can already see. We’ll enhance runtime visibility into Spring and Grails applications, as we’re doing with our tc Server product itself. We're looking to offer modular deployment with SpringSource dm Server. Both Adrian and I have blogged about the possibilities of a fully integrated stack in which the application framework and application server work closely with the cloud infrastructure to deliver the best possible experience. With Cloud Foundry, we are opening up that path to developers.

We’re working on integration with Cloud Foundry in our freely available SpringSource Tool Suite (STS), making it even easier for Spring developers to deploy applications to the cloud. We’re also planning Grails integration, making it as easy to deploy Grails applications to the cloud as it is to create them in the first place.

Get Started Today!

Today’s launch is a beta service. As our tradition with Spring projects, we’ll be working to get developer feedback as we move to a GA release.

Simply go to CloudFoundry.com, and you will be able to deploy an application in minutes. We want to hear from you! For example, we are open to offering persistence choices besides MySQL, and would love to get your input.

Welcoming Chris Richardson

Some readers will recognize the Cloud Foundry name. Having identified cloud as an important strategic direction, we chose to acquire Cloud Foundry Inc. due to the innovation and leadership it had brought in the space. Since then we have increased investment in Cloud Foundry technology.

Many of you will know Chris Richardson, the founder of Cloud Foundry, as a long-time member of the Spring community and an enterprise Java thought leader. I’m happy to welcome Chris and his team to SpringSource. The combination of their work and SpringSource’s strength in frameworks, servers and management is exciting!

Similar Posts

Share this Post
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • DZone
  • LinkedIn
  • Slashdot
  • Technorati
  • TwitThis
 

20 responses


  1. That's great news! I've been waiting for such a service to come out of beta for months, but waiting a while longer is sure worth it if it gets better support for Spring applications.

    Here are a few thoughts and suggestions:

    Are there any plans to offer SLA? The lack of SLA is the only reason my company can't use such services, and I imagine it's true for other companies too.

    About the MySQL database: I would like to have the option to use the Maria or Falcon engines since they support both transactions and full text search.

    Would it be possible to store JAR files in the Tomcat's lib directory? If I needed to upload my application with all it's dependencies every time, it would not be practical due to its size.

    I suggest that you include tools for managing development in a team: source control, CI server, maven repository and issue tracking system. I think such a package would really give everything a developer needs in one box. That way the developers won't have to upload the WAR, but let the build server build it from the source. Maybe you could partner with XP-Dev?

    Thanks and good luck!


  2. How do you plan to support MySQL on cloud instances, given that cloud instances are meant to be stateless and ephemeral by nature?


  3. Awesome! Has any experimentation been done with deploying to a Eucalyptus-based private cloud environment? Figuring since Eucalyptus is a clone of the EC2 API it should – but just curious if you guys have done it. ;)


  4. Interesting publication


  5. Are you guys planning support for OSGi deployments via dmServer in the near future?

    Thanks!


  6. Are SignUp applications being processed by hand? I submitted one hours ago and still no email, and just in case that was dropped I just submitted another!


  7. @Stacy

    Good point. We do expect to support dm Server in future. I've amended the blog to include that point.

    Rgds
    Rod


  8. Very Cool!

    I second the response that mentions managing team development (source code control, build server, etc.). I think either providing this or partnering with someone to provide this integration would give a development project everything it needs.


  9. @Jacob

    Yes, I think they are being processed by hand. I also signed up to try this out yesterday but still no response :-) I am very eager to try it out as I am waiting a long time for something like this. The Google App Engine was very promising but you are still limited by the libraries and API's you can use.

    Does anyone have an idea what will happen after the beta? Do we have to pay in order to continue using the Cloud Foundry or will there also be a limited free subscription?

    Keep up the good work guys!


  10. @Manik
    Elastic Block Store would be one way to support this:
    http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1663


  11. @Donnchadh EBS doesn't guarantee durability (and backups, etc). Even AWS' docs don't recommend using EBS unless you're backing up periodic snapshots to S3. Now this has 2 problems: generating snapshots with any degree of safety inevitably involves locking the partition from writes for a period of time. Performance hit. And any periodic snapshot mode of backup will have windows where data loss may occur. So what's the moral of the story? Don't use an RDBMS on the cloud for anything important/critical?


  12. The service is very promising. I have been playing around with it a little bit. It is a nice clean interface that does make it easy to launch apps quickly into the cloud. Look forward to seeing it grow.

    @Davy
    The faq at https://www.cloudfoundry.com/faq.html has a little bit about this. It says "pricing will be announced after an extended beta period and will follow standard cloud service pricing models". That is a very vague statement, so I hope there will be some more detail soon.


  13. @Rod

    Would be very interesting if we could get support for elastic PARs. (In addition to straight virtualization of dm Server itself)

    Cheers,
    Stace
    Adobe


  14. There is a spelling mistake on the home page s/aplications/applications


  15. @Manik
    I suppose it depends what you're comfortable with, but two of the stated benefits of EBS are:
    * Persistence beyond the lifetime of instances
    * High availability and reliability
    See:
    http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?concepts-failure-resilient-apps.html#concepts-ebs
    Of course there's nothing preventing you setting up MySQL replication etc. just as you would with any other storage system that may fail (e.g. hard drives on your own server).

    It would be interesting to see a rigorous comparison of the performance and reliability of EC2 EBS vs. a physical machine local RAID system for example.


  16. @Gabriel, I understand your desire for an SLA. Currently, we are focused on going through an extended beta period after which we will introduce pricing, support, and associated SLAs. We are also interested in expanding the feature set to include additional databases, text search etc. We are also looking at ways to speed up web application uploads.

    @Manik, we provide the option of using Elastic Block Store as the database along with MySQL Master-Slave replication and periodic EBS snaphots. Also, on http://aws.amazon.com/ebs/ : "Amazon EBS volumes are designed to be highly available and reliable."

    @Jacob/@Donnchadh – the team of gerbils processing signup applications was overwhelmed by the volume. Apparently, they are all caught up now. Please email us if you have not received your invitation.


  17. Rod,

    This is a smart move and I am sure you are ready to disrupt the enterprise java space again. I am sure this will go long way and may change the way enterprise Java happens.

    I am looking forward to see support for DM Server and STS to foundry.

    Regards
    -Niranjan.


  18. awesome….


  19. I loved this post. Fabulous

    Resveratrol


  20. SpringSource helps enterprise IT deploy lean and powerful application infrastructure runtimes to accelerate time to value and cut cost and complexity.it is the best Eclipse-based developer tools for building Spring applications Transforms application infrastructure metrics into reports and systems intelligence that business users can use to analyze, evaluate, plan and make strategic decisions ……………Dual Action Cleanse

14 trackbacks

Leave a Reply