Blog

In this post we will explore a new command in v7.0.1, tpm report. The purpose of tpm report is to provide easy access to all of the settings that pertain to a specific topic. Since Security is a high priority at Continuent, the current default (and only) topic is the Security stance. The tpm report command will evolve and grow over time. This first version is Continuent’s way of providing as much transparency about Tungsten Cluster Security as possible.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA version 6.1.17 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.

Scalability is necessary to keep your database from crumbling under increased traffic. A scalable database must be able to handle larger data sets and more queries per second (both read and write), and the architecture must support these higher workloads seamlessly and efficiently. This blog attempts to explain what sharding is versus the pod architecture that some of our customers employ.

When an application is a primary source of revenue for an organization, keeping Production operations going is critical. This blog discusses three things that can help prevent issues in Production. In fact, that’s why multiple environments exist - to make sure that the final act, delivered in Production, runs smoothly; read on to find out how to make sure your labor is not in vain!

At Continuent, we believe high-quality 24/7/365 Support is rare and invaluable. In today’s blog, I’d like to tell a short story about our support because it makes me really proud of my company. Our Support delivering effective solutions in an agile manner is just one of the many benefits of using Tungsten - and it’s cited as one of the main reasons our Customers stick with Continuent year after year.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA versions 7.0 are now available. This new major release includes the Tungsten RESTful API (API v2.0), enhanced security, monitoring, performance, management, new commands, a new and improved Dashboard, and new Dynamic Active/Active (DAA) topology. Tungsten v7.0 is the culmination of years of planning and work, and it lays the foundation for even more pinnacle developments. Read this blog to learn about the new v7 release!

Tungsten is the go-to replication and clustering solution for MySQL - powering real-world, geo-distributed business-critical applications. Sometimes we get asked by those who are not familiar with us, what we mean by “MySQL,” and this blog is meant to shed some light on this question.

One of the common misconceptions about Continuent is that because Tungsten does not have an open source license, we do not support open source. In fact, quite the opposite, in everything we do. The whole purpose of Tungsten Clustering is to empower and enable teams that build business-critical applications on open source databases.

This leads us to the subject of this blog: how Tungsten is designed for openness.

There are many options for databases, and many organizations use multiple different types for their various use cases. In this blog we explore the use case of a business-critical or mission-critical application that requires a performant, robust and reliable OLTP RDBMS, and a few reasons to stick with a native open source database for this use case.

Hop on-board and sail the San Francisco Bay with the Founder and CEO of Continuent, Eero Teerikorpi, as he zeros in on one of the reasons customers love Continuent’s 24/7/365 customer service: speed. Of course, speed isn’t everything - but when combined with highly experienced and available DBAs, SysAdmins and Architects - it’s hard to find better peace of mind about your business-critical databases.

This is the third post in a short series about Tungsten Clustering topologies. In this post we will highlight the key differences between Composite Active/Passive, Composite Active/Active (CAA), and the newly available Dynamic Active/Active topology. In short, DAA blends the simplicity of CAP with the automated continuous operations of CAA.

You’ve seen the recent news about AWS outages; enterprises have to think about where their physical AWS data centers are and treat them as a single point of failure. As such, enterprises running business-critical and mission-critical applications are accounting for geography of public cloud resources in their business-continuity plans. Learn about a solution for continuous operations for your MySQL database that’s a step above traditional MySQL Disaster Recovery (DR).