If you’ve built a serverless application or two, you’re probably familiar with the benefits of serverless architecture. You take advantage of already built, managed cloud services to handle standard application requirements like authentication, storage, compute, API gateways, and a long list of other infrastructure needs. You can spin up these resources in a matter of minutes and add your own specific business logic (usually as AWS Lambda function code).

DevOps is a very data-driven practice. After the right cultural changes take place within an organization to adopt DevOps, teams often rely heavily on monitoring, measurement, and continuous improvement to keep their projects on track. The best teams use KPIs to benchmark their performance and report up to management. However, there’s one metric your DevOps team might not be tracking: The cloud cost of their engineering decisions.

Cloud security is becoming one of the most pressing issues for many modern organizations as they move to the cloud. According to Cloudneeti’s 2019 Cloud Security Trends and Predictions report, by 2020, 41% of overall workloads will run in public clouds. Defending against unauthorized data exposure and securing data, applications, and infrastructures across the cloud environment is a must. It is the responsibility of every organization and should be taken seriously.

Deploying a basic Serverless application has been made easy with the abundance of frameworks out there. If you’re part of a small team or working on a relatively simple project, setting up a basic serverless CICD process is also pretty straightforward, since there is plenty of information on the subject. But when a Serverless application grows it can get very complex very fast.

At Logz.io we obsess over our customers and believe that our customers’ happiness is fundamental to our success as a company. With a growing number of customers all over the world, it’s important to us that we provide them with the best experience we possibly can. After all, we know we’re handling extremely important data and helping to keep mission-critical applications up and running.

With Serverless, it’s not the technology that’s hard, it’s understanding the language of a new culture and operational model. Serverless architecture has coined some new terms and, more confusingly, re-used a few older terms with new meanings. This glossary will clarify some of them.

Engineering stateless, high-availability cloud services comes with juuuuuuust a few challenges. Here’s how we (eventually) slayed the dragon.

One of the basic ingredients of any software is that before you deliver it to the end user you want to make sure that it works properly. The question is how we need to adapt our approach to testing to take account of the cloud-based, highly distributed nature of serverless architecture.

Like many startups, Stackery is a small team. For this reason, employees often need to go beyond their official job title to ensure everything gets done. As the Stackery product matures and gains more exposure, we’ve seen an increase in customer support inquiries and decided to further refine our customer support process through the creation of a customer support rotation that rotates amongst the software engineers on a weekly basis.