Nextcloud is an open source, self-hosted file share and communication system. You might even consider it a platform, in the sense that apps run on top of Nexcloud and it provides a variety of features beyond file handling, including calendar/contacts, project management, communication, and more.

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.

Amazon RDS allows you to store your application data in databases without having to actually manage the servers the databases are hosted on. It also allows you to easily set up read replicas and take snapshots of your database. However, since it’s a managed service, you have less visibility with traditional monitoring tools. As such, it becomes even more important to take advantage of the available monitoring tools in AWS.

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 the unintended side-effects of the public cloud is the enablement of a platform-agnostic cloud architecture. This means that it’s now easier than ever to mix offerings from multiple vendors (cloud vendors in this case) to form a single application or service-based solution. There is one gotcha, however: log management.

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.

Last month OpsRamp delivered our Winter release, which introduced several innovations for digital operations management, including: Impact Visibility and Service Context, AIOps for Proactive IT Operations, Cloud Native Monitoring and Event Management

AWS introduced Lambda Layers at re:invent 2018 as a way to share code and data between functions within and across different accounts. It’s a useful tool and something many AWS customers have been asking for. However, since we already have numerous ways of sharing code, including package managers such as NPM, when should we use Layers instead?