Operations | Monitoring | ITSM | DevOps | Cloud

Cloud-native is an evolving architecture. Existing vendors will keep on evolving their offerings and different teams inside your organization should be able to use the tool that will support them better in delivering their desired outcome fast. By implementing a standard application layer, you enable teams to adopt what works best for them while the DevOps team can focus on adopting the infrastructure components they believe to be best to support their organization.

I recently returned from a birthday trip to Napa Valley and got to spend some time with the Shipa Team in Palo Alto during the trip. Grabbing a coffee on my trek back to San Francisco, I overheard someone talking about YAML at the coffee shop and I had to hold back my laugh. You usually do not hear folks talking about YAML out in the public but this is San Francisco. For many engineers, YAML is a way of life.

With our latest releases of Epinio, we’ve focused on making both the setup and developer experience much more streamlined. We’ve looked at where users are having issues and removed many of the roadblocks. This reduced footprint also allows for more customizability and easier long-term maintenance. If you are not familiar with Epinio, it is an application development engine for Kubernetes that lets you go from code to URL in a single step.

Do you need to manage hundreds of Kubernetes clusters, or are you just curious to know why you could potentially need more than two clusters, or do you want to see the magic behind it? You are in the right place because you’re about to learn everything there is to know about it.

Continuous Integration(CI) is a software development practice where developers frequently merge the code and the changes in a central repository. The important goals of continuous integration is to find and resolve the bugs more quicker, improve the software quality, and reduce the time taken to validate and release new software updates. Continuous Delivery(CD), which is done on the top of Continuous Integration and includes the practice of automating the entire software release process and builds.

Kubernetes has become the most widely adopted and popular container orchestrator and, with the help of CNCF and the surrounding community, its reach is increasing every day. The orchestrator currently boasts 140k+ members on its Slack and continues to grow in popularity.

Organizations rely more than ever on their engineering teams to get in front of their customers. Quickly delivering the latest functionalities to end-users in a reliable way can make or break a company these days. This need raises the pressure on engineering to deliver a scalable platform, rollout application updates faster, and manage applications efficiently once in production.

Kubernetes provides a set of primitives to run resilient, distributed applications. It takes care of scaling and automatic failover for your application and it provides deployment patterns and APIs that allow you to automate resource management and provision new workloads.

Containerization packages a software component and its environment, dependencies, and configuration into an isolated unit called a container. That makes it possible to deploy an application consistently across different computing environments, whether on-premises or on the cloud. The concept of containerization is more than a decade old.

In February we had our first online meetup of the year, 'Connecting and securing your microservices by using EnRoute.' Check it out on our YouTube channel if you missed it. Meanwhile, for Civo Shorts, David Flanagan of Pulumi explains why Civo is his service provider of choice for testing environments. Plus guides and tutorials on all things Cloud Native and Civo. Read on.