A Blueprint to Adopting a Serverless Ecosystem

A Blueprint to Adopting a Serverless Ecosystem

It seems pretty definite that ‘serverless ecosystems’ are here to stay and who can blame them? These newbies come with benefits such as tougher security, upgraded operational practices, faster market and innovation times, and radical ‘pay-as-you-go’ pricing options. At the moment, there’s lots of stuff out there...and a fair bit of confusion about what’s what. Let’s organize it.

Currently, ‘serverless’ is being used as an umbrella term for a number of architectures. Officially, serverless was born in November 2014 with the release of Amazon’s AWS Lambda. Defined as “an event-driven serverless computing platform”, AWS Lambda embodies the concept of function as a service (FaaS). Over time, FaaS is evolving into a more inclusive idea known as platform as a service (PaaS). The essential difference? FaaS is a self-contained system in which the service provider does it all whereas PaaS builds complex, scalable systems comprised of FaaS and other cloud services. Serverless systems on offer today include Amazon’s AWS Lamdba, Microsoft’s Azure, Google’s Cloud Platform, and IBM’s Bluemix/OpenWhisk.

ITTB has made it our business to know the ins and outs of serverless. We engage with you to choose the cloud services which best match your unique needs, including logging and monitoring. Our development process constructs the appropriate infrastructure to superbly support your system and ensures that the resulting code is of the highest quality and according to best practices. Nothing is deployed to the cloud until it is rigorously tested, tweaked, and tested some more—a challenging task but we’ve cracked it. Needless to say (but we’re going to anyway), ITTB is always on hand to answer your questions and keep you in the ‘your website’ loop.

If you’re interested in learning more, shoot us a message here.