In the rapidly evolving financial services industry, the ability to innovate and deliver solutions quickly is crucial for staying competitive. As customer expectations grow and market dynamics shift, organizations need a robust database solution that not only supports their current operations but also empowers their development teams to be agile and responsive. MySQL Enterprise Edition […]

This blog outlines how MySQL Enterprise Edition enhances developer agility and performance in financial services.

RBL Bank, a leading private sector bank in India, has transformed its operations significantly since its inception as a cooperative bank in 1943. With a customer base of nearly 15 million and an extensive network of branches and ATMs, RBL Bank has continuously evolved to meet the demands of the digital banking landscape. Recently, the bank achieved a significant milestone of one trillion Indian rupees in deposits, […]

RBL Bank's strategic shift to MySQL Enterprise Edition fortified its cybersecurity defenses and streamlined operations, positioning the bank for continued growth and customer satisfaction in the competitive banking landscape. Read the blog.

As a managed cloud service, HeatWave MySQL periodically delivers system updates to keep the underlying hardware and software current, efficient, secure, and reliable. These updates, which may involve scheduled or unscheduled maintenance windows, sometimes requiring downtime to apply changes to the database or operating system.   During such maintenance activities, whether planned or unplanned, it […]

Customer contacts in HeatWave is a new feature that streamlines notification management by allowing you to assign specific contacts for all critical databases. With this capability, your Cloud Ops and DBA team can stay informed about operational issues, maintenance updates, and service announcements, ensuring timely responses.

With multi-threaded replication (MTR), a replica can commit transactions in the same order as the source, or not. This is determined by sysvar replica_preserve_commit_order (RPCO). As of MySQL v8.0.27 (released October 2021) it’s ON by default, but it was OFF by default for several years prior. In either case, it’s relatively new compared to 20+ years of single-threaded replication for which commit order was not an issue or option. But with MTR, it’s important to understand the affects of RPCO, especially with respect to the focus of this three-part series: replication lag.

I recently became aware of WeSQL. A MySQL-compatible database that separates compute and storage, using S3 as the storage layer. The product uses a columnar format by default which is significantly more space-efficient than InnoDB.

WeSQL introduces a new storage engine called SmartEngine using a LSM-tree-based structure that is ideal for a storage bucket implementation, and documentation shows the implementation of raft replication to combat latency concerns. There is a lot more information to review, the serverless architecture and WeScale, a database proxy and resource manager.

It was very easy to take it for an initial spin using a docker container and an AWS S3 bucket. I would really like to try CloudFlare R2 which implements the S3 API.

Under the covers there …

[…] installing & configuring Dolphie, let’s take a look into how we can “re-record not fadeaway” and avoid […]

LikeLike

After installing & configuring Dolphie, let’s take a look into how we can “re-record not fadeaway” and avoid using a VHS tape.

One of the coolest features is being able to go back in time with Dolphie and analyze what was happening at a specific moment.

This feature requires recording so we can replay.

Setting Dolphie up for recording mode.

I’m really just going to share the links to the the github site and organize my steps so someone else might want to rinse’n’repeat or “replay”. I’m just a mere messenger.

It works via the Daemon mode. …