Last year, we made 12 predictions about what would happen in the cloud space in 2013. As the year comes to a close, it’s only fair for us to assess our hits and misses to see how well we did.
Recap and Scorecard
PREDICTION #1: 2013 will be the year of cloud management software.
REALITY: Hit. We saw this come true on multiple fronts. First, cloud management providers Enstratius and ServiceMesh were acquired by Dell and CSC, respectively. Tier 3 – known for the sophisticated management software that runs our IaaS – was acquired by CenturyLink. On top of this, Gartner estimates that a new vendor enters the cloud management space every month, and nearly every cloud provider is constantly beefing up their own management offerings. This shows the strategic value of comprehensive management capabilities in a cloud portfolio. Customer adoption of these platforms is also on the rise and Gartner sees 60% of Global 2000 enterprises using cloud management technology (up from 30% in 2013).
PREDICTION #2: While the largest cloud providers duke it out on price and scale, smaller cloud providers see that enterprise adoption really depends on tight integration with existing tools and processes.
REALITY: Mixed. Of course, cloud prices definitely declined in 2013 and massive scale continued to be a key selling point. Hybrid cloud picked up momentum this year as more companies looked to establish an IT landscape that leveraged on-premises assets while taking advantage of cloud scale. In order to maximize the efficiency of hybrid scenarios, companies need consistency in processes and tools. While cloud management platforms have helped with this a bit, there wasn’t a wholesale move by cloud providers to seamlessly integrate their core offerings with established products.
PREDICTION #3: Enterprises move from pilots to projects, and architecture takes a front seat.
REALITY: Hit. There’s been much less gnashing of teeth on “should I use the cloud” this year, and much more discussion about how to capitalize on the cloud. We’ve seen our customers move to more substantial solutions and ask for more sophisticated capabilities, such as self-service networking. Throughout the industry, we’re seeing more enterprise-class case studies where customers are putting mission critical workloads in the cloud. However, outages still occur on any cloud, and providers are publishing guidelines on how to properly architect for high availability. The recent AWS conference was full of sessions on architecture best practices, and developers are hungry for information about how those best practices are applied.
PREDICTION #5: Standalone, public PaaS offerings will be slow to gain enterprise adoption.
REALITY: Hit. In 2013 we saw renewed discussion on what PaaS actually is and what it SHOULD be. Longtime PaaS providers Microsoft and Google added IaaS products to their portfolio, while smaller firms like Apprenda saw success in private PaaS. Our sister company, AppFog, has launched over 100,000 apps, including some impressive enterprise deployments. Former Tier 3 colleague Adron Hall asked whether PaaS was still “a thing” or whether new container technologies like Docker were going to replace it. However, as some like our own Jared Wray and Red Hat’s Krish Subramanian have said, PaaS is about more than JUST application containers. A rich PaaS also includes the orchestration, management, and services that make it a valuable platform for web applications of any type. Either way, PaaS is still in its infancy and will continue to morph as customer scenarios take shape.
PREDICTION #6: Public goes private.
REALITY: Mixed. There were hints of this in 2013 as Amazon won a bid to win a private cloud for the CIA (and for you too if you have half a billion sitting around!), Microsoft offered a “pack” for making on-premises environments resemble their public cloud, and platforms like OpenStack gained traction as a private cloud alternative. We continued to make advances in supporting private scenarios by adding self-service site-to-site VPN capabilities to an already-robust set of connectivity options. I gave this a “mixed” score because as a whole, public cloud providers don’t yet (and may never) make it simple to run their stack in a private data center for mainstream enterprises.
PREDICTION #7: Cloud providers embrace alternate costing models.
REALITY: Hit. 2013 saw some changes to how cloud customers paid for resources. We modified our pricing to decouple some components while still making it easy to provision exactly the amount of CPU, memory and storage that you need for a given server. Google and Microsoft both launched their IaaS clouds with “per minute” pricing for compute resources. Cloud providers have yet to move to a “pay for consumption instead of allocation” model for things like storage, but overall we’ve seen a maturation of pricing considerations in 2013.
PREDICTION #8: While portability will increase at the application and hypervisor layer, middleware and environment metadata will remain more proprietary.
REALITY: Mixed. We might have been too pessimistic last year! DevOps tools have flourished in 2013 and platform adapters have made it possible to move workloads between clouds without a massive re-architecture effort. To be sure, code portability is still MUCH simpler than environment portability. Each cloud provider has their own value-added services that rarely transfer easily to other locations, and no clear IaaS standard has emerged. However, platforms like OpenStack are attempting to make cloud portability a reality, and the increasing prevalence of public APIs makes it possible for tools like Pivotal’s BOSH or Chef to orchestrate deployments in diverse provider environments.
PREDICTION #9: Global expansion takes center stage.
REALITY: Hit. One of the first questions we hear from prospective customers is “where are your data centers?” This year, almost all of the leading cloud providers expanded their footprint around the globe. For our part, we added data centers in Canada, the UK, and Germany. Now, as part of CenturyLink, we have major expansion plans in 2014.
PREDICTION #10: IaaS providers who don’t court developers get left behind.
REALITY: Hit. In 2013, Stephen O’Grady wrote that developers are the “new kingmakers” and this was reinforced by Gartner analyst Lydia Leong who wrote that IT operations no longer has a monopoly on cloud procurement. Developers are now running the show – bringing in vendors that meet their unique criteria. Consequently, a new crop of developer-centric cloud providers has popped up. While they don’t offer managed services or sophisticated resource management, they DO help developers get going quickly in the cloud. We wooed developers with new self-service capabilities, API improvements, and with new features like Autoscale and webhooks. Developers will continue to be a focus for us at CenturyLink and we plan on continuing our regular Open Source contributions!
PREDICTION #11: Clouds that cannot be remotely managed through an API will fall behind.
REALITY: Hit. APIs are the gateway to modern services and allow ecosystems to flourish. Consider the vibrant crop of cloud management platforms discussed in prediction #1. And that is just one small example. The vast majority of clouds listed in Gartner’s 2013 Magic Quadrant for Cloud Infrastructure have public, comprehensive APIs that developers can use to consume the cloud in whatever way they want. In 2013, we started an effort to replace our existing API with an even more expansive offering that offers complete parity with our industry leading Control Portal user interface. That effort will continue into the next year. When complete, a new host of capabilities will be accessible for CenturyLink, our partners, and mostly important, our customers.
PREDICTION #12: Usability and self-service become table stakes for cloud providers.
REALITY: Mixed. In 2013, we seemed to hit the point where “clouds that aren’t really clouds” struggled as the market began to demand more. Customers expected more and more self-service capabilities, and Tier 3 – along with most every other major provider – focused heavily on that in 2013. Platform usability was a lesser focus this year. While new clouds from Microsoft and Google included relatively straightforward user experiences, few providers made any massive visual improvements. While the CenturyLink Cloud continues to be lauded for an easy to use, powerful interface, we haven’t stood still. A major redesign is underway that will surface more data, simplify activities, and improve performance.
2013 was an important year in the maturation of the cloud industry. New vendors were introduced, popular platforms were acquired, and consumption of cloud services skyrocketed. What will happen in 2014? Stay tuned for our predictions!
Last week, CenturyLink Cloud led a webinar focused on helping organizations kick-start their cloud efforts. While the cloud makes a lot of sense for organizations of all sizes, it can be daunting to get started with such a disruptive initiative. No doubt that most CIOs have heard horror stories about failed cloud initiatives, so how do they avoid becoming a statistic? CenturyLink Cloud offered five best practices to help companies take a successful plunge into the cloud.
#1 - Form a “tiger team” to achieve quick wins and pursue IT-as-a-Service
What’s a “tiger team”? I liked this description of its military background and applicability to IT:
“When the Navy needed some quick turnaround work or repairs, they would assemble a tiger team,” Ballard said. “The connotation was that it was a self-contained team that included all the skill sets and resources needed to do the work — journeymen, planners, engineers, fabricators, etc.”
“A tiger team was a small hand-picked, particularly skilled and capable group of ‘tigers,’ often chosen and chartered by a commanding officer, to plan for and/or achieve a very specific mission,” Lehman said.
The good news - you probably do this in your organization today when new, major initiatives come up and big organizational change happens. This cloud-oriented tiger team should be tasked with identifying strategic projects and executing them. Instead of pursuing complex, instantly-outdated, multi-year plans to embrace the cloud, start small and get moving! Ideally, this team is comprised of executive sponsors (from IT and other business units), a program lead, business analysts (who understand standard operating procedures and business needs), application architects, network engineers, and developers. This is a team of hands-on doers, not a bunch of box-drawing hand-wavers. Find the top performers in your organization and assemble them into a team that can partner with business units and start delivering high-value projects while aggregating valuable knowledge about cloud technology and IT-as-a-Service.
Another bit of good news – the individuals on the soon-to-be tiger team are already thinking of cloud on their own time, and have likely been itching for this kind of assignment.
#2 - Find the *right* cloud provider for your organization.
There are dozens upon dozens of interesting cloud infrastructure providers, and they aren’t all the same. Some are vanilla providers without much differentiation while others offer something unique.
The trick is finding the right one that is a match for your organizational culture, skills, priorities, or business needs. This isn’t unique to the cloud and applies to many (most?) of the strategic investments that a company makes. It’s likely that you have an evaluation process in place today that use assessment checklists, preferred vendor lists, strategic sourcing departments, and more. You also likely have a set of IT requirements that any new vendor needs to comply with. Here are some things to make sure you are thinking about:
- Security capabilities. What kind of physical, network, and account security does the provider offer? Are you running batch jobs with sensitive data, or hosting a public website with limited private data?
- Compliance certifications. Do you need assurances that the provider can host HIPAA or PCI-compliant applications? Are you storing data for EU users and weighing data sovereignty concerns?
- Performance. Does the provider offer server and network specifications that meet or exceed what you have in house? Does that matter for the types of applications you plan to run in the cloud? Can you provision components (virtual machines, storage, networks, etc.) at different performance levels to meet your needs?
- High availability. Are the various services you depend on individually designed to be highly available, and does the provider offer the necessary services (e.g. VPN) to architect highly available applications on the platform?
- Strong SLAs. Cloud failures are inevitable, so how does the provider define their SLA with regards to availability, response times, and outage credits?
- Disaster Recovery procedures. Do you have mature processes in place to manually fail over in the case of a full site outage, or are you looking for a provider who delivers a built-in DR capability?
- Global footprint. Location, location, location. Does the provider’s data center presence match your customer and employee geographies?
- Management interface. The creation of a cloud resource is invariably the smallest portion of its lifespan. So, it’s great if you can spin up individual servers or databases quickly, but how easily can you manage them after the fact? This may include installing updates, resizing capacity, changing security roles, or even shutting it down.
- Application services. Do you need more than raw infrastructure? Looking for managed databases or web platforms that abstract away the low level details? Or storage services that can be accessed from cloud – or on-premises – systems?
- Pricing plans. Are you looking for a fixed contract (or monthly commit) that results in lower costs? Or do you need a provider who delivers true pay-as-you-go services?
- Support. What level of support is needed? Do you want a dedicated support person? Call center? Public knowledge base? User forums?
- Professional services. Do you expect a consultative experience during the POC stage or when doing critical business updates? How about the full outsourcing of cloud server management to the provider?
Assess what really matters to YOUR organization, and find the provider who most closely matches those priorities.
#3 – Find, partner with, learn from, and collaborate with shadow IT.
What is Shadow IT? A phenomenon that occurs when there is unmet technology needs in an organization and employees “go rogue” and use non-standard solutions. You’ve likely read negative press about the concept and you might even have corporate initiatives meant to stamp it out.
Where do you often find shadow IT in your organization?
- Line of business applications. These are the applications used every day to collect, store, and analyze data used for business decisions. This can take the form of Microsoft Access databases, Filemaker Pro applications, Excel workbooks, or custom developed web applications.
- Productivity solutions. This is the technology that is meant to improve efficiency and collaboration. Bring-your-own-device (BYOD) brought this to the forefront as employees used tablets and smartphones at work, whether supported or not. Other things in this category include instant messaging and VOIP tools like Skype, and virtual meetingplace tools like Google+ Hangouts.
- Data management. Often departments need to store, analyze, or transfer data and don’t like the sanctioned options offered by corporate IT. This may mean creating production database replicas for later analysis (by custom BI tools!), or using storage services like DropBox to exchange files with business partners.
The bad news? These shadow solutions may not meet corporate security standards, are invisible to IT audits, don’t feed innovative ideas back to central IT, and frequently become too large and difficult to maintain locally.
Now, the good news – your employees are showing initiative and can show you exactly how IT can improve day-to-day productivity!
The one thing all the above categories has in common is how much EASIER each one is in the cloud. Today, you can use a credit card to provision enterprise-class CRM, ERP, marketing, and HR software in the cloud without batting an eye.
Instead of shaming and shutting down those in your organization who are trying to solve problems in new ways, partner with them and make them some of the most passionate advocates for your new cloud projects. Figure out what technologies they’ve pursued, how they evaluated them, and use their knowledge to make better cloud choices.
#4 - Learn and enable best practices in the cloud.
The cloud is very different from how you do on-premises enterprise IT. Resource planning, financial projections, technology choices, level of control, and self-service model are all very likely foreign to your IT department. Therefore, carefully consider how you discover and capture best practices in this new world. What are some areas to focus your attention on in order to truly take advantage of the cloud?
- Embrace automation everywhere. Automation is the difference between long-term cloud success and simply having a souped-up virtualized environment. Self-service is critical for the agility promised by the cloud, and that’s only possible if you’ve made a concerted effort to automate nearly every activity in the application lifecycle. This includes provisioning environments, updating environments, continuous application deployment, automated testing, auto scaling of servers, and much more. Could you immediately adopt an immutable server model where you never update a deployed server, but simply re-create it whenever there are application changes? If not, look at how you do these sorts of things internally today, and start introducing processes and tools that will make it that much easier to understand and exploit the cloud.
- Design software differently. New web applications (whether hosted in your data center or the public cloud) should be built for multi-tenancy, statelessness, horizontal scale, ready for failure, and service-oriented. This means building applications made up of components that can scale independently, communicate asynchronously, and have no dependency on a particular piece of hardware. Deploying an application in the cloud doesn’t guarantee high availability; rather, the application must be specifically architected in a way to be resilient from failures. This may be counter to how applications are built in your organizations today, but unless you design web applications in this manner, you’ll find it difficult to take full advantage of the cloud.
- Use the right service for the right situation. Not everything belongs in customer-managed virtual machine. Cloud computing is made up of many “as-a-service” offerings, some of which take the management burden away from the customer. Consider services like database-as-a-service where a provider manages the database infrastructure and the customer doesn’t have to worry about provisioning, scaling, backing up, or patching servers. Or object storage services that let you store massive amounts of highly available data without worrying about setting up that infrastructure yourself. If you don’t need complete control over the infrastructure, look to other types of cloud services that take that work away.
- Apply security everywhere. Get ready to secure your data at rest and in transit. Get familiar with data encryption concepts and tools, and don’t simply rely on peripheral security to protect your servers and data.
- Get your hands dirty! Maybe the most important item in the list. Every senior architect and developer in your organization should have a (free) account set up for all the major cloud providers. Try things out. Fail quickly and safely. Figure out what works and what doesn’t. The cloud has made it amazingly simple to explore and experiment with technology and you should be actively encouraging your technical team to try it out.
#5 – Carefully assess which applications to migrate.
Not every application is fit for the cloud. Many applications in your data center weren’t built with the cloud in mind. They may be monolithic applications that aren’t naturally redundant and resistant to failure. They could use hard-coded configurations and IP addresses, and expect physical proximity for all components. Simply moving these types of applications won’t grant magical performance or scalability improvements, and may actually result in a worse experience.
However, if you have cloud-friendly applications in your data center, you may realize value from moving them to a cloud environment. There are at least three techniques to follow.
- First, you can lift-and-shift and simply take the application as is and move it to the cloud.
- Second, you can refactor the application and make small changes to make it friendlier to cloud environments.
- Finally, you could do an entire rebuild of the application to completely optimize it for the cloud. Odds are, the last option is not economically beneficial, and it’s better to leave the application where it is.
The best migration candidates include vanilla packaged applications like Microsoft Exchange and Microsoft SharePoint, public-facing Internet websites, applications with bursty or unpredictable usage, applications/façade for mobile users, and custom service-oriented web applications. Consider leaving the following types of applications in your own data center: monolithic applications that can’t be easily broken apart, applications with extensive integrations with on-premises systems, heavy I/O applications or those optimized for specific hardware.
The cloud offers game-changing opportunities for organizations who take advantage of it. We’ve seen organizations both large and small take the plunge and realize the benefits. Interested in talking with us and getting some help on your cloud journey? Contact us today and we can help you avoid the pitfalls and get up and running quickly.
Just a couple weeks ago, we looked at how Platform-as-a-Service (PaaS) helps developers rapidly build and deploy applications to the cloud. We also covered a new breed of cloud-based development environments (IDE) that developers can use to create and publish their web applications. Since then, the cloud-based IDE we featured – called Codenvy – has updated their product to support the CenturyLink Cloud Platform as a Service. In this post, we’ll walk through how to quickly and easily deploy and manage Platform as a Service applications from your web browser.
To start with, when users of Codenvy start a new web application project, they are asked which technology they want to use, and then which PaaS to deploy to. At this moment, the CenturyLink Cloud Platform as a Service is available for Java Web Application (WAR), Java Spring, and Ruby on Rails projects. Note that Platform as a Service works with more environments than these three, but these are the technologies supported via Codenvy.
Once the user chooses the technology and corresponding PaaS, they choose a simple project template (if one exists for that technology), and are then asked for the management API endpoint of the Platform as a Service environment.
The project framework is then created, and the user is prompted for their Platform as a Service credentials. After providing a valid username and password, the application is deployed and Internet-accessible. All of this in matter of seconds! To update the application, developers visit the PaaS menu option and choose CenturyLink Cloud Platform as a Service.
From the subsequent window, developers can modify the name, URL, and memory allocation of the application. Additionally, the application can be started, stopped, deleted, and updated. It’s also possible to add Platform as a Service application services – such as RabbitMQ for messaging or Microsoft SQL Server for relational database storage – to a project.
Codenvy can also be used as a simple management interface for any applications running in Platform as a Service. This can come in handy if you’re on a shared machine without the typical Cloud Foundry management tools available!
This interface shows you each application running in your Platform as a Service environment, and lets you start, stop, restart, or delete it.
We’re excited to be a supported part of the innovative Codenvy platform and think that this lowers the barrier to entry for our customers while making it simpler for developers to build amazing applications in any language of their choice. Want to try it out? Sign up for a free Codenvy account and then take Platform as a Service for a spin!
Web applications are a dominant part of most enterprise IT portfolios and Platform-as-a-Service (PaaS) products offer a compelling way to easily deploy and manage these applications. However, PaaS have proven tricky for vendors to explain, and therefore difficult for customers to understand. In this post, we’ll discuss the reason you should consider using PaaS products, what CenturyLink Cloud has to offer, and how you can deploy a web application to a PaaS in a matter of minutes.
Benefits of PaaS
What exactly is PaaS? Basically, it’s a way of delivering an application platform as a service. Developers don’t interface directly with infrastructure (e.g. servers, networks, load balancers) but rather, focus on building and deployment applications through a set of exposed services in a managed fabric. PaaS simplifies the deployment and management of modern web applications while making those applications more resilient and functional. How can PaaS add value to your organization? Let’s drill into some specifics:
- Reduce server sprawl with a centralized host for web applications. How many web servers are sitting relatively idle in your data center because they are only running a handful of applications? Server sprawl can be a major issue as each IT project requisitions its own hardware for application development/staging/QA/production. What about all your websites for customers and marketing campaigns? It’s possible that you’re using many different servers (and even providers!) to host all of those individual websites. PaaS can offer a centralized fabric that can be sized and optimized for hundreds of internal or external web applications.
- Save money by adding resources only when you need them. Many PaaS products have a concept of automatic scale or user-driven resizing to account for spikes or dips in utilization. Before cloud computing, organizations typically sized their infrastructure for peaks and accepted that their environment would be underutilized the majority of the time. Now, it’s possible to deploy a web application with a 128MB memory allocation, and instantly double it when needed. Need to spread the workload across multiple machines? Simply issue a command to add the application to another node in the PaaS fabric. No calls to the operations team, no formal “deployment” exercises. PaaS makes it possible to size and scale applications on demand, which makes it easier for you to manage the overall environment.
- Focus on your application, and don’t sweat the infrastructure. One of the most important benefits of PaaS is that it abstracts the infrastructure away from the application, and the developer. Developers deploy to a fabric, not a server. There’s no need for the IT project team to provision web or database servers. Simply push applications to the existing PaaS environment. The infrastructure itself is managed closely by an operations team and automation is included at all levels to deliver automatic patching, scaling, monitoring and more.
- Multi-tenancy and high-availability baked in. PaaS products are designed to deliver high-availability to multiple applications (or “tenants”) and are therefore scaled out to provide significant compute capacity. As such, you’ll find many PaaS products with built-in load balancing services, failover when servers fail, concurrency management, and more. All of these features boost reliability and performance for each application hosted in the PaaS. Even applications not specifically designed for PaaS can conceivably be deployed to a PaaS with little to no code refactoring.
- Avoid unnecessary duplication by using consolidated application services. When most people think of PaaS they think of hosting web applications, but some of the best capabilities are those offered by complimentary services. Most PaaS products offer add-on services like databases, storage, identity management, messaging, caching and more. You’ll also find some PaaS products that offer business services such as service catalogs, and API management and monitoring. Developers can use these services when building their web applications and not have to provision or locate hardware to host those services at runtime. These services simply exist inside the PaaS and are available to all applications deployed there.
- Deliver “IT as a Service” through measured usage for easy chargebacks. A core tenet of cloud computing is “pay as you go” and measured usage. A true PaaS is built upon a “cloudy” foundation that tracks utilization and delivers an all-up cost to the user at the end of the month (or whenever the user checks their charges). Because of this cost transparency, it’s easy for organizations to deliver “IT as a service” by offering a PaaS for internal/external websites and passing along the usage-based invoices to each department.
All of this helps developers produce faster deployments while giving system administrators a more streamlined operations responsibility.
Why CenturyLink Cloud Platform as a Service?
CenturyLink Cloud has its own PaaS product – called Platform as a Service – that is based on Pivotal’s Cloud Foundry project. We’ve added the open-source Iron Foundry extensions so that we can offer some of the best language and framework support in the industry. Unlike the shared PaaS services offered by others, Platform as a Service is provisioned uniquely for each customer. This gives you the isolation you need, while still offering a robust platform for all the custom applications used by your organization. The default Platform as a Service environment consists of five total servers and can support dozens of web applications.
Why might you choose to use the CenturyLink Cloud Platform as a Service to host your modern web applications? We like to point out at least five reasons:
- Support for the programming languages you already use. Most IT shops are heterogeneous and use technologies from multiple vendors. You may have written a number of enterprise-class web applications in .NET or Java, but also have departments that make use of Ruby or PHP. If you’re doing more mobile development, you might have started looking at Node.js for high performing web applications. CenturyLink Cloud’s Platform as a Service supports all those programming languages and more. Instead of using multiple PaaS products or infrastructure clouds to host your diverse application portfolio, use a single fabric for all of them!
- Application services to cover your scenarios. Need a relational database? We offer MySQL, PostgreSQL, and Microsoft SQL Server. Looking for a NoSQL repository? Platform as a Service has Redis and MongoDB. RabbitMQ is also available when you want to add a durable message queue to your solution. In addition, each Platform as a Service comes with New Relic monitoring for web applications. This excellent application performance management tool gives you deep insight that helps identify bottlenecks and monitor application health.
- Cloud Foundry ecosystem. There’s no doubting the impact of Cloud Foundry on the PaaS industry. This open source project was launched in 2010 and has been adopted by multiple PaaS vendors. Not only does this make it straightforward to move applications between Cloud Foundry-compliant clouds, but also means that there are multiple parties creating tools that work for any Cloud Foundry environment. From the Windows-based Cloud Foundry Explorer, to the OSX-friendly Project Thor, to web-based development environments, there’s a growing ecosystem of vendors and tools to help you be successful with Cloud Foundry.
- Enterprise-class infrastructure. CenturyLink Cloud’s network of highly resilient, globally distributed infrastructure is optimized for performance throughout the stack. And since Platform as a Service runs on the CenturyLink Cloud enterprise cloud, your applications will be powered by high performing storage, multiple VPN options, security services, and much more.
- IaaS and PaaS, better together. Not all workloads fit into a PaaS platform, and not all applications require dedicated infrastructure. By offering our customers enterprise-class infrastructure in addition to Platform as a Service, we’ve provided two useful hosting mechanisms in the same cloud. Keep your PaaS applications geographically close to your IaaS applications and data, and share the same management tools, security profile, and networking configuration.
Deploying to Platform as a Service from a Cloud-based Development Environment
Developers can push their application to Platform as a Service in a number of ways. While most developers are familiar with command line interfaces and GUI tools that run on their desktop, a new crop of cloud-based integrated development environments (IDEs) can make PaaS deployments even simpler. Cloud IDEs offer excellent collaboration capabilities, easy accessibility, and “no-touch” setup.
One such cloud IDE is Codenvy. This tool works natively with Cloud Foundry, making it easy to build Java/Ruby/Python/PHP applications and then push them to Platform as a Service. After signing up for a free account, the developer is presented with the option to link to GitHub or any Git repository.
Codenvy uses a handy “new project” wizard experience to help the developer choose which programming language to use, and then which (supported) PaaS to push to. In the short animation below, observe how I created a new Java Spring project, chose Cloud Foundry (Platform as a Service) as a destination, finish the wizard and publish the application to Platform as a Service.
The Codenvy IDE includes many developer productivity features including type-ahead coding (i.e. “intellisense”), code generation, formatting tools, and much more. Changing the application code and re-publishing the application to Platform as a Service is simple. Notice how easy it is to resize my application (e.g. memory, instance count) at any time!
Besides simply deploying applications, Codenvy supports simple management of existing applications. From the PaaS –> Cloud Foundry –> Applications menu, I can see all the applications that I’ve deployed to Platform as a Service and stop/start/restart/delete any of them.
Developers using cloud-based IDEs don’t get all the features of desktop IDEs (like access to local resources, plug-ins), but they are an increasingly viable choice for developers who are trying new technologies or need access to their IDE from any computer.
With our enterprise-class infrastructure and platform cloud, CenturyLink Cloud is uniquely positioned to address your cloud needs. Platform as a Service is an ideal host for your modern web applications and its Cloud Foundry heritage makes it compatible with a wide array of tools including cloud-based IDEs like Codenvy.
Interested in taking a look at Platform as a Service? Contact us for a demonstration and free trial!
At CenturyLink Cloud, we’ve been big supporters of Cloud Foundry—the VMware-led, open-source PaaS framework—from the beginning. That said, we’re a .NET shop and many of our customers’ most critical applications are .NET-based. So today we’ve decided to contribute Iron Foundry, our own .NET fork of Cloud Foundry, back to the community as an open-source project.
This project includes both the primary framework as well as both a Windows version of Cloud Foundry Explorer and a Visual Studio Plugin for Cloud Foundry. (Video demos for the command line interface and Visual Studio plugin are located at the bottom of this post.) Because developers can run their own instances of Iron Foundry in-house or with any service provider who supports it, developers finally have a truly open, interoperable .NET PaaS solution that can be run inside and outside the firewall. And because you can run your own instances of Iron Foundry, it’s easy to have a full test, QA, and staging environment before pushing to production.
In addition, operations teams now have the freedom to choose among various service providers that meet their needs in areas such as security, compliance, availability, location, etc. For developers who are interested in trying Iron Foundry, we have put together a “try it now” test bed package on IronFoundry.org that offers the compute resources needed to run one web and one database instance per developer free for 90 days on CenturyLink Cloud’s Enterprise Cloud Platform. Iron Foundry is Cloud Foundry + .Net. This means developers have access to standard tools—enabling them to write .Net code against a MySQL backend, for example, or just write against a simple name-value pair datastore like Redis. Another advantage that Iron Foundry inherits is the ability to add instances to an application on the fly with the app being pushed automatically each new node. The core source code will be available on GitHub under an Apache 2.0 license. You can also download and install Iron Foundry with Cloud Foundry from our web site at www.ironfoundry.org. Read the full press release here.
Iron Foundry Video Demo