No server will be the next step in the enterprise cloud computing journey as CIOs further abstract their infrastructure and operations in pursuit of greater business agility.
Infrastructure as a service is a boon to the enterprise, enabling CIOs to stop using physical servers or even shut down data centers while achieving new levels of business agility. However, the CIO needs to ask: What is the next big thing that can bring business results?
Scott Buchholz, head of emerging technology research at Deloitte, said the answer might be “serverless computing,” an emerging software architecture that dynamically allocates requests based on higher-order services such as databases or code functions. Calculation, storage, and memory.
According to a survey of global CIOs by Deloitte in 2018, 69% of IT leaders believe that “process automation and transformation” is the main focus of their digital agenda, and that no servers seem to fit well with CIO actions and actions. . Buchholz said, “We are getting closer and closer to the stage where IT departments no longer spend more time focusing on the details and mechanisms of technology, but more on business outcomes.”
Defining serverless computing
In a traditional cloud environment, the Infrastructure and Operations (I&O) team designs and configures the computing power, storage, and other tools provided by vendor partners.
No servers act on business logic to automate these tasks, as well as the patches, backups, security, and database management associated with those resources. This can reduce infrastructure and operations (I&O) management costs by 10%, while Buchholz says, enabling infrastructure and operations (I&O) leaders to focus on other tasks such as management APIs and service level agreements.
It should be noted that serverless computing still uses the server. However, Gartner analyst Ross Winser wrote in the 2018 Infrastructure and Operations (I&O) Trends Report that cloud computing vendors (rather than infrastructure and operations staff) are responsible for configuring and extending all of the underlying layers involved in the runtime environment. Resources.
In its 2019 Technology Trends report, Deloitte pointed out that the serverless goal is to automate and abstract the “NoOps” IT environment from the underlying infrastructure. As demand for operational resources decreases, CIOs can redistribute the remaining human resources to develop new capabilities to support the business.
“The increase in options means that we are changing the nature of the work,” says Buchholz. “More IT staff need to think like CIOs and business users, not NIB, NOBS, patches and other versions.”
According to a report released by Gartner in April 2018, despite the promotion and hype, no server is still in its infancy, and only 5% of organizations use it in some way, but researchers say that by 2020, more than 20 % of global enterprises will deploy without servers.
Serverless case study
For example, Nick Rockwell, chief technology officer of The New York Times, believes that serverless computing will be the next step in the cloud computing journey, leaving developers no longer worried about the servers on which their code runs.
The Times runs most of its enterprise applications and e-commerce platforms on AWS’s cloud platform, and the Google Cloud Platform (GCP) supports consumer-facing applications, including its websites, mobile apps and crossword puzzles. But Rockwell’s infrastructure team still needs hours to determine how many AWS and Google Cloud instances they need, how big they should be, and whether the instance needs additional input, output, or memory. They must configure each instance and patch and install the software on the operating system. In addition, they must carefully manage the dependencies associated with each application and figure out how each part of the application will scale.
It is also important to note that the pricing of IaaS and SaaS involves paying a fixed monthly or annual fee, regardless of whether or not the full capacity provided is used. “Resource utilization and optimization depend on the customer. If you rent 50 instances, if one instance is full and the other 49 are idle, this is a problem with improper use,” Rockwell said.
Serverless rendering does not solve the problem of idle instances. Conversely, when a predefined event occurs, code written specifically for the execution function is fired and the serverless platform performs the task. The customer does not need to tell the cloud provider how many times these functions will be triggered, and they only pay a small fee each time the function is executed. Rockwell says that no server can increase efficiency by 5 to 10 times. “No server makes the product both reliable and scalable,” Rockwell said. He said his company is working with Google Cloud to provide a serverless plan. In the long run, this will be a better, cheaper and more efficient way from an economic perspective.
Whether serverlessness is the next important issue in computing is still to be seen, but suppliers are actively seeking this emerging market opportunity.
No server is a risky business
Serverless applications are not suitable for companies that are cautious, especially for companies planning to deploy applications on a large scale. For example, migrating to no server usually requires rebuilding the application or exchanging major system components (such as databases). This may prove to be costly and damaging. For this reason, many people, including Rockwell, believe that serverless is safer for greenfield development programs.
According to Buchholz, monitoring and debugging are also challenging given the transient nature of serverlessness. For example, capturing data using a serverless model is more challenging because no machine can log in. But Buchholz said that a new generation of debugging and monitoring tools are emerging to help.
Another issue is vendor lock-in, and CIOs have been trying to move their business to the public cloud. Buchholz said there is currently no industry standard for serverlessness, which raises concerns for early adopters who are afraid of making mistakes.
No server prompt
As CIOs continue to advance the serverless program, Buchholz offers some advice for this.
The CIO needs to understand his data architecture. When you think about vendor options, understand the data and its processes, how to store and manage it, and how to integrate it with the front-end platform. And you need to ask yourself: What is the data for storage and operation? How is it handled? For example, those who manage unstructured data and large amounts of management data on a large scale may need something different from the transaction data that handles the relational model. The answers to these questions will help them determine which platform to use.
People should not be confused by new tools or new technologies. Serverless services are growing rapidly, so watch out for new tools that are cool and advertised. Organizations need to choose the technology that makes the most sense for achieving business outcomes.
Know your employees. The CIO needs to know his organization and employees. For example, what skills are needed at the moment? Do you need to refine or repurpose? Or hire a new worker? “If you don’t drive, it doesn’t make sense to have a Ferrari key,” Buchholz said.
Green. To avoid the risk of refactoring, many companies are adopting applications in the green world, and these applications can enter serverless. This is the code for new services that are not interdependent with countless other systems. Even small changes in older applications can have a huge chain reaction.
Send your message to us:
Post time: May-07-2019