Access your Pro+ Content below.
Serverless computing architecture, microservices boost cloud outlook
This article is part of the Modern Infrastructure issue of July/August 2017, Vol. 6, No. 7
With the current rate of innovation in cloud computing, the industry is loaded with acronyms and buzzwords that, on the surface, might be misleading or just plain confusing. You may have heard about people building applications using serverless computing platforms or designing software that runs on a microservices architecture. Even though these ideas sound like hype, the reality is that they're changing the way businesses build, deploy and operate applications. A serverless computing architecture is a way for developers to build applications without having to think about servers. It's simply a layer of abstraction that enables developers to focus on writing code while ignoring the concept of servers and traditional infrastructure. In 2014, Amazon released AWS Lambda, a service that enables developers to create cloud-based functions that run on an existing fleet of managed instances. AWS later released its API Gateway service, which can be used to provision a public endpoint to invoke Lambda functions over HTTP. Together, AWS ...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
As the hyper-converged market develops, container support, more flexible pricing schemes and other enhancements come to the enterprise.
Applications that are built on serverless computing and run on microservices change the way IT uses cloud. And AWS Lambda plays a key role in the shift.
IT support requires a great deal of perfunctory tasks and communications. You'll soon be able to hand off the routine to bot-based IT help desk tools and integrations.
Columns in this issue
The private cloud promised a flexible and scalable alternative to public clouds, but in many cases, the concept fails to deliver.
Just because you don't see the server doesn't mean it's not there. Serverless frameworks are superseding containers, but is the extra abstraction worth it?