Operations | Monitoring | ITSM | DevOps | Cloud

Database Partitioning: Types, Strategies, and When to Use Each

How database partitioning works in PostgreSQL and MySQL. Range, list, and hash partitioning with SQL examples and guidance on when to partition vs shard. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

White-Label Loyalty Platform Features Checklist

White-label loyalty platforms sound great on paper. You launch your own branded rewards program without building everything from scratch. No heavy dev work is required. Just plug it in and go. In reality, though, choosing the wrong platform can lock you into limited features, poor customization, and endless workarounds. If you are evaluating vendors right now, this checklist will help you focus on what actually matters. So, what features should a solid white label loyalty platform have?

AWS vs Google Cloud vs Azure for Cloud-Native and Kubernetes

Cloud adoption is no longer about “moving to the cloud.” It’s about building cloud-native platforms that are scalable, observable, automated, and Kubernetes-driven. This guide provides a deep comparison of with a focus on Kubernetes, platform engineering, DevOps, and modern workloads, aligned with standards pioneered by the Cloud Native Computing Foundation.

Database Sharding: How It Works and When You Actually Need It

How database sharding works, common strategies (hash, range, directory), shard key selection, and the operational cost of running a sharded database in production. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

When Technology Failures Become Securities Litigation Risks

When a company's systems crash or a breach hits, it often looks like lawsuits appear out of nowhere. The real issue is that even a single tech failure can shake customers, stall revenue, and erode investor confidence. Many businesses downplay risks they already know about, leaving shareholders feeling misled when problems explode publicly. That gap between internal awareness and external disclosure is exactly what opens the door to securities litigation, turning tech troubles into legal and financial fallout almost instantly.

Expert Insight: Why Local Internet Traffic Matters More Than You Think

Imagine sending a letter to your neighbour across the street, only for it to be routed through London or even Amsterdam before landing in their letterbox. This is effectively what happens to much of Scotland's internet traffic. Despite physical proximity between users, businesses and services, digital data is frequently sent on needlessly long journeys, often leaving the country before reaching its destination. This approach is inefficient, costly and poses questions about privacy, resilience and digital sovereignty.

Trello outage on February 19, 2026

On February 19, 2026, Trello users around the world began experiencing issues loading boards and accessing their workspaces. StatusGator received the first outage reports at 14:24 UTC and triggered an Early Warning Signal at 14:28 UTC. Trello did not officially acknowledge the incident until 15:08 UTC, after user reports had already subsided. This incident highlights how real time user reports and Early Warning Signals can identify widespread service degradation before providers confirm a problem.

Kubernetes Namespaces: What They Are, How They Work, And What They Don't Solve

Using Kubernetes to manage containerized applications has its fair share of challenges. One of those challenges is managing complexity. Using namespaces can help minimize that complexity. Yet, a common misconception is that using multiple namespaces in a single Kubernetes cluster can degrade performance. Another issue: Kubernetes namespaces can reduce visibility into costs. There’s more to it than that.

Identify untested code across every level of your codebase

As organizations scale their services and adopt AI-assisted coding, code changes are landing faster and in greater volume than ever before. While this powerful new practice is accelerating the pace of development, it is also increasing the likelihood that untested code may slip into repositories without detection. What makes this problem even worse is that most teams have no reliable way to know which code is covered by tests.