Clustrix announced its nResiliency feature which ensures that the database, and hence the application, remains available in the event of multiple simultaneous server or instance failures.
Available now, nResiliency offers confidence that valuable data is safe and continuously available should two or even more servers (nodes) fail at the same time. Companies can now decide on the maximum number of nodes that could potentially fail in the cluster without losing any data, then ClustrixDB automatically generates the number of data replicas necessary to successfully recover, in the event of multi-node failure.
“Too many companies rely on databases for OLTP applications that are susceptible to even single-node failure,” said Mike Azevedo, CEO, Clustrix. “By offering protection against multi-node failure, we’re offering peace of mind through an easy-to-use feature that would otherwise require IT resources that most companies don’t have and can’t afford. This is critically important for larger scale applications that typically service millions of users like in e-commerce, gaming, adtech and social.”
ClustrixDB was developed to address MySQL’s scale limitations, but its architecture is distinct from other MySQL replacements in that it is designed to “scale out” both writes and reads by adding server nodes. This enables it to scale linearly to the point where there are almost no limits to the number of simultaneous transactions it can handle, with practically imperceptible latency to the end user.
Scale-out ability, combined with the new nResiliency protection against multi-node failure, means that companies can now easily scale to the demands placed on their application by millions of concurrent users. E-commerce sites facing holiday shopping traffic; gaming companies launching a new title; consumer web services and social applications can now all freely match database capacity to demand. Easily add scale when you need it, and then scale-back when you don’t, only paying for the servers you need.
ClustrixDB’s new nResiliency feature provides the ability to define the number of servers in the cluster that can become unavailable simultaneously while ensuring continuous database availability: it is easily configurable according to data sensitivity and criticality.
For example, users may:
- Set MAX_FAILURES at a high number for their high-value data that are necessary to keep mission-critical applications running in the event of simultaneous failures
- Set MAX_FAILURES at a mid-range number for high volume data that are not required to have multiple levels of redundancy
- Set MAX_FAILURES at a low number for high-throughput, ‘fast-lane’ data which can be easily replaced
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.