Today, we’re excited to announce support for Google Cloud Platform. Now, you can manage your Google Compute Engine virtual machine instances using the same advanced scheduling options already available in Skeddly.

In the world of web applications, Web Frameworks (WF) existed for a very long time. Traditional WF existed in a world without the notion of microservices, let alone the notion of serverless. Many first-time serverless users use WF to ease the transition into the ecosystem, sometimes unaware of its effect on the performance. The following post focuses on potential cold start issues when using WF in the NodeJS ecosystem.

One of my former teammates approached me the other day (and by other day i mean like 3 months ago) and asked ‘Am I thinking about this right? Kubernetes is actually akin to the Linux Kernel. So Rancher and OpenShift are distributions of Kubernetes. And for a supported enterprise application I’m more likely to use a more enterprise focused distribution than a DIY distribution, yeah?’ To which I responded ‘Yep, you hit the nail on the head’.

Today’s applications are marvels of distributed systems development. Each function or service that makes up an application may be executing on a different system, based upon a different system architecture, that is housed in a different geographical location, and written in a different computer language.

We are very excited to announce Calico v3.6. Here are some highlights from the release.

With AWS Lambda, deploying a new version of our application has never been simpler. However, we still need to take care of some underlying plumbing. Such as managing the configuration for our functions as well as other related resources such as API Gateway, CloudWatch log groups and IAM policies. Depending on the event sources you would like to use, you also need to provision the necessary EventSourceMapping in order to use Lambda with the likes of Kinesis Streams and SQS.

In the last couple of weeks StackStorm has published back-to-back releases. 2.10.2 is a traditional patch release from StackStorm, and you’ll find some of the highlights below. 2.10.3 and 2.9.3; however, are releases to address CVE-2019-9580. I want to thank Barak Tawily and Anna Tsibulskaya: the researchers who discovered and submitted a patch for the issue.