GigaOm has once again placed VMware Tanzu Service Mesh within the leader ring of its Radar Report on Service Mesh. This year Tanzu Service Mesh has been upgraded to the Outperformer label, moving closer to the center and marking its heightened recognition as an industry leader. This is not only a testament to our robust enterprise capabilities and broad support for various application platforms, public clouds, and runtime environments, but also a validation of our strategic approach.

Kubernetes, or K8s, is an open-source, portable, and scalable container orchestration platform. With K8s, you can reliably manage distributed systems for your applications, enabling declarative configuration and automatic deployment. Yet, K8s can be resource-intensive and costly, with a rather steep learning curve. But in 2019, a lighter, faster, and potentially more cost-effective alternative appeared: K3s. Still, K3s is not a magic wand that works for all Kubernetes deployments.

In our previous article about Database migrations we explained why you should treat your databases with the same respect as your application source code. Database migrations should be fully automated and handled in a similar manner to applications (including history, rollbacks, traceability etc).

As Kubernetes adoption surges across the industry, AWS EKS stands out as a robust solution that eases the journey from initial setup to efficient scaling. This fully managed Kubernetes service is revolutionizing how businesses handle containerized applications, offering agility, scalability, and resilience.

Autoscaling the resources and services in your Kubernetes cluster is essential if your system is going to meet variable workloads. You can’t rely on manual scaling to help the cluster handle unexpected load changes. While cluster autoscaling certainly allows for faster and more efficient deployment, the practice also reduces resource waste and helps decrease overall costs.

Getting your applications running on Kubernetes is one thing: keeping them up and running is another thing entirely. While the goal is to deploy applications that never fail, the reality is that applications often crash, terminate, or restart with little warning. Even before that point, applications can have less visible problems like memory leaks, network latency, and disconnections. To prevent applications from behaving unexpectedly, we need a way of continually monitoring them.

Docker’s power and versatility have cemented its place in developers’ and administrators’ toolkits. Along with this widespread adoption comes the critical need for effective logging in Docker containers. However, once you scale beyond a single container on a single machine, effectively capturing and working with logs from Docker presents a challenge. The native docker logs command quickly becomes inadequate, and you’ll need a more scalable solution.

Navigate Europe 2023 has come to an end, and we couldn’t be more grateful for everyone involved in this, from our sponsors, attendees, and most importantly, the Civo team. Whilst we have already announced the next event for next year in Austin, Texas, we want to spend some time reflecting on the amazing few days we’ve just had, and everything we took away from it.

Most modern infrastructure architectures are complex to deploy, involving many parts. Despite the benefits of automation, many teams still chose to configure their architecture manually, carried out by a deployment expert or, in some cases, teams of deployment engineers. Manual configurations open up the door for human error. While DevOps is very useful in developing and deploying software, using Git combined with CI/CD is useful beyond the world of software engineering.