In this post, Sureel Bhurat, co-founder of Synapse LLC, a young Boston based company that builds SaaS web and mobile applications for consumer start-ups and enterprises, explains how PWS lets them innovate fast at a disruptively low cost. Synapse can build and operate applications for multiple customers with a very small team because they can use services from the Marketplace as well their own services with "user provided services". They rely on PWS to automatically load balance, dynamically scale and keep their apps running. Pivotal Web Services' simple and fine-grained pricing model allowed them to tune resources to just what they needed to serve their customers.
Last week we announced an important new partnership with Cloudbees to bring a native enterprise Jenkins service to Pivotal CF (PCF). This provided a first glimpse at the power of Pivotal Network, a service catalog for PCF, that allows any private PCF installation to import additional scalable platform services from Pivotal and a growing ecosystem of partners. In the wake of this milestone, Pivotal's James Watters takes this opportunity to articulate how this is yet another positive signal for the rapidly growing enterprise PaaS market, and how Cloud Foundry is serving up "fresh hope to IT people searching desperately for a private cloud strategy".
Today we’re announcing our partnership with CloudBees, the company behind Jenkins, to offer Pivotal customers access to the leading continuous integration and delivery software for enterprises. The CloudBees Enterprise Jenkins (CBJE) software will be delivered as an add-on service for Pivotal CF. Our customers will be able to download CBJE directly from Pivotal Network to install and configure Jenkins using Pivotal CF Operations Manager.
Award-winning Berkley astronomer, Onsi Fakhouri, has brought years of experience from working with Pivotal Labs and is currently leading the re-imagination and re-engineering of elastic runtime architectures on Cloud Foundry. This post covers Fakhouri’s background, Go (open source programming language) refactoring, Cloud Foundry Dojos, challenges of distributed systems, and more.
Today's guest post is from Tom Wilson, President and Lead Technologist for Jack Russell Software, where he is responsible for the Software Development Vision and part of the Software Architecture Team. In this post, Tom explains why his team decided to break out new business logic for their parent company's (CareKinesis, Inc) flagship Rails application into a set of microservices running on Pivotal Web Services. A period of rapid growth made them feel the pain point of a monolithic Rails codebase. By moving to a micro-services stack on Pivotal Web Services, Tom and his team were able to add developers to build new features in days vs weeks and take advantage of lightweight containers for performance. Pivotal Web Services $0.03/GB-Hr pricing and fine-grained container sizing allowed them to do more for a lot less.
This is the final post in our CI pipeline series. This time, we talk about how the pipeline stages loggregator-related changes to cf-release to other cf-release consumers (e.g. other teams) in a minimal-impact way. We also show how the pipeline uses git to rebase and merge the various repositories and branches that flow into it.
VMware kicked off VMworld, its annual week-long showcase in San Francisco, on Sunday with a number of significant product and partnership announcements. Aligned with Pivotal's goal to empower enterprises to develop and deliver modern applications on an open cloud platform, VMware is pushing for a new model of IT that supports hybrid cloud platforms and drives agile, mobile-first companies.
For well over 100 years, engineers have utilized wind tunnels to study the effects of aerodynamic forces on airplanes, buildings, automobiles, and other structures. This testing is conducted as part of a full suite of analyses intended to demonstrate, among other things, the ability of these structures to withstand various forms of stress.
Read more »
This post continues our CI pipeline series. In this edition, we talk about how we optimized the pipeline’s Cloud Foundry deployment step (into bosh-lite on AWS) from previously over one hour to about 20 minutes, resulting in shorter feedback cycles and therefore faster development.
A previous post explained CI pipelines for loggregator, and this post zooms in on why the Cloud Foundry engineering team uses Docker and how. A background is given and covers the problems faced without Docker and the benefits. Then, one of our top engineers, Johannes Petzold, explains how we use it and the issues we've seen.