If you have anything to do with the world of cloud computing or even programming for that matter, then I’m sure you’ve heard of different terms being tossed around such as “serverless computing” or “containers,” and even “monolithic architectures.” A lot of people who understand such computing methods can have a bad habit of using these terms without leaving any explanation as to what they are.

There’s no sure-fire way to tell whether or not serverless tech is going to grow or even be around next year. Every post-apocalyptic movie has thought me that technology is the first thing to go after a catastrophic event happens. And if that happens we’ll have to return to some ancient tech like ** knock on wood ** containers.

In 2008, Netflix was struck by a disaster. A fast-growing global streaming service was well on its way to transform the entertainment industry when the management faced a problem exposed by a data center failure. Even though it was a single issue, it shut the entire service down, depriving the company of millions in profits and effectively ending the shipments of DVDs (they were still a thing in 2008).

I’ve spent a lot of time with the development community over the years but every time I get to talk to people in the serverless community I’m constantly surprised by the passion and the general excitement over this technology. Below is one of the latest of said topics and I wanted to share it with you.

Serverless has become something of a buzzword lately - but it’s much more than a trend. Its benefits have gained the attention of professionals and amateurs in the tech industry, mainly due to how much cloud vendors have raved about the design. For mid-sized ventures, the idea of serverless is exceptionally appealing, for those looking for budget-friendly, but useful pieces of technology. It’s genuinely breaking the ground and is sure to make even more moves in the tech industry.

Now I’m sure this is not the case for everyone but for me personally, I like watching video tutorials on subjects that I need help with. I spent a good amount of time searching for these tutorials and while there might be a lot more of them out there I believe these are some of the best and easiest tutorials to follow but nevertheless, I’d like to keep this list updated so if you have any suggestions please let me know.

If you have anything to do with the world of cloud computing or even programming for that matter, then I’m sure you’ve heard of different terms being tossed around such as “serverless computing” or “containers,” and even “monolithic architectures.” A lot of people who understand such computing methods can have a bad habit of using these terms without leaving any explanation as to what they are.

With serverless computing, our daily tasks and routines are much more comfortable than they used to be before. Serverless allows us to put our focus on the code itself without the need to worry about the configuration of the underlying compute resources or maintenance. Numerous cloud providers (AWS included) gives us a variety of previously managed services which we can combine and create a massively scalable and incredibly robust serverless microservices.

AWS API Gateway is a completely managed service that makes developers’ job much easier by allowing them to publish, create, monitor, maintain, and secure APIs at any scale. In today’s article, we’ll talk more about API Gateway What is it, why is it so important, as well as how it can help us with?

We are going to talk about an essential part of AWS Lambda called “AWS Step Functions.” What are Step Functions? Why are they important for AWS Lambda users? What are they used for, and what can we expect to get by using them? Bare with us, and discover more critical information on Step Functions throughout this article. We’ll begin with the explanation of what are Step Functions. AWS Step Functions service is the most recent service released by none other than Amazon Web Services.