It’s the beginning of a new year and when it comes to computing, going serverless is the resolution of many engineering teams. At Stackery, this excites us because we know how significant the positive impacts of serverless are and will be. So much, in fact, that we’re already thinking about its applications for next year and beyond.

Pharmaceutical companies are witnessing a shift in the way they function where innovative products, beyond the pill concepts, automated machine systems, etc. are defining new boundaries. Eroom’s law acknowledges the fact which states the cost and time taken to develop a new drug almost doubles every nine years.

As the CEO of Stackery, I have had a unique, inside view of serverless since we launched in 2016. I get to work alongside the world’s leading serverless experts, our customers, and our partners and learn from their discoveries. It’s a new year: the perfect time to take stock of professional progress, accomplishments, and goals.

Multi-cloud is a cloud computing strategy that uses two or more different cloud services. This can be a combination of Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), or Infrastructure-as-a-Service (IaaS) solutions running in a public or private cloud environment. Multi-cloud offers a number of benefits including greater reliability and availability, less vendor lock-in, and potentially lower costs.

Already have a monitoring service with your current host? Does your plan include Amazon CloudWatch, Azure Monitor or another proprietary monitoring tool? You might want to check the fine print. These services often provide internal web monitoring only. While they may check HTTP availability from locations outside their network, HTTP checks alone are not sufficient.

If you missed the first 2 tips, go back and read 5 Tips to Avoid Deadlocks in Amazon RDS (Part 1), and then come back for the last 3 tips on deadlock avoidance. Once again, I want to re-emphasize that RDS is not actually capable of creating deadlocks — it merely reports them from the underlying database engine.

Last week, I wrote A Beginner’s Guide to Deadlocks in Amazon RDS. This week, I’d like to lay out my 10 years of experience about how to avoid deadlocks altogether. Often times, this will be out of the hands of operations people, but you can still move for dev changes based on issues in production. The more knowledgeable you are about deadlocks in general, the more they will lean on you as a resource with wisdom, not a totalitarian barking rules.

Sometimes it's necessary to run a maintenance API script in your LogicMonitor portal. For example, I move decommissioned devices into a specific folder because I no longer want to receive any alerts on these devices. An API script helps automate the process by running once a day to disable alerts on any new devices added to this folder.

One difficult task for the AWS account administrator is to keep track of used and unused resources. That’s why we’re adding more actions to help track down unused resources. Today, we’re happy to announce a new action: Delete Unused Elastic IP Addresses.