All technology evangelists talk about revolutions. Even they just have a classic product to demonstrate. So, if I tell you that the Cloud will change the IT industry, you may consider that I'm biased, being a CloudBees employee. Anyway, I'm convinced that a huge shift has been introduced by the Cloud technologies and the way in which we develop a software and use it to host the application will enter a new age. To demonstrate my point of view, let's compare with another major revolution that changed the industry all around the world.
In the late 19th century, industry development discovered the flexibility of using electric engines compared to traditional steam ones. This was a huge improvement and was adopted for most of the activities. At this time, every manufactory has its own generator, sized to produce power for the engines they used internally.
With the adoption of electricity, sharing resources and concentrating on the generation of electricity was a natural shift from dedicated on-premise generators. This was a major improvement to reduce costs and to improve reliability and flexibility. First, power plants were created by large manufactories for their internal needs but quickly, a dedicated industry emerged, specializing in large-scale electricity generators.
From manufactories, electricity gradually began to be used for general purposes, and power plants became bigger and much more advanced to become the nuclear plants and giant hydroelectric generators we use today.
Such a shift from on-premises generators has been possible thanks to specialization and standardization. Some incompatible standards still exist for power plugs and voltages, as some of you may have experienced while travelling around the world, but that's nothing compared to the early electric age.
In 1900, Paris was split into six regions, each of them with a distinct company to produce electricity for public lighting. Some of them used a direct current of 110 V, some others used a high voltage, as much as 3000 V. Some used two, three, or five wires to transport power to users. With power plants to concentrate into bigger companies, standardization helped to make electricity something that you don't actually have to worry about. If you don't have to travel to another continent—not considering myself traveling to London—you can use exactly the same electric device, without even thinking this could be an issue.
Nowadays, electricity is used as a service and you don't know from where it gets produced. You just rely on some standards to plug in your toaster and get it to work. You pay a bill per month, based on your actual use of electricity. You don't mind, when you buy a new washing machine, the amount of electricity it will require—maybe you should anyway—because you know your electricity producer will give you more when needed.
Automated computing is such a revolution and is getting even quicker. First, the computer replaced human beings for repetitive computational tasks. They were huge, complex, and dedicated mainframe machines. With large acceptance, some standards emerged, such as Unix/Posix compatible systems, and helped to reduce the dependency you had as a computer user on a specific hardware.
First, datacenters could be considered as equivalent to power plants; users didn't actually know where the computer was located physically and where they were connected to, on a vt100 terminal. They were just sharing resources, concentrating in a specialized location, with dedicated engineers and technicians.
Cloud is the next step. When Amazon creates a datacenter, it's about hundreds of thousands of computers that will be available for consumption using an API to rent them. You don't need to have a dedicated server anymore; you don't even have to estimate how large it has to be. You only rent one for your actual use and you can change your mind at any time.
The major shift with the traditional datacenter is that it's not just about grouping the resource in the same building, rather it's about sharing the resources for the whole world, without worrying about who is actually using them, and making it available using the 21st century power plugs, APIs—either de facto standard Amazon Web Services or open source OpenStack.
Cloud is such a big change that it completely changes our industry. There is no need to spend hours estimating our hardware requirements when a project is just a bunch of ideas that need to be prototyped. You'll have the adequate hardware available and can stop anything at anytime without any extra costs.
This book is a great opportunity for me to share my knowledge about the CloudBees platform on which I'm working as a support engineer. I'll guide you on how to discover the platform and show you its benefits for software projects, as well as the changes it allows you to make your development process more efficient.
Chapter 1, What's a PaaS and Why CloudBees?, introduces the concept of Platform as a Service (PaaS) and why this is the best place for a developer to start using Cloud services. We will also introduce CloudBees high-level vision of PaaS.
Chapter 2, Getting Started Quickly, covers setting up your CloudBees account and using ClickStart to get an application ready to develop within a minute. Also, it explores the services provided by the CloudBees platform.
Chapter 3, Users, Domains, and Services, explores the CloudBees platform from a user management point of view. It also covers the service ecosystem that makes the CloudBees platform extensible to match your requirements.
Chapter 4, ClickStart in Depth, gets deeper into the concepts of ClickStart and demonstrates how to use it in order to improve your own efficiency.
Chapter 5, Managing Your Build, demonstrates the use of the DEV@cloud platform to drive your project build and development workflow.
Chapter 6, Running Your Applications, explores the application-hosting service and options to manage your application scalability and security.
Chapter 7, Tools, demonstrates the advanced use of the CloudBees platform using the SDK, as well as other development tool integrations.
Chapter 8, Using ClickStack to Extend the Platform, gets deeper in to the RUN platform and its extensibility capabilities. It demonstrates how to select an alternate stack, customize, or create your own ClickStack.
If you are a Java developer and want to explore the world of the Cloud, this book is ideal for you. This book will guide you through the process of developing and deploying an application on the Cloud. Prior knowledge of Java is essential.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "The project skeleton is basically a Maven pom.xml
file and comprises few classes."
A block of code is set as follows:
"build-with-jenkins": { "template": { "type": "https://raw.github.com/CloudBees-community/play2-clickstart/master/jenkins.xml" } }
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
"app-variables":{ "proxyBuffering":false, "http_version":"1.1" }
Any command-line input or output is written as follows:
git push heroku master
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes, for example, appear in the text like this: "To create an account, www.cloudbees.com provides a SIGN UP link."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>
, and mention the book title through the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website, or added to any list of existing errata, under the Errata section of that title.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]>
with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]>
if you are having a problem with any aspect of the book, and we will do our best to address it.