I talk a lot about containerd. I write blog posts about it, speak at conferences about it, give introductory presentations internally at IBM about it and tweet (maybe too much) about it. Due to my role at IBM, I’ve helped IBM’s public cloud Kubernetes service, IKS, start a migration to use containerd as the CRI runtime in recent releases and similarly helped IBM Cloud Private (our on-premises cloud offering) offer containerd as a tech preview in the past two releases.

Viewers are streaming gigabytes of content every day than before. Their expectations of viewing endless high-quality content, anytime – anywhere and on any screen size and device is driving business for media companies. As a matter of fact, PwC anticipates revenue from the Media & Entertainment will reach an estimated $2.2 trillion by 2021. In addition, we will have 5G wireless networks in 2019 that would allow access and streaming of content at supersonic speeds across geographies.

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.

This blog describes how Rancher and its managed kubernetes clusters can be affected by the recent announcement detailing the vulnerabilities of the proxying external IPs and dashboard.

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.

Learn how to create a hybrid Kubernetes registry for any application deployed on any cluster managed by Rancher and JFrog Artifactory.

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.