Cartoon illustration of a building surrounded with cloud.
Cartoon illustration of a farmer about to plough the land using cloud services.
Cartoon illustration of a hacker taking the sack of cloud payments.
Cartoon illustration of a van being operated using a computer.
Cartoon illustration of the animals performing in a music band.
Cartoon illustration of a cloud developer creating a building.
Cartoon illustration of a farmer looking worried about his spoiled plant due to unplanned costs.
Cartoon illustration of a person deploying a internet biz.
Cartoon illustration of an artificial intelligence, video processing, machine learning, and robotics.
Cartoon illustration of a person looking at a ladder connecting to the cloud.
Cartoon illustration of a person flying in a cloud air balloon.

A WORD TO THE NERD

GETTING YOUR HANDS CLOUDY

If you take one thing away from this book, it should be that I'm very bad at drawing fish and trains.

But if you have a second takeaway, I hope it's that the cloud isn't just some inscrutable thing for you to passively consume.

The cloud is meant for you to build on. Yes, you.

Democratizing Computing

There's a reason essentially every startup company for the last few years—no matter the field—has built its IT infrastructure in the cloud, often disrupting competitors with decades of established advantage. Many reasons, in fact.

We've covered most of the reasons in one chapter or another, but let's recap them:

  • Pay-as-you-go pricing lets people without a lot of money have access to world-class software services. If they build something successful that gets a lot of traffic, then the costs increase in parallel with their ability to pay.
  • Cloud services abstract away basic IT tasks, so most people don't have to worry about them anymore. Werner Vogels, the CTO of Amazon, calls this kind of work “undifferentiated heavy lifting.” That's a fancy way of saying hard work that doesn't need to be duplicated by every single company. Once Amazon or Microsoft gets a particular kind of database service right, there's no reason for every mom-and-pop company to build their own (worse) version. They can just use the cloud provider's. That helps the little company spend less time on grunt work and more time building the unique, special thing that's their reason to exist. Like Netflix's movie library or Lyft's ridesharing algorithm—just to name two startups that grew at hyperspeed through aggressive use of the cloud.
  • The cloud lets you collaborate from anywhere. Some of today's hottest tech companies are “fully remote”: they have no physical office, and everyone works from home and communicates over cloud services like the videoconferencing tool Zoom and the chat app Slack. That lets you hire the best talent wherever they live, not relying on the local want ads. It also insulates you from unexpected problems in the physical world. It's safe to say that without the option of cloud communications, the world would not have been able to impose such drastic quarantine measures during the 2020 coronavirus pandemic.

These reasons, and more, have helped cloud adoption explode over the past decade. As 2020 dawned, 91 percent of companies were building at least some portion of their software in the public cloud, spending more than $400 billion to do it. And there is plenty of innovation still to come.

Serverless

As cloud providers continue to refine their offerings, they're selling more high-level services that are simple and easy to use. You might not know what to do with a virtual machine, no matter how easy it is to rent. But you probably can think of a use for Amazon's Polly service, which turns written text into speech—an automated way to create audiobooks and phone greetings. These days, you can stitch an entire software application together using mostly cloud services and writing very little new code.

“Serverless,” a movement that has gained much prominence (and a bit of controversy) in the cloud engineering community over the past few years, tries to use cloud services whenever possible, writing new code only when absolutely necessary. Despite what the name implies, a serverless software application still runs on servers. (I'm not aware that there's any other way to run code!) But from the developer's perspective, the underlying servers are irrelevant: all they see is the cloud interface, so for them the experience appears seamless…and serverless. Whether the name catches on or not, the principles of cloud-first engineering developed by the serverless community are sure to play a big role in the next decade.

That's because analysts believe that the world will have jobs for 100 million software developers by 2030—and they will need simple tools that let them build quickly. Imagine writing code by giving conversational instructions to a virtual assistant (“Alexa, make me an inventory database”), which sends commands to a “serverless” software system in the cloud, which runs on virtual machines automated on physical servers mounted in three redundant data centers spread halfway across the country, each with their own security staff, maintenance crews, and disaster recovery protections. That's the future of abstraction, and it's closer than you think.

The Edge

Will all software eventually run in the cloud? Certainly not. Packets can only travel through the cables of the Internet at the speed of light, and so when you are talking to a cloud server halfway around the world, you'll experience some amount of lag time, known as latency. So some applications will always need to run on hardware that is physically close to the end user, not connected over the Internet. For example, algorithmic stockbrokers rely on nanoseconds of advantage to be first with a big trade, so they put their servers right in the same data center as the stock exchange—in the very next server rack if possible. (This is called colocation.)

Many industrial machines do not have reliable Internet connectivity, or they produce too much data to send it all to the cloud cost-effectively. These machines often process some of their data locally, right on the factory floor, before sending some or all of it to the cloud. We increasingly refer to local IoT devices that send some of their data to the cloud as edge computing. Edge devices are notoriously difficult to keep track of and keep updated, for reasons we've covered in the IoT chapter. But they're not going anywhere, so we just have to learn how to deal with them.

The Cloud and You

Even if you don't want to start a business, you're still living in the cloud—whether you like it or not, you don't have much choice at this point. It's up to you to be a responsible citizen.

  • Maintain your privacy: Stay aware of services that collect your data without your consent.
  • Stay vigilant over security: Use strong passwords and multifactor authentication.
  • Keep backups of your data: You never know when lightning will strike.

And maybe, once in a while, step back to appreciate this thing that exists at the intersection of the Internet and our imaginations. This great big, magical, dangerous, colorful thing called the cloud.

Happy building,

Forrest

Cartoon illustration of a person constructing a building.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.188.252.23