The short answer is: because that's where all of computing is going. For most industries, the days of buying a lot of a compute hardware, and maintaining it in a data center you own are pretty much over. Now there are some industries where this is slower to happen or may never happen because of regulations, particularly privacy ones, the must adhere to (healthcare, government, etc.) and there are other industries that are so conservative in their approaches and are very slow to adopt things like the cloud (like banks and finance in general).
For me personally, I really enjoy working in the cloud because it first my style of working. I can be very experimental. If I want to try a new approach, I can spin up whatever I need in the cloud, work with it for a little while and make quick decisions on whether to continue or just throw it away without having to worry about either generating a big bill I'm going to have to answer for or go through a lot of red tape and waiting to get the resources I need.
Tony recommends the following next steps:
Now cloud is required and will be more required in future due to high computing needs which cannot be managed by today home devices even though they have some high config.
Plus if you see we human have already decided to move forward with technology first and network is every technology communication nervous system simmilar to human nervous system.
Hence it has to grow with technological needs.
I will suggest courses like ccna and aws to get used to cloud and Internet technology if you are interested.
Naresh recommends the following next steps:
The public cloud is the biggest revolution in computing for decades, and involves a lot more than infrastructure! Cloud is a new way of working, rather than just a big set of servers in someone else's data centre.
One of the very important differences with the cloud is that everything can be treated as code: not just your application, or the tools and libraries that it uses, but also the underlying infrastructure. All of this can be constructed and managed as source code. This enables and provides incredible power to the cloud engineers and builders, but also means learning new disciplines and skills for working in a fully software-driven organisation.
Because everything can be done "as code", there is also much more automation that is possible, and far less boring operational work that needs to be done in managing a well-architected cloud environment. Unlike server engineers who spend a lot of their time doing repetitive tasks like capacity management and server patching, cloud engineers can build solutions that use extensive automation to do the equivalent tasks at scale, in a scripted way. Many of these "boring" tasks that are required in a non-cloud environment are catered for by the cloud provider when the solution is built in cloud, or are just not needed. Serverless code (for example AWS Lambda) doesn't even have a server to patch!
This all leads to a situation which is very satisfying for the cloud builders and engineers. There is a great deal of satisfaction from creating a large-scale technology solution much more quickly than the equivalent on-premise solution, that requires less effort to operate, and often costs less!
Cloud services provided by Amazon, Google and Microsoft are also iterating very fast, with new features coming out all the time, so there is always a lot of new and exciting stuff to learn.
Hyperscale public cloud is the way almost all technology will be delivered, now and in the future. It's by far the best part of the technology world to be involved in!
Sean recommends the following next steps: