2019 has been a great year for cloud native technologies. This year we launched the world's first managed Kubernetes service back-ended by Rancher's k3s distribution, opened the #KUBE100 beta, and watched our users create some really neat things on our platform. To that end, we wanted to highlight some of our top posts from the wider Civo community, and posts that showcase the exciting state of play of the cloud native landscape at the moment.

Systemd is an initialization program that manages processes on Linux systems. It was designed to improve the performance of its predecessors by creating a dependency tree of system components, initializing them only when needed, and using as much parallelization as possible. With systemd becoming ubiquitous in Linux distributions, it’s crucial that you monitor the health and performance of both systemd and the components that it manages.

Open source components have become a basic building block in today’s software development process. It’s no surprise that 60%-80% of the codebase in 92% of modern applications is open source — they provide us with tried-and-true code that allows us to save time and focus on creating the secret sauce that will make our products the next great tech innovation.

Open-sourced by Google in 2014, Kubernetes is a container orchestrator. That means it enables users to deploy and manage apps distributed and deployed in containers. It takes care of scaling, self-healing, load-balancing, rolling updates, etc. The project is managed by the Cloud Native Computing Foundation (CNCF) along with multiple other open source projects, and you can find it here on GitHub.

The cloud native stack, also referred to as the new stack, is composed of the new cloud-independent counterparts of cloud managed services. As enterprises moved to the cloud, they started leveraging cloud managed services such as AWS’ DynamoDB or GCP’s BigQuery. Very convenient, these on-demand services significantly increased developer productivity. Being proprietary, they only work on that specific cloud, however — a significant drawback.

Transitioning from a Monolith to a Microservices architecture can take years to complete. The internet is full of stories of companies famously making this transformation. But how do you know if it’s right for your organization? Is your organization ready? In this article, we will look at five questions you can ask to see if you’ll benefit from a Microservices architecture. We’ll also discuss five challenges you will face during this transformation.

This blog focuses on Dashboard capabilities in Serverless360 and its use cases. Let us take a simple cab booking application scenario to have a better understanding of the Composite Application Dashboard.