GCP has introduced a new in-memory solution, and it is still in preview mode..

 GCP has introduced a new in-memory solution, and it is still in preview mode..

"VALKEY"

Valkey is an open-source, high-performance key-value data store developed as a community-driven project under the Linux Foundation, created in response to licensing changes in Redis. It supports a wide array of data structures, including strings, sets, hashes, and sorted sets, making it perfect for real-time applications such as caching, analytics, and message queues.

Additionally, Valkey provides advanced features like clustering, replication, and Lua scripting for extensibility, allowing developers to customize their operations. It is backed by major cloud platforms like Google Cloud and AWS, aiming to offer a robust, open-source alternative for in-memory databases.
Some key points.
==============
01. Open-source platform:- Valkey is a fully open-source key-value data store under the Linux Foundation.
02. Alternative to Redis:- It was developed as an alternative to Redis after changes in Redis’s licensing​.
03. Diverse data structure support: - Valkey supports strings, sets, hashes, and sorted sets, making it versatile for various tasks​.
04. High-performance: Valkey is designed for low-latency tasks like caching, real-time analytics, and message queues​.
05. Clustering and replication: It supports clustering for scalability and replication for high availability​.
06. Extensibility with Lua: Developers can extend its capabilities using Lua scripting for custom operations.
07. Module plugins: Valkey supports module plugins for additional functionality and custom data types​.
08. Cloud provider support: Major providers like Google Cloud and AWS back Valkey, ensuring strong industry support​.
09. Sustainable alternative: Valkey aims to provide a community-driven, open-source alternative for in-memory databases.
10. In-memory storage: It uses in-memory storage, allowing for fast data access and processing​.

Comments

Post a Comment

Popular posts from this blog

Creating Physical Standby using RMAN Duplicate Without Shutting down The Primary

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4 - Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 Goal  - Ref Metalink ID - 789370.1 The following note describes step-by-step procedure to create physical standby by using RMAN duplicate without shutting down the primary (Production) database. Database Name :- prim Primary db_unique_name :- prim standby db_unique_name :- stdby Primary Hostname :- raca.idc.oracle.com standby Hostname :- core1.idc.oracle.com Solution 1.Enable force logging. 2.Create SRL(standby redo logs). 3.Make proper changes in the parameter file of primary. 4.Backup the database that includes backup of datafiles, archivelogs and controlfile for standby and copy the backups to standby server. 5.Create the parameter file for standby, 6.Establish the connectivity from primary to standby. 7. Move backup to standby. 8 and 9. Start the standby instance. 10.U
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo
Read more

index rebuild candidates oracle

Steps... CREATE TABLE index_log (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  last_inspected DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     CLOB); ALTER TABLE index_log ADD CONSTRAINT pk_index_log PRIMARY KEY (owner,index_name); CREATE TABLE index_hist (  owner          VARCHAR2(30),  index_name     VARCHAR2(30),  inspected_date DATE,  leaf_blocks    NUMBER,     target_size    NUMBER,  idx_layout     VARCHAR2(4000)); ALTER TABLE index_hist ADD CONSTRAINT pk_index_hist PRIMARY KEY  (owner,index_name,inspected_date); CREATE OR REPLACE PACKAGE index_util AUTHID CURRENT_USER IS vMinBlks     CONSTANT POSITIVE := 1000; vScaleFactor CONSTANT NUMBER := 0.6; vTargetUse   CONSTANT POSITIVE := 90;  -- equates to pctfree 10  vHistRet     CONSTANT POSITIVE := 10;  -- (#) records to keep in index_hist  procedure inspect_schema (aSchemaName IN VARCHAR2);  procedure inspect_index (aIndexOwner IN VARCHAR2, aIndexName IN VARCHAR2, a
Read more