Premier developer event opens speaker proposals
San Francisco, December 15, 2016 — Cloud Foundry Foundation today announced its call for papers has opened for Summit Silicon Valley 2017, which will take place June 13-15 in Santa Clara, CA. Early Bird Registration and a speaking call for papers (CFP) are now open for the event. Sponsorship opportunities are available now for members only. Non-members will be given the opportunity to sponsor starting January 3, 2017.
Cloud Foundry Summit Silicon Valley is the premier event for enterprise application developers. The event will focus on microservices and continuous delivery in all frameworks.
Premier developer event opens speaker proposals
Cloud Controller is the primary API through which third parties interact with Runtime; it encapsulates the myriad internal services that take a user from ‘cf push’ to a running application. Both the Pivotal Developer Console (the web application that ships with Pivotal CF and backs console.run.pivotal.io) and the CloudFoundry CLI interact directly with the Cloud Controller API. The two applications were originally written in Ruby and shared a common Ruby code base for talking to Cloud Controller called CFoundry.
CFoundry provides a friendly interface to the Cloud Controller API.
The Cloud Foundry team has released new features to improve management of Ruby gems in apps running on CloudFoundry.com. These features include support for using Git URLs in Gemfiles, handling of the BUNDLE_WITHOUT environment variable, and platform specification to control the gem installation process. With these improvements, it is now easier than ever to get your existing Ruby projects up and running on CloudFoundry.com.
In 2003, RubyGems was launched as Ruby’s package manager. Six years later, Rubyists began using Bundler–a means for managing and installing gem dependencies in the context of an application.
Also in this series:
Cloud Foundry Improves Support For Background Processing
Running Workers on Cloud Foundry with Spring
Running Standalone Web Applications on Cloud Foundry
We introduced Cloud Foundry’s new “standalone” applications feature in the first post in this four-part series. In this second installment, we will look at the most common use of a standalone application–the worker process. Workers can be used for all kinds of asynchronous background jobs, such as updating search indexes, emailing all users with a password reset approaching, performing a database backup to persistent storage, or uploading new customer data from external storage.
Cloud Foundry has significantly enhanced support for worker applications that perform background processing by allowing applications to run on CloudFoundry.com without the application container. Cloud Foundry applications are no longer limited to Web applications that respond to HTTP requests. Instead, they can be run as executable or “standalone” applications. A standalone application is one that does not require a provided framework or container.
Many developers create distributed applications that have workers to perform specific functions and communicate via a data or messaging system, such as those developed with Spring Batch, Spring Integration, Resque, or Delayed Job.
We have recently made many improvements to Cloud Foundry to increase Ruby developer productivity and expand support for Ruby application frameworks. Cloud Foundry was built to run multiple languages and frameworks, and we have had support for Ruby from day one.
It is well known that VMware developers are the stewards of the incredibly popular Java Spring framework. Therefore, Cloud Foundry’s support for running Java applications in a platform as a service environment has always been excellent. However, many CloudFoundry.com users may not realize that most of Cloud Foundry’s system components are built using the Ruby programming language, and providing great support for Ruby applications is also very important to us.
The services offered in Cloud Foundry are necessary for writing any serious application. Our aim is to make it easy to configure and consume these services. In addition to the auto-reconfiguration described in the Using Cloud Foundry Services with Ruby: Part 1 – Auto-reconfiguration blog post we also have support for manual service property lookup as well as library calls to obtain a pre-configured connection object.
Library call to obtain client object
For each supported service type there are corresponding library calls to obtain a pre-configured client object. This makes it easy to use in your code since you don’t have to lookup connection properties, instead you can rely on the library to do the work for you.
Right from the launch, Cloud Foundry supported auto-reconfiguration of Spring and Rails apps that use a relational database service. This allowed deploying such an app without changing a single line of code. Recently, we extended this support for Spring apps to cover all services (Redis, Mongo, and Rabbit). We are now extending this support for all services for Rails and making this available for Sinatra apps as well. In this blog, we will explore how auto-reconfiguration works with Rails and Sinatra applications.
Auto-reconfiguration in action
To demonstrate auto-reconfiguration, we will grab an application from github and deploy it to Cloud Foundry without modification. Let’s use lamernews, a Sinatra app that uses Redis.
Cloud Foundry™ is the industry’s first open platform as a service. Providing a choice of developer frameworks, application services and deployment clouds, Cloud Foundry simplifies application development and makes it faster and easier to build, test, deploy and scale applications. Cloud Foundry already supports multiple application services including MySQL, MongoDB and Redis. And we are working to add more.
Today, we are pleased to announce an important milestone: the RabbitMQ messaging service, available today as a free public beta. You can get started right away: on CloudFoundry.com, you will find sample applications and guides. If you create a cool application, please let us know and we’ll link to it. And if you get stuck, tell us what we need to get right.
We spent this week at RailsConf Baltimore, Maryland. It was great to see hundreds of Ruby and Rails developers excited about the open PaaS vision of Cloud Foundry. We got tons of questions and great feedback – thank you all!
On Monday we conducted a hands on tutorial where attendees build their own “who follows who” twitter Ruby application on Cloud Foundry. Above you can watch a step-by-step screen cast of the tutorial and try it yourselves.
On Tuesday, we had a session on the architecture from the developer perspective of Cloud Foundry, focusing on the Ruby and Rails benefits. You can watch the presentation here.
This screencast is technical and focused on Developers, showing them how to use Cloud Foundry, the first Open Platform as a Service by VMware.