How do you start? How should you build a plan for cloud migration for your entire portfolio? How will your organization be affected by these changes? This book, based on real-world cloud experiences by enterprise IT teams, seeks to provide the answers to these questions. Here, you’ll see what makes the cloud so compelling to enterprises; with which applications you should start your cloud journey; how your organization will change, and how skill sets will evolve; how to measure progress; how to think about security, compliance, and business buy-in; and how to exploit the ever-growing feature set that the cloud offers to gain strategic and competitive advantage.

An expert guide to selecting the right cloud service model for your business Cloud computing is all the rage, allowing for the delivery of computing and storage capacity to a diverse community of end-recipients. However, before you can decide on a cloud model, you need to determine what the ideal cloud service model is for your business. Helping you cut through all the haze, Architecting the Cloud is vendor neutral and guides you in making one of the most critical technology decisions that you will face: selecting the right cloud service model(s) based on a combination of both business and technology requirements. Guides corporations through key cloud design considerations Discusses the pros and cons of each cloud service model Highlights major design considerations in areas such as security, data privacy, logging, data storage, SLA monitoring, and more Clearly defines the services cloud providers offer for each service model and the cloud services IT must provide Arming you with the information you need to choose the right cloud service provider, Architecting the Cloud is a comprehensive guide covering everything you need to be aware of in selecting the right cloud service model for you.

Cloud native infrastructure is more than servers, network, and storage in the cloud—it is as much about operational hygiene as it is about elasticity and scalability. In this book, you’ll learn practices, patterns, and requirements for creating infrastructure that meets your needs, capable of managing the full life cycle of cloud native applications. Justin Garrison and Kris Nova reveal hard-earned lessons on architecting infrastructure from companies such as Google, Amazon, and Netflix. They draw inspiration from projects adopted by the Cloud Native Computing Foundation (CNCF), and provide examples of patterns seen in existing tools such as Kubernetes. With this book, you will: Understand why cloud native infrastructure is necessary to effectively run cloud native applications Use guidelines to decide when—and if—your business should adopt cloud native practices Learn patterns for deploying and managing infrastructure and applications Design tests to prove that your infrastructure works as intended, even in a variety of edge cases Learn how to secure infrastructure with policy as code

Despite many uncertainties in cloud computing, one truth is evident: costs will always tend to go up unless you’re actively engaged in the process. Whether you’re new to managing cloud spend or a seasoned pro, this book will clarify the often misunderstood workings of cloud billing fundamentals and provide expert strategies on creating a culture of cloud cost management in your organization. Drawing on real-world examples of successes and failures of large-scale cloud spenders, this book outlines a road map for building a culture of FinOps in your organization. Beginning with the fundamental concepts required to understand cloud billing concepts, you’ll learn how to enable an efficient and effective FinOps machine. Learn how the cloud works when it comes to financial management Set up a FinOps team and build a framework for making spend efficiency a priority Examine the anatomy of a cloud bill and learn how to manage it Get operational recipes for maximizing cloud efficiency Understand how to motivate engineering teams to take cost-saving actions Explore the FinOps lifecycle: Inform, Optimize, and Operate Learn the DNA of a highly functional cloud FinOps culture

"Product-Led Growth is about helping your customers experience the ongoing value your product provides. It is a critical step in successful product design and this book shows you how it's done." - Nir Eyal, Wall Street Journal Bestselling Author of "Hooked"

For many decades, IT infrastructure has provided the foundation for successful application deployment. Yet, general knowledge of infrastructures is still not widespread. Experience shows that software developers, system administrators, and project managers often have little knowledge of the big influence IT infrastructures have on the performance, availability and security of software applications. This book explains the concepts, history, and implementation of IT infrastructures. Although many of books can be found on individual infrastructure building blocks, this is the first book to describe all of them: datacenters, servers, networks, storage, virtualization, operating systems, and end user devices. Whether you need an introduction to infrastructure technologies, a refresher course, or a study guide for a computer science class, you will find that the presented building blocks and concepts provide a solid foundation for understanding the complexity of today's IT infrastructures.

If you want your startup to succeed, you need to understand why startups fail. “Whether you’re a first-time founder or looking to bring innovation into a corporate environment, Why Startups Fail is essential reading.”—Eric Ries, founder and CEO, LTSE, and New York Times bestselling author of The Lean Startup and The Startup Way Why do startups fail? That question caught Harvard Business School professor Tom Eisenmann by surprise when he realized he couldn’t answer it. So he launched a multiyear research project to find out. In Why Startups Fail, Eisenmann reveals his findings: six distinct patterns that account for the vast majority of startup failures. • Bad Bedfellows. Startup success is thought to rest largely on the founder’s talents and instincts. But the wrong team, investors, or partners can sink a venture just as quickly. • False Starts. In following the oft-cited advice to “fail fast” and to “launch before you’re ready,” founders risk wasting time and capital on the wrong solutions. • False Promises. Success with early adopters can be misleading and give founders unwarranted confidence to expand. • Speed Traps. Despite the pressure to “get big fast,” hypergrowth can spell disaster for even the most promising ventures. • Help Wanted. Rapidly scaling startups need lots of capital and talent, but they can make mistakes that leave them suddenly in short supply of both. • Cascading Miracles. Silicon Valley exhorts entrepreneurs to dream big. But the bigger the vision, the more things that can go wrong. Drawing on fascinating stories of ventures that failed to fulfill their early promise—from a home-furnishings retailer to a concierge dog-walking service, from a dating app to the inventor of a sophisticated social robot, from a fashion brand to a startup deploying a vast network of charging stations for electric vehicles—Eisenmann offers frameworks for detecting when a venture is vulnerable to these patterns, along with a wealth of strategies and tactics for avoiding them. A must-read for founders at any stage of their entrepreneurial journey, Why Startups Fail is not merely a guide to preventing failure but also a roadmap charting the path to startup success.