Access your Pro+ Content below.
A serverless architecture could live in your data center
This article is part of the Modern Infrastructure issue of July/August 2017, Vol. 6, No. 7
Have you figured out everything you need to know about managing and operating container environments already? How to host them in your production data centers at scale? Transform all your legacy apps into containerized versions? Train your developers to do agile DevOps, and turn your IT admins into cloud brokers? Not quite yet? I hate to tell you, but the IT world is already moving past containers. Now you need to look at the next big thing: serverless computing. I don't know who thought it was a good idea to label this latest application architecture trend serverless computing. Code is useless, after all, unless it runs on a computer. There has to be a server in there somewhere. I guess the idea was to imply that when you submit application functionality for execution without caring about servers, it feels completely serverless. In cloud infrastructure as a service, you don't have to own or manage your own physical infrastructure. With cloud serverless architecture, you also don't have to care about virtual machines, operating ...
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?