Serverless computing is gaining steam, so you're bound to wonder what makes it better than other cloud-based back-end models. It's not like serverless doesn't use servers at all - it does, but the developer is not responsible for handling them. Today, you can outsource this to a cloud vendor and focus on mission-critical activities like building new features.

Why should you care about serverless architecture when the industry is buzzing with new approaches all the time? There are a couple of reasons why the serverless framework is a serious disruptor in software development. Serverless quickly delivers direct business value.

A serverless architecture opens the door for IT teams to build and run applications and services without having to manage any of the underlying infrastructure. Sounds like a dream, doesn’t it?

Software developers are often faced with the challenging task of managing large datasets in real-time. Modern apps often require some serious big data processing and many of them (like Spotify or Zalando, for example) use Apache Flink to get the job done.

Choosing the right tools is one of the most common challenges that DevOps engineers face in their daily work. In today's entrance, we will focus on comparing the two most popular infrastructure management tools on AWS – the native CloudFormation and the open-source Terraform.

Today’s blog post demonstrates the most efficient way of iterating over a huge dataset when every record needs to be updated within a restricted time frame. This requirement might be applied when you rely on calls to an external service and the number of requests per day is capped, or when you’re careful about the number of resources you use in order to prevent a “denial service attack” upon yourself.