Cloud Platform Webinar Series

It’s a Mobile First World: Faster Mobile Apps with Pivotal and VMware


Let’s face it – delivering modern, mobile applications for your customers and employees isn’t a matter of when, but a matter of how fast. How can IT build apps faster? How do you scale if the app is a huge success? How do you update if it’s a dud?

Legacy platforms may be fine for systems of record, but they aren’t built for mobile. Join Pivotal and VMware to find out how enterprise Platform as a Service (PaaS) and an enterprise hybrid cloud give you the power and agility to deliver mobile apps faster.

Learn how:

  • PaaS is key to building modern, responsive mobile apps
  • Enterprise PaaS with built-in mobile services keeps your data secure while providing agile development and operations
  • Hybrid cloud solutions are critical for flexibility, redundancy and seamlessly scaling out high-performance apps

Attend this Webinar and learn how Pivotal and VMware together can help any enterprise become a mobile-first organization.


Jay Marshall
Principal Cloud Development Strategist, VMware

Jay Marshall is a Principal Cloud Development Strategist at VMware specializing in next generation application architecture on VMware's vCloud Air cloud platform. He has spent almost twenty years working in enterprise application development, a large portion of that time in enterprise Java and most recently mobile web. His passion for technology has helped launch multiple startups, legacy modernization projects and bleeding edge application development and delivery initiatives. Jay has worked with some of VMware's largest customers to help shape their vision and start them down this path.

Rosie Pongracz
Senior Director Product Marketing, Pivotal

Rosie leads the Pivotal Cloud Foundry and PaaS Product Marketing team at Pivotal. She has more than 20 years of experience bringing enterprise technology to market, including software development tools and platforms, virtualization, SaaS, security, wireless, telecom and medical instrumentation. She previously held leadership roles in marketing, product management and product marketing for companies including Salesforce, VMware and AOL.


Rosie: Good morning and thank you for joining us. We're going to get started now. My name is Rosie Pongracz. I am from Pivotal and I'm here with my cohort Jay Marshall from VMware. Say hi, Jay.

Jay: Hey everyone, happy to be here.

Rosie: We're happy that you could join us. Thank you so much. Together, Jay and I have an exciting story to tell. We're actually continuing where we left off with our prior webcast if any of you made that one. If not that's okay. In this chapter, we're going to focus on how modern open cloud platform is critical for developing and delivering mobile apps faster and how this new cloud platform accelerates application development, deployment, delivery of high performing highly engaging mobile apps so let's jump right in.

You may know PaaS, as the public [PaaS 00:00:52] solutions that are available on the market and have seen some success in the past few years. They've been successful for mobile in many ways because they provide the type of platform that can deliver these next generation applications at scale and as we'll see scale is really important for mobile. There are also separate mobile backend as a service solutions available as well as you might of heard of. We'll take a look today at what platform as a service offers for mobile along with how the demands of enterprises are currently only marginally being met with the public solutions. That when you bring together enterprise platform as a service with integrated mobile features that you can run on your own cloud or your hybrid cloud of choice, you get an enterprise-grade solution for mobile that can run in your private cloud and also scale seamlessly onto an enterprise-grade hybrid cloud solution.

I think we all know intuitively about the proliferation of apps simply by looking at our own phones but if you count the number of apps from your company and from large enterprises you'll actually find a dearth of enterprise apps typically. If you take out your phone now you'll probably see that that number is ten to one of the more consumer type than enterprise apps but this is changing rapidly. Every CIO and IT operations team leaders are scrambling to keep up with the demands from their businesses. No question that mobile is transforming how enterprises engage with their customers and employees so the conversation is actually moving from mobile first to mobile only. In fact [Gartner 00:02:23] says by 2017, 90% of all apps will be mobile and that's up from 20% in the current time frame and right around the corner in 2015, [Gartner 00:02:33] predicts that mobile application projects targeting smartphones and tablets will outnumber PCs by four to one so the shift is well underway.

What's going on with enterprise mobile and app delivery? Well, it's not an act now for a company to make their website readable on a mobile device. Their employees want to get their work done. They want to increase their productivity. Their customers want to have a personalized experience and access their information, their accounts, and their products. Consumer apps have clearly driven the expectations and set the bar to provide the same type of experience for enterprise apps.

The UI for mobile can't simply be a website or desktop [port 00:03:12]. Mobile UIs need to be smartly designed for a subset of capabilities in look, simplicity, and aesthetics and even more important they have to be responsive and perform instantly. For example, if you're sending notifications those need to be instantaneous. If you're updating account info, people expect that to be immediate. The experience needs to be richer and different from the web and desktop experience so that your customers come back and they choose to interact with your brand over and over again. This all points to the fact that consumer apps, be it for social or games or entertainment, have really set the level for enterprise apps in terms of performance, design, and engagement so what we say is enterprise apps they must deliver consumer-like experiences.

Even as we often talk about software use in the [world 00:04:01], it's no longer true that every business is a software business. Every business is actually a mobile software business. You think back to the 90's just as client server computing brought new levels of productivity internally to companies, now software is key for creating those systems of engagements with customers to disrupt industries and to change business models. The customers want to engage with companies where and when they find it convenient which is likely on their mobile devices so mobile software and apps are your core company differentiator. This is rapidly changing how companies are viewing software development. It's not just a tedious back office chore that is outsourced. Rather companies are turning to create their own innovation labs and insourcing their software development.

This software development is not trivial customizing of off the shelf software. Their same software is core to making their business model and products differentiated. Software and mobile matter more than ever to insure that companies can stay competitive and customize unique features and offers for their businesses. For example, even with our own company. A major Wall Street bank is renting out office space for their innovation lab in our building in Palo Alto. Recently you can read about it almost everyday about other companies, non-IT companies, are cohabitating with technology companies or at least setting up offices nearby so this is definitely a trend we see happening much faster.

Let's look at mobile specifically. It brings new opportunities, requirements, and of course a lot of challenges that companies are having to face and it's on a variety of different levels. First mobile apps provide a new and extremely effective engagement model and as I was saying before, if you just want to port your legacy web applications to a small form factor you've really missed the boat on the opportunity there. Multifunction legacy applications often need to be broken down into several task or audience-oriented applications and that often requires a number of mobile apps. Mobile is all about now and real-time so these engagement features things like push notification and other smartphone features are expected and they need to be incorporated really thoughtfully from the get-go into the mobile design.

Next mobile apps also provide new experiences and this is important with new data they're incorporating such as location and data from a host of sensors. In fact, there's 17 different sensors on a smartphone as compared to 4 or 5 on a laptop so things like location-based is often a feature that can help provide new experiences for your customer. Also the data from those sensors they provide insights into the application developer on how to tune and design your app based on user behavior and you can find out valuable and new things. You really got to incorporate how to use that data and how to ingest all that data from those sensors from the get-go and it requires a different platform.

Then lastly if you look at it operationally successful mobile apps also need to support greater scale and uptime than traditional web apps. With over 1.5 billion devices in the world, mobile devices surpass desktops and laptops already. In contrast, a prior generation of these client server apps were really designed to support tens of thousands of employees so that's one area or one issue about the scale. Then the operating system evolution, the mobile operating system evolution, of updates are more frequent. Client server are generally about a three to five year cycle and now if you look at the mobile OSes and the three major ones and multiple ones that you're trying to support, those are at least on a yearly basis. Users, as soon a new OS comes out, expect their apps to be updated and again those consumer apps are setting the bar.

If you look at these all together the new engagement model, context awareness, sensor variety, device volume, and the OS update frequency you can really start to see why best of breed apps are updated well 10 to 24 times per year. This same old way of developing and releasing with current platforms and monolithic client server applications for these fast iterative releases, well it's just not going to work that well. You're trying to solve for each of these challenges separately and that could create some complexity too but guess what no surprise. There's a better way. A more holistic way to meet these requirements of the mobile app world.

Let's look at enterprise PaaS and it's pretty much the answer, the solution, and critical for mobile for these third generation mobile apps that are being built and are so important for your company. This modern app architecture has to support these faster almost constant iterations that are expected by users and you want to be able to add new features to remain competitive as well. Plus if you look at who's developing these. They want state of the art tools including modern frameworks, languages, and databases, and they want a modern cloud stack. These applications need to be architected from the beginning in this cloud architecture and to be able to ingest all the big data we talked about from those sensors and then how to be able to feedback and inform those app updates.

Next given this new engagement model mobile apps have exponentially increased workloads and those workloads are highly dynamic. For example, some of our customer's banks see that their apps on payday are being checked up to 30 times per day. Then you think of apps, even apps for sports or entertainment, during a small period of time get millions of users during short periods who want immediate notifications. PaaS provides this concept of being [intimately 00:09:57] scalable for these dynamic workloads and then users expect no downtime. Again it's driven by the social and consumer apps like Facebook, Google, Instagram who've set those expectations. These apps don't get taken down for upgrades or maintenance and enterprise PaaS is a platform built for these apps with this ethos of no downtime.

In fact, enterprise PaaS allows things what we call blue-green deployments so you can release new apps into the mix so new features can be released to a small group and you can do things like A/B testing which leads to the last point on this slide. Because mobile devices and OSes are changing so fast you really need a platform that supports this ability to update. It's about adding new features. It's about staying relevant and it's about outmaneuvering your competition and being able to do this is truly becoming table stakes for any company.

Now let's talk about how Pivotal Cloud Foundry and Pivotal Cloud Foundry Mobile Services are built into the Cloud Foundry platform. Pivotal builds the mobile services, a consumer-grade mobile backend services built specifically for the enterprise. Let's revisit quickly what we mean by consumer-grade built into an enterprise platform. Rich user experience, simple clean UIs, modern technology stack, and very large scale and high throughput. By built for the enterprise what we mean is it's highly secure, enterprise customers retain control and ownership of their enterprise data, and this can be deployed in their private cloud on premises behind the firewall.

The set of mobile services available now on Pivotal Cloud Foundry on vCloud Air are push notifications, API gateway, and data sync. This set of services form a middle layer between the mobile devices and the enterprise backend all deployed and running on Pivotal Cloud Foundry the enterprise PaaS. This allows services to leverage all the operational benefits that [PCF 00:12:00] provides such as fast app deployment, four levels of application high availability, monitoring, auto scaling, and in-place upgrades without taking services down, logging, routing of traffic. All of the Pivotal Cloud Foundry operational goodness and that's built into the mobile services on your enterprise platform.

Let's explore a bit on each of these Pivotal Cloud Foundry mobile services. First, let's talk about push. Now that's critical for engaging consumers. Think of the notifications you get for special promotions or when your favorite team scores or social network posts. In the enterprise world though push isn't being leveraged as much for both employees or customers. One of the main reasons for that is that existing push providers are public third party solutions and these are limited for several reasons. In fact, we have a customer story coming up that ran into just this dilemma.

First of all enterprises are still a bit wary of sending their data to third parties and it's harder to integrate deeply into your systems of record which maybe part of the application you're trying to notify your customers with. Multi-tenant solutions are often impacted by what we call noisy neighbors and that means that if another application has a sudden spike in traffic, neighboring apps are actually going to be affected and see their [SLAs 00:13:24] degraded. We solve these issues by combining this as a service on Pivotal Cloud Foundry on your private cloud, on your hybrid cloud, your own dedicated solution. Enterprises retain full control of their data and integrate with systems of record easier and your solution is fully dedicated on your cloud with scaling available. Also on an enterprise solution like vCloud Air and we'll talk about that in a moment.

Next onto data sync. First, virtually all apps need to access your backend application and virtually all app store mobile specific data so things like mobile user profiles, session state data. That can be used to enable workflows across different devices. For example, I may start a process on my phone and then move over to complete it on my iPad so as a application I need to store that mobile specific data somewhere. Existing backends often can't accommodate this and developers are faced with the challenge of hey do I modify the backend for mobile specific data which can be really painful often involving different teams. What we're doing is providing a simple external data repository to store the mobile specific data and then sync it across the different devices.

Now since this is deployed in your private or hybrid cloud it meets your enterprise data security requirement so you actually don't lose control of that data. We're providing mobile optimized APIs for accessing multiple types of storage starting with Redis key value stores. Some of you maybe familiar with Redis and adding others over time so this is really simple. Developers love that kind of key value store functionality. Simple for developers. Flexible, highly scalable, and then secure as well.

Finally let's talk about the API gateway. The issue here is that legacy APIs are not optimized for mobile devices. They're not optimized to send only relevant content for the device form factors be it screen size or capabilities et cetera. You certainly don't want to send the same content to a mobile device that you are sending to a desktop. These are things like high resolution images and a lot of unnecessary data that the server is sending down that can really drag down performance of your mobile device. As we talked about performance is really paramount for the user experience and what customers expect. The other thing is that mobile apps usually require several API calls to the backend to display even a simple set of content on the app so this will drag down performance.

As we touched on earlier, performance is critical. Users are much more sensitive to the latency on mobile than they are on the desktop and you also have the factor that you can't assume constant connectivity. One moment the user may have a strong signal and the next it totally drops out so it's really important to send only the relevant data that you need down to the mobile device. The mobile API gateway acts as a middle layer between the legacy API backend and the mobile devices. You can have the business logic and transformations in the API gateway to take those ugly backend APIs and turn them into really clean mobile optimized mobile friendly restful APIs that's easy for the devices to interact with. The net result is that a much richer experience, a much snappier UI, and of course a better customer experience overall.

Let's take a look at this in practice and we'll take a look at a customer who is a major sports brand who's actually using Pivotal Cloud Foundry Mobile Services on vCloud Air that Jay is going to talk to us about. They were using a hosted push notification service, a mobile backend as a service, and there's several reasons why that mobile backend as a service fell short for them.

First they were having reliability issues. Some notifications were getting dropped or delayed during an event and this is a sports event so you can imagine things happen every few minutes if not seconds. Actually, this had to do with that noisy neighbor problem that I mentioned before because there were other apps sharing the service and this company had no operational visibility into what was going on so even though it was hosted on a public PaaS solution they couldn't see logs. They couldn't see what was happening to those message. They couldn't troubleshoot and those notifications were key to the user experience and the expectations of their app so in the end their IT team wanted much more control and visibility.

With Pivotal Cloud Foundry running their own Pivotal Cloud Foundry instance on vCloud Air they were able to scale very quickly and we're talking huge scale. Up to 20 million notifications per minute. Additionally and this is pretty typical for these events and for these apps, we had to do an upgrade to the push notification service and we had to do this while in production. While with an enterprise PaaS like [PCF 00:18:18] the platform is actually designed to be able to do that. I mentioned something earlier called blue-green deploys which means we could bring up new app instances while the old ones were still running and run them simultaneously and gradually switch over without any down time. We're also able to run that roll back if there were any problems. This type of operational visibility, that flexibility and power, is only possible when you have an enterprise PaaS like Pivotal Cloud Foundry and it's running on infrastructure that you control.

Beyond push notifications this app also was doing live video sharing so that's another performance potential problem. We need to look at what the metrics are, the performance there, and we're interested in taking metrics data for the video viewing that shows what the users are watching, how long they watched, and all of their viewing behavior. We're getting all of that heavy amount of video data ingested in the platform and storing it.

This whole story when you put it together with the mobile, the mobile push notifications, performance, the ability to upgrade while live, it's a great snapshot of the power of what an enterprise PaaS can do and the value that it brings. The value of mobile services running on enterprise PaaS and operational visibility that you get for your app and the ability to get the data, ingest the data, and analyze it to understand the viewing behavior. When you pull this all together you get a pretty compelling story for why this company was so happy and getting the app performance, the customer experience, that they wanted with Pivotal Cloud Foundry Mobile Services on vCloud Air.

I talked a lot about vCloud Air and so for this part I'm going to hand it over to Jay who's going to tell you a little bit more about some of those benefits and what you can get when you're running it on premise as well as on vCloud Air. Take it away Jay.

Jay: Thanks Rosie. I just want to point out to anyone that has been in the mobile development space for a number of years hopefully you can appreciate these services being provided by the platform itself and particularly in the same platform where you're building the rest of your enterprise apps with Pivotal Cloud Foundry. The evolution of mobile development in the past three years or four years has been pretty astounding. It wasn't that long ago that our primary focus was just the app itself or as Rosie was pointing out earlier just maybe the UI or translating our apps into a mobile format or maybe exposing access to existing data to our mobile devices. Even in my own experience back in 2010, I thought I was a hero just for getting Apache Jersey running and creating a bunch of rest URLs that my iPhone could get data out of so that doesn't really cut it anymore.

Now it's about competitive differentiation and new features that people are looking for that are very mobile specific so this is where the additional services, geolocation, Rosie mentioned about push messaging. These things are critical now so with all of those platform features that she showed you a minute ago it still has to run somewhere. With what you're looking at on the screen here the enterprise hybrid cloud is what becomes the perfect landing spot for these kinds of services. The screen that you see here, with on the left you have a cloud and on the right you have a cloud. On the left, this pretty much represents your private data center. What we typically talk about in this notion of hybridity on the VMware vCloud Air platform is that you can take your existing compute and network and storage and extend that to vCloud Air so your people, your processes, your tooling, it basically becomes your hybrid data center and it looks and feels just like what you're already running in your own four walls.

If we look at the next slide and some of the pieces where we feel this is ideal for mobile. If you think about all these mobile devices that could potentially be nailing your data center this is one of the most basic value props of running your mobile services on vCloud Air. It could be for security purposes. Maybe you want to keep your data center completely abstracted from those devices. Maybe you want the core data and database access completely remote. As I mentioned a minute ago, do you really want 10,000 random devices nailing your data center 24/7 so just security or performance alone can make this less than optimal for most shops. Also even setting up and configuring the services themselves.

Your current available capacity maybe fine but by definition mobile workloads can be very unpredictable particularly when you think about seasonal workloads but what about seasonal mobile workloads? What if you do promotions that you're building a mobile app for or something where you're doing a tweet jam but you want it to go through the mobile app? These are things that having to worry about budgeting or planning for capacity in your own four walls maybe a challenge so you don't have to worry about that if you're doing it on vCloud Air.

You may also notice that the word direct connect there that's connecting vCloud Air to your private data center. This is a service that we offer where we literally lock down a port on our network just for you and you can drop in the high speed connection like an [MPLS 00:23:46] connection so you can now get that super low latency between your file instance and your private data center. Once again Rosie mentioning about some of the data store and some of the synchronization features. You're able to do that as well as have low latency to other data you may need to go back and get so once again very very ideal use case for mobile.

When we go to the next slide where we talk about the actual value prop of enterprise hybrid cloud in general, you can actually extend this and consider this to be hybrid platform as a service or hybrid PaaS. What I mean by this is if you look at the diagram Pivotal Cloud Foundry is actually a distribution that's available on both vSphere and vCloud Air and this would also include the Pivotal Mobile Services so you can pick and choose where you want to run which applications. Some apps may have requirements that you need to run them in your own data center. Maybe there's data sensitivity issues that makes cloud a non-starter. Maybe you just want to have control down to the bare metal because you want your own staff to be able to get down to that level in case of an emergency. The bottom line here is whether it's your standard development that you might be doing on [PCF 00:25:03] or the mobile apps themselves you can pick and choose any app for either private or public deploy based on VMware, vSphere, and vCloud Air.

If we look at some examples of this on the next slide this is where we talk about a couple example use cases of where when I say hybrid PaaS why this is critical when you're planning out not only a mobile strategy but even just your application development strategy overall. We throw three of them out here so one is based on application life cycle stage. Once again if you want to have that control and you want production to be on vSphere in your own data center but you want to use vCloud Air or the cloud just for sandboxing because maybe once again at certain times of the year maybe you want to have more [burstability 00:26:00] for doing testing because maybe you have an app that you're building just for Christmas for example since we're in the Christmas season but then you're not going to really use that as much moving forward. That's a perfect cloud use case.

You also might do it based on enterprise requirements so with tier 2, tier 3 apps. Maybe ones that don't have the same SLAs so you don't have the same concerns over performance. Maybe that's your vCloud Air solution but if you do need once again spinning disk access and configuration and specific resource pooling that your infrastructure administrators control down to the bare metal as I mentioned, that's another great use case for vSphere.

Then the last one on the right here where we talk about scale requirements, predictable scale. Once again, the fact that you need to budget for capacity. You need to verify projects and plan for those projects. If that's the type of workload perfect for vSphere but when we talk about burst-scale or commonly called web-scale or some of the examples that I gave before around mobile applications that could have very random scale. Once again perfect use case for vCloud Air. This notion of a hybrid platform as a service and how it applies to not only existing regular applications or core platform as a service apps with regular web apps, applying this to both that as well as mobile and private and public is where a hybrid PaaS platform we feel is an ideal choice.

Rosie can I turn it back over to you in terms of how we both feel about enterprise PaaS and mobile.

Rosie: Thanks Jay. Thanks for that overview. That was really good and really helpful. We'll just wrap it up here quickly. I hope you have enjoyed this overview of enterprise platform as a service, mobile, and vCloud Air and just some key takeaways that we wanted to reinforce and leave these ideas with you. The fact that mobile apps and mobile enterprise apps require this next generation of an open cloud platform and that you don't have to do that in the public cloud. You don't have to stitch together multiple public solutions. You can actually have this all running together on your private or your hybrid cloud. Enterprise PaaS offers that agility and speed that you need to meet your mobile app demands for millions of customers and devices.

Again the paradigm has shifted from supporting tens of thousands of employees to millions of customers and devices. You want to be able to iterate on your apps quickly as well as build them out with these new cloud mobile architectures and to do that a new platform is really needed. Then finally of course Pivotal Cloud Foundry and vCloud Air are these leading enterprise mobile solutions that you're going to be able to have that flexibility, that reliability, that security, that governance, and that flexibility to run the apps as you want to run them as Jay was mentioning and also to account for the new mobile traffic, dynamic traffic, and workloads that you're going to be seeing.

Jay, anything else that you wanted to add for our audience?

Jay: No, I think in general this offering from me personally as I mentioned before it's almost embarrassing to say in the old days when it was three or four years ago. Seeing this evolution of mobile architecture is very exciting so hopefully anybody else that feels the same way reach out to your local Pivotal reps and ask for a deeper dive.

Rosie: Great thank you and so at this time we're seeing a few questions come in. If you have any we're not going to open up the line but put them into the chat box and Jay and I will be happy to take some questions. Let me field one that I saw pop up.One of the questions that came up it said okay well great, how is enterprise PaaS different than mobile backend as a service?

If you think about it there's different layers of things that you need to do to develop a mobile application. You have of course the client SDKs that develop things like the iOS apps, the Android, that live resident on the phone but then you have also of course all the backend enterprise app type of solutions and there are a couple of different layers out there on the market. One is a mobile application development platform and these other solutions are called MBaaS or mobile backend as a service. Those can be separate solutions as we talked about but what we've done with enterprise PaaS and what even we've heard some of the analysts say is that they see those two, the MADP layer and the MBaaS layer actually rolling into the PaaS because those features, those capabilities, can easily be consolidated and that's really what we're seeing and talking about here with enterprise PaaS.

We talked about some of the limitations of those so the other thing is if you think about it as an IT department. When you're trying to run these apps and troubleshoot, if you have separate platforms that some are on premise and some of them live off in a service provider off premise, a public cloud, then you've got to purchase and learn them and manage them and scale. As we talked about before, you're not getting any of the operational visibility that you need and that you want for your enterprise apps. We really see the mobile backend as a service more or less converging into this platform as a service concept that we're talking about here. Hopefully, that answers the question there.

I got another question coming in. That one is what about other mobile services? Is that all we have?

Well, actually no. You're in luck. We are going to be introducing more mobile services as they become available because Pivotal actually has been developing mobile apps for many many years. Actually since the first iOS device came out and so we're quite versed in what the demands of mobile application development is as well as performance are so we've got a great roadmap of services that are going to be rolling out actually continually starting this quarter.

Soon to be released we have something for mobile identity coming out as well as app distribution and app configuration so that's just a little peak into how we're going to continue to build out these services. Again you'll be able to use your enterprise PaaS platform going forward to do what you need to do for mobile and we have years and years of experience and folks have been building these applications. Thousands of apps with some of the biggest logos in the industry who know and have seen some of the limitations with the MBaaS platform so we've said look we can develop our own and you can run them all in one place.

Another question along similar lines. How does this actually help building the apps out themselves?

We mentioned a little bit about how there's different tools that you can use to run the apps as well as to build them so we actually work with the client applications, the SDKs tools, for Android, iOS, et cetera and then the backend frameworks and languages you are already working with so there's nothing different there. I guess we've been building mobile apps. We have a lab, our Pivotal Labs practice, that actually is really well-practiced in helping enterprises bring things like agile and continuous delivery practices to their enterprise. If you're interested in getting an app to market without building your platform, without picking a platform on it, initially we can certainly do that. Build your app for you. Show you how to use the leading tools and practices and methodologies and then you can have the platform and take it back on premise. We've got a lot customers who are saying show me how, give me the platform, give me the tools, teach me how to fish, and then I'm going to go build it and run it on my own enterprise. We've got that capability too.

Let's see, any other questions coming in. I think we're probably good there. That's all we have time for right now. I'm getting the sign to wrap it up and we're supposed to go about 30 minutes and I think we're a little bit over now. Thank you so much for joining us this morning or this afternoon wherever you are. Jay, any final parting words for our audience?

Jay: No, you know what guys thanks for joining. Other questions you may have feel free to send them in and we'll be sending a follow-up email to everybody with a lot of these questions and answers to make sure that we get them all answered your way. Really appreciate the time.

Rosie: Great and then I just put another slide up there on the screen. We have a Pivotal Platform Roadshow that has been going on the last few months. If you'd like to attend one you can go to our web page and register and then you can also learn about VMware, vCloud Air, and learn about our products at the Pivotal website or the VMware website respectively. Thank you so much again for your time and for joining us. We hope it was informative and useful and please let us know if you have any other follow on questions.

Jay: Thanks everyone.

Rosie: Thanks.