We use cookies and similar technologies to improve your experience, analyze site traffic, and personalize content. By clicking "Accept All", you consent to our use of cookies. You can manage your preferences or learn more in our Privacy Policy.
Privacy & Cookie Settings
We respect your privacy and give you control over your data. Choose which cookies you want to allow:
These cookies are necessary for the website to function and cannot be disabled. They are set in response to actions made by you such as setting your privacy preferences, logging in, or filling in forms.
These cookies help us understand how visitors interact with our website by collecting and reporting information anonymously. This helps us improve our services.
Providers: Google Analytics, Plausible Analytics (privacy-friendly)
These cookies are used to track visitors across websites to display relevant advertisements and measure campaign effectiveness.
Providers: LinkedIn, Twitter/X, Reddit
These cookies enable the website to remember choices you make (such as your language preference or region) to provide enhanced, more personalized features.
Your Privacy Rights
Right to Access: You can request a copy of your personal data
Right to Deletion: You can request deletion of your data
Right to Object: You can object to processing of your data
Right to Portability: You can request your data in a portable format
It is May 2017. The container wars are raging. We benchmark Kubernetes 1.6 against Docker Swarm Mode to see which orchestrator offers the best balance of sanity, performance, and persistence on Norwegian infrastructure.
We compare Kubernetes 1.6 and Docker Swarm Mode for production workloads. Discover why underlying KVM infrastructure and NVMe storage are critical for container performance in the looming GDPR era.
Monoliths are safe; microservices are a distributed systems minefield. We explore battle-tested patterns (API Gateways, Service Discovery) to maintain sanity, leveraging KVM isolation and NVMe storage to combat latency in the Norwegian ecosystem.
Kubernetes networking isn't magic—it's complex Linux routing. We dive into the CNI chaos, overlay network latency, and why your choice of underlying KVM infrastructure in Norway matters for production workloads.
With the EU-US Privacy Shield barely two weeks old, relying solely on US-based hyperscalers is a gamble. Here is a pragmatic, code-heavy guide to building a resilient hybrid infrastructure using KVM, Nginx, and local Norwegian NVMe storage.
Monoliths are safe; distributed systems are chaotic. We explore the 2016 microservices landscape, from Service Discovery with Consul to handling NIX latency, and why fast I/O is non-negotiable.
We benchmark the complexity and performance of Kubernetes 1.2 against Docker Swarm and Mesos. Discover why raw infrastructure latency matters more than your orchestration tool choice for Nordic deployments.
A battle-hardened look at how Kubernetes handles pod-to-pod communication. We dissect the specific challenges of CNI plugins like Flannel and Calico, debug MTU mismatches, and explain why raw underlying hardware performance is critical for overlay networks.
It is 2016, and the monolith is dying. Learn how to deploy scalable microservices using Docker 1.10, Nginx, and Consul without drowning in complexity. We cover the architecture, the config, and why hardware selection is the silent killer of distributed systems.
Moving from a monolith to microservices introduces a new enemy: network latency. We explore the Nginx gateway pattern, service discovery with Consul, and why the recent Safe Harbor ruling makes hosting data in Norway critical for DevOps teams in 2016.
Kubernetes 1.1 has brought massive changes to networking with the new iptables proxy mode. We dive deep into CNI, Flannel configuration, and why the recent Safe Harbor invalidation makes running your own K8s cluster in Norway a smart move.
Kubernetes 1.1 has stabilized, but the flat networking model remains a black box for many. We dissect Flannel, iptables, and the hardware requirements needed to keep latency low in production.
Docker 1.9 just changed the game, but managing containers at scale is still a battlefield. We pit Kubernetes 1.1 against Swarm and Mesos to find the best stack for Norwegian infrastructure post-Safe Harbor.
Managing containers across multiple nodes is the new infrastructure nightmare. We break down the current state of Docker Swarm, Kubernetes 1.0, and Mesos, and why your underlying hardware determines who wins.
Docker is great, but running it in production is a battlefield. We benchmark Kubernetes v1.0, Docker Swarm, and Mesos on high-performance KVM slices to see which orchestrator actually survives real-world traffic.
Google's Kubernetes is changing how we orchestrate Docker containers, but the networking model is a headache for traditional sysadmins. We analyze the 'One IP Per Pod' model, configure Flannel manually, and explain why your kernel version matters.
Docker is standardizing builds, but production deployment remains the Wild West. We compare Mesos, the rising Kubernetes beta, and CoreOS Fleet to see which orchestrator deserves your root access.
It is late 2014 and Docker is eating the world. But running containers in production without hardening is negligence. We dissect LXC isolation, kernel exploits, and why KVM is your safety net.
Docker 1.0 has just landed, changing the conversation around virtualization. We compare the emerging container tools against battle-tested LXC and OpenVZ, and explain why KVM is the only sane foundation for your stack in 2014.
It is April 2014, and Docker is changing how we deploy. But networking containers across multiple hosts remains a nightmare of NAT and port mapping. We explore manual bridging, Open vSwitch, and how to architect high-availability clusters on CoolVDS KVM instances.