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
Stop treating microservices like a silver bullet. A senior architect breaks down the network patterns, storage bottlenecks, and discovery mechanisms that actually work in production environments.
Microservices solved your monolith problems but introduced a networking nightmare. Here is how to implement Istio 1.0 without destroying your latency, specifically tailored for Norwegian infrastructure requirements.
Moving to microservices? Don't trade code complexity for operational insanity. We cover the API Gateway, Circuit Breakers, and why NVMe storage is non-negotiable for distributed systems in 2018.
Stop building distributed monoliths. We dissect practical microservices patterns, from container orchestration to Nginx tuning, specifically optimized for the Nordic infrastructure landscape in late 2018.
Moving from monolith to microservices introduces complexity. We explore battle-tested patterns like API Gateways, Circuit Breakers, and Service Discovery using NGINX and Consul, specifically tailored for the Norwegian hosting landscape.
Microservices solve scalability but introduce chaos. Learn how to implement Istio 1.0 for observability and mTLS without destroying your latency budgets, specifically tailored for Norwegian compliance standards.
Microservices solved your scaling problems but broke your observability. Here is a battle-tested guide to implementing Istio on Kubernetes without destroying your latency—specifically for the Norwegian infrastructure market.
Monolithic architectures are dying, but distributed systems introduce complexity that breaks cheap hosting. Here is a battle-tested guide to microservices patterns—Gateway, Discovery, and Circuit Breakers—tailored for the Nordic infrastructure landscape of 2018.
Microservices solve scale but introduce chaos. We explore implementing Istio on Kubernetes to handle observability and mTLS in a post-GDPR world, specifically tailored for Norwegian infrastructure constraints.
Microservices solve scaling issues but create networking nightmares. Learn how to implement Envoy and Istio (0.8) to regain control, enforce mTLS for GDPR, and why underlying hardware latency defines your mesh's success.
Breaking the monolith doesn't mean breaking your SLA. We explore proven architecture patterns—from API Gateways to Circuit Breakers—that keep distributed systems alive when network latency strikes.
It is June 2018. GDPR is live, but your API latency is killing user retention. Learn how to tune Nginx and Linux kernel parameters for raw performance on Norwegian infrastructure.
It is May 2018, and GDPR is hours away. We break down the essential microservices patterns you need to deploy on Norwegian infrastructure to maintain compliance and sub-millisecond latency.
Most load balancers break gRPC. We dissect why HTTP/2 multiplexing creates hot spots and how to fix it using the new NGINX 1.13.10 support and client-side strategies.
With the GDPR deadline looming, moving to microservices isn't just about code—it's about compliance and infrastructure survival. Here is the battle-tested roadmap for May 2018.
It is April 2018. Everyone is breaking monoliths, but few are handling the network latency and consistency trade-offs correctly. Here is a battle-tested architecture guide for Norwegian DevOps teams facing the GDPR deadline.
It is April 2018. The GDPR deadline is weeks away, and your microservices are choking on SSL handshakes. Here is the definitive guide to tuning NGINX gateways on KVM infrastructure, specifically for the Nordic market.
Moving from monolith to microservices isn't just about code—it's an infrastructure war. Learn the battle-tested patterns, Nginx configurations, and KVM strategies needed to keep latency low and uptime high in the Norwegian market.
Microservices are creating chaos in production environments. Learn how to implement a Service Mesh using Linkerd and Kubernetes 1.9 to regain observability and reliability, without sacrificing performance on Norwegian infrastructure.
Latency isn't just a network issue; it's a configuration failure. We dissect the kernel flags and Nginx directives required to handle 10k+ req/s without melting your CPU, specifically for Norwegian workloads.
Moving from a monolithic architecture to microservices is dangerous if you don't manage the complexity. We explore the API Gateway pattern, Service Discovery with Consul, and why low-latency infrastructure in Norway is critical for distributed systems.
Google and IBM just dropped Istio, changing the microservices game. We dive into the sidecar pattern, analyze the resource overhead for your VPS, and show you how to deploy this alpha release on CoolVDS infrastructure.
Move beyond the monolith without breaking production. We analyze the API Gateway pattern using Nginx and Consul, specifically tailored for Norwegian infrastructure requirements and GDPR preparation.
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.
Microservices solve development bottlenecks but create operational nightmares. Learn how to implement a Service Mesh with Linkerd to fix latency and observability before the GDPR deadline hits.
Microservices solved your code velocity problems but broke your network reliability. In this guide, we deploy Linkerd (v1.0) to handle service discovery and circuit breaking without polluting application code. Valid for March 2017.
The 'Serverless' buzzword is dominating 2017, but proprietary cloud functions come with cold starts and data residency risks. Here is how to architect a containerized, self-hosted FaaS alternative using Docker and Nginx on Norwegian infrastructure.
Microservices are trending, but they turn function calls into network calls. Here is how to architect for resilience using NGINX, Hystrix, and Consul without destroying your latency budgets in Oslo.
Monoliths were easy. Microservices are a distributed nightmare of latency and failures. Here is how to regain control using Linkerd and Kubernetes 1.5 without burning down your infrastructure.
Moving from monoliths to microservices introduces a new nightmare: service discovery and latency management. In this guide, we explore the emerging 'Service Mesh' concept using Linkerd to handle inter-service communication without rewriting your application code.