Lucas Carlson - Programming for PaaS
Here you can read online Lucas Carlson - Programming for PaaS full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2013, publisher: OReilly Media, genre: Business. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Programming for PaaS
- Author:
- Publisher:OReilly Media
- Genre:
- Year:2013
- Rating:4 / 5
- Favourites:Add to favourites
- Your mark:
Programming for PaaS: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Programming for PaaS" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Platform-as-a-Service (PaaS) is gaining serious traction among web and mobile developers, but as new PaaS providers emerge and existing vendors upgrade their features, its hard to keep track of what PaaS has to offer. This thorough introduction takes you through the PaaS model from a developers point of view, and breaks down the types of services that Google App Engine, Windows Azure, Heroku, Cloud Foundry, and others deliver.
Whether youre an entrepreneur or part of a large enterprise development team, this book shows you how PaaS can help you focus on innovative applications, rather than spend your time worrying about technical operations.
- Track the clouds evolution from IaaS and DevOps to PaaS
- Learn how PaaS combines the simplicity of shared web hosting with the control of dedicated hosting
- Explore the benefits of both portable and non-portable PaaS options
- Apply best practices for moving legacy apps to PaaSand understand the challenges involved
- Write new applications for PaaS from scratch with RESTful meta-services
- Use PaaS to build mobile apps with backend services that scale
- Examine the core services that each major provider currently offers
- Learn the situations in which PaaS might not be advantageous
Lucas Carlson: author's other books
Who wrote Programming for PaaS? Find out the surname, the name of the author of the book and a list of all author's works by series.
Programming for PaaS — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Programming for PaaS" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Beijing Cambridge Farnham Kln Sebastopol Tokyo
For Yoscelina, My Love,
Thank you for every nano-amount of support. I honestly do not think this book would be here if it were not for you and your encouragement. I love you for everything.
Lucas Carlson
If you purchased this ebook directly from oreilly.com, you have the following benefits:
DRM-free ebooksuse your ebooks across devices without restrictions or limitations
Multiple formatsuse on your laptop, tablet, or phone
Lifetime access, with free updates
Dropbox syncingyour files, anywhere
If you purchased this ebook from another retailer, you can upgrade your ebook to take advantage of all these benefits for just $4.99. to access your ebook upgrade.
Please note that upgrade offers are not available from sample content.
Programming is a hard job. Deceivingly so. At first you write code, and it works, and you are happy. Then it has bugs and you spend hours, days, even weeks trying to find, fix, and resolve bugs and edge cases. Then when you have everything perfectly programmed and just when you thought the job couldnt get harder, you have to go deploy your code. vim apache.conf. vim my.cnf. vim /etc/hosts. iptables . Just when you thought you were a programmer, all of a sudden you get waste deep in system administration and wonder how you got there.
If there is one thing that programmers are good at, it is being productively lazy. When a programmer does the same thing over and over again, eventually he thinks: cant my computer do this for me? Around 2005, enough programmers in the world had edited apache.conf files that something dramatically changed. A few brilliant programmers decided they didnt want to do it any more.
Out of this came two paradigms that have forever changed the landscape of deploying applications in the world: DevOps and PaaS. DevOpss response to apache.conf editing says: I can write code templates (called recipes or cookbooks) that do system administration for me. PaaSs response to apache.conf editing says: I can write a program that manages system administration for me. Many great books have been written about DevOpslike Puppet Types and Providers by Dan Bode and Nan Liu or Test-Driven Infrastructure with Chef by Stephen Nelson-Smithbut few books have been written about PaaS.
PaaS is great because you get the benefits of dedicated hosting (like each app running in its own process and load balanced to scale) with the ease of shared hosting (you dont do any configuration management, the PaaS does it for you). But those benefits come at a cost. You have to write code that works with the PaaS.
This topic has not been written about a lot: which programming patterns work well on PaaS and which anti-patterns no longer work in a PaaS environment ? This is the entire theme of this book. Although the popularity of PaaS has grown exponentially with millions of developers worldwide having already adopted it and millions more starting to learn about it right now, not a lot of work has been written to help guide developers on how to successfully incorporate PaaS best practices into their coding processes.
Specifically, one of the biggest challenges facing many developers working in businesses today is how to move legacy code and older applications into a PaaS paradigm. There have been few resources to help guide people through this challenge and hopefully this book will be a first step in the right direction to providing the dialogue.
This book is aimed at programmers, developers, engineers, and architects who want to know more about Platform-as-a-Service.
You do not need to be a programmer to find value in this book. In fact, if you are trying to convince your boss to let you use PaaS inside your company, you may want to give your boss a copy of this book. Alternatively, you can find resources for talking to your boss about PaaS, both the pros and cons, in . This will show you have thought through the problem from both sides of the table and have an informed opinion, not just a passing fashion.
In some of the technical chapters, I even provide code samples. Since PaaS works with many programming languages, I provided simple programming samples in various programming languages including PHP, Ruby, Node.js, Java, and Objective-C. We do not go deep in any one language, but rather stay high level on various ones in hopes that you are familiar with one or two and can read through the others.
If you are an architect or technical manager, or are simply new to PaaS, the first three chapters are very important to understand the context for which PaaS has entered the technical landscape. These chapters explain what the cloud is ().
If you already know about the history of PaaS or have used a PaaS, you can skim through the first three chapters and dig in for the next three chapters around Chapters . These chapters are the heart of this book, providing real life tools, techniques, and programming patterns that will help you stay away from the biggest pitfalls of PaaS and not waste any time on programming anti-patterns.
is an important chapter for everyone to understand. Services like database and caching services or email services contain some of the biggest gotchas in the PaaS world. If you are not careful, this is the place you can fail most quickly when adopting PaaS.
The next two chapters go back to a higher level of understanding. In , the discussion centers around where PaaS is going, some industry trends, and thoughts around Open Source movements in the PaaS world.
The last chapter is a great place to reference any technologies available around PaaS. should have a bookmark sticking out of it, because you will be flipping to it to find ideas for service providers and technologies of all types (PaaS, IaaS, SaaS, and helpful programming libraries).
The following typographical conventions are used in this book:
Indicates new terms, URLs, email addresses, filenames, and file extensions.
Constant widthUsed for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.
Constant width boldShows commands or other text that should be typed literally by the user.
Constant width italicShows text that should be replaced with user-supplied values or by values determined by context.
This icon signifies a tip, suggestion, or general note.
This icon indicates a warning or caution.
Supplemental material (code examples, exercises, etc.) is available for download at http://examples.oreilly.com/9781449334901-files/.
This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless youre reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from OReilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your products documentation does require permission.
Font size:
Interval:
Bookmark:
Similar books «Programming for PaaS»
Look at similar books to Programming for PaaS. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Programming for PaaS and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.