The following blog post covers functions-as-a-service and serverless computing. Before we dive into functions, let us take a brief walk through the history…
It’s no secret that digital transformation has been driven by evolution in software. Software has progressively enabled levels of abstraction, from physical servers to virtual machines to containers to functions, thereby increasing the focus more-and-more on the code to be written and less-and-less on the infrastructure to be implemented. The figure below highlights this trend.
Physical servers offer high performance but provide the least flexibility for consolidation of workloads. Bare metal servers cannot decouple your applications from your underlying hardware — your organization’s email system and payroll processing application deployed on a single server can affect each other’s performance and won’t generally be deployed together. The advent of VMware’s server virtualization product in 2001, followed by Xen and KVM hypervisors, enabled bare-metal resources to be abstracted into multiple operating system instances. Virtual machines (VMs) allowed you to decouple multiple workloads from a physical machine, thereby decreasing the concern for infrastructure implementation. Read the complete article here
For regular information become a member in the Developer Partner Community please register here.