Altibase enhances data security via secure communication, audit SQL & standard integration method for 3rd party encryption solutions

How does Altibase enhance data security?

Aug. 29. 2018

Data security can only be achieved by a holistic approach. Altibase provides strict data security covering all aspects of our product with extreme speed of in-memory database. Representative data security related features are its secure communication support, Audit SQL support and standard integration method support for 3rd party encryption solutions. Altibase also provides various additional security related features such as policy based password management, IP access control, object privileges and the list goes on.

Secure Communication:

  • Altibase adopts SSL/TLS using symmetric-key algorithms to encrypt/decrypt data, and asymmetric cryptography to safely exchange the shared key and public/private key pair for authentication.
  • Altibase uses the TLS 1.0 protocol supported by the OpenSSL library.
  • Altibase supports server-only authentication and mutual authentication.
  • Altibase provides the JDBC and ODBC interfaces for SSL connection, which is currently
    supported only in Linux.

Audit SQL:

  • Auditing tracks specific statements or all statements being executed on the Altibase server in real time and records their information.
  • Auditing conditions can be configured with SQL statements.

Standard Integration Method for 3rd Party Encryption Solutions:

  • Altibase provides external procedure, function-based index and instead of trigger.
  • Altibase enables integration of all 3rd party encryption solutions.

Altibase – Downloading is Believing.

Altibase differs from Oracle buffer cache in that the latter can only store a very small subset of data and is useful for reads only

How does Altibase compare to Oracle’s database buffer cache?

Aug 23, 2018

Occasionally, we are asked why Altibase outperforms Oracle since Oracle uses a buffer cache to improve performance. Some say that the buffer cache resides in memory, and so it should perform equivalent to an in-memory database.

This is categorically false. While it is true that the buffer cache resides in memory and dramatically improves performance, it is absolutely not identical to an in-memory database. The buffer cache typically can only store a very small subset of data. Anytime a client requests data that does not currently exist in the buffer cache, it must fetch the data from the physical disk and load it into the buffer cache before it is read.

This corresponding disk read dramatically reduces performance. In addition, this data caching is really only useful for reads. There is no real performance improvement when it comes to inserts, updates or deletes. In contrast, an in-memory database dramatically improves the total performance of the database regardless of the type of the SQL query made.

Altibase is faster than Oracle buffer cache because Altibase accesses a record directly by an operating system providing native memory pointer, whereas Oracle accesses a record indirectly through a logical Row ID (RID). With an RID Oracle has to go through a buffer manager, a buffer page and a position of the record in the buffer page. The net result is much slower performance.

 

Altibase vs. Oracle’s Database Buffer Cache

Item

Altibase

Oracle Database Buffer Cache


Architecture

 4_How does Altibase In-Memory database compare to Oracle's database buffer cache-1-1  4_How does Altibase In-Memory database compare to Oracle's database buffer cache-1-2

INSERT

Speed

Faster

Slower

UPDATE

Speed

Faster

Slower

DELETE

Speed

Faster

Slower

SELECT

Speed

Faster

Slower

Data Access Method

Direct access by native memory pointer

Indirect access by logical Row ID

 

Altibase – Downloading is Believing.

 

Altibase can be used as a persistent cache and is open source. Thus, there is no need to purchase separate caching solutions

How does Altibase perform as a persistent cache?

Aug. 23. 2018

Altibase can be utilized as a persistent in-memory cache which eliminates common issues associated with commercial caching solutions.

The following case studies include related stories.

Caching is a good strategy to use when specific query results need to be returned quickly. However, using this method does not give full flexibility for increasing performance amongst all data and operations:

  • Caching is only useful for common read operations; any DML (INSERT, UPDATE, and DELETE) that is executed will run at low, disk-based speeds. When used in an in-memory only mode, Altibase stores all data in memory, so any query that is run on the data will perform at cached speeds, including DML.
  • Unlike many commercial caching solutions, Altibase does not lose data when shut down or restarted. Altibase adheres to full, real time ACID compliance that guarantees data durability. Altibase’s persistent cache is a default setting, and can recover all data without any issues.
  • Since Altibase combines an in-memory database and an on-disk database in a single unified database, strict durability is possible and so is complete data durability.
  • Altibase provides MOVE technology, allowing DBAs to decide which sets of data should be high-speed and which are designated for long-term storage.
  • Altibase is a single database solution that meets all needs in any use case. With persistent in-memory and on-disk in a single database, flexibility and data integrity are given. With Altibase, there is no need to purchase separate caching solutions.

Representative Use Cases That Can Take Advantage of Altibase’s Persistent Cache Solution?

Any business that needs high performance can take advantage of it instantly:

  • Risk Management
  • Fraud Detection
  • Security Intelligence
  • Supply Chain Tracking
  • Telecom/Media Revenue Leakage
  • Service Delivery
  • Online Gaming
  • Inventory Forecasting
  • Transportation Operation Management
  • Software-as-a-Service
  • Real time Analytics
  • Profitability Analysis
  • Global Web Commerce
  • Sales Incentive Promotions Management

Altibase – Downloading is Believing.

Altibase offers an automation tool, Migration Center, that easily migrates various data objects from Oracle to Altibase to ensure 100% data integrity and consistency

How does Altibase migrate data from legacy systems?

Aug 20, 2018

Altibase offers an automation tool: Migration Center. It migrates various kinds of data objects from sources to target databases and ensures 100% data integrity and consistency.

Migration Center

Migration Center is a database migration tool that copies compatible database objects and data from other databases to Altibase. Manual tasks of database migration are complicated, time-consuming and prone to human error. Migration Center helps users to process database migration with a few mouse clicks in the Graphic User Interface (GUI) mode. It also supports the execution of migration using a Command Line Interface (CLI) mode.

Internal Process of Migration Center

  • Define database source and target:
    • Source and target database IP addresses and ports
    • Source and target user ID, password, JDBC driver, character set encoding, etc.
  •  Define data objects to migrate:
    • Source and target data objects information: table, column, index, view, procedure, etc.
  • Define migration options:
    • Selection of options: Thread count, batch size, etc.
    • Selection of migration scope: User mode and table mode
    • Data type mapping
    • Tablespace mapping
    • Stored procedure converting
    • DDL Modification
  • Validate migration rules
  •  Execute migration via rules
  •  Review the report files
    •  RunReport4Summary.html: the summary report file that provides the overall result of migration
    • RunReport4Missing.html: the report file that provides the list of data objects which were not migrated properly
    • DbObj_Failed.sql: the list of failed SQL commands and the cause of each failure

Migration Center Advantages

  • Easy and simple migration from other DBMSs to Altibase
  • Flexible mapping of different types of data objects
  • Migration summary report to review the migration result
  • High performance parallel migration
  • Manual rule modification

Migration Center Specifications

Source Databases

  • Altibase 4.3.9 or high version
  • Oracle 9i ~ 11g
  • Timesten 7 ~ 11
  • SQL Server 2005 ~ 2012
  • MySQL 5.0 ~ 5.5
  • Informix 11.50
  • CUBRID: 8.4.1~9.3.5(ISO-8859-1, UTF-8 charset)

Target Database

  • Altibase 5.5.1 or higher version

GUI Tool

  • JRE : Sun or IBM Java 5 or higher
  • Processor: 800MHz Pentium III or better
  • Memory: 512MB or more
  • Disk: 150MB or more free space
  • Screen resolution: 1024 x 768 pixels or greater
  • OS graphic library

CLI Tool

  • JRE : Sun or IBM Java 5 or higher
  • Processor: 1 CPU or more
  • Memory: 512MB or more
  • Disk: 150MB or more free space

Altibase – Downloading is Believing. 

SK telecom with over 26 million subscribers utilizes Altibase as a front-end to Oracle for higher performance and lower TCO

A Telco With Over 26 Million Subscribers Utilizes Altibase as a Front End to Oracle for Higher Performance and Lower Database-Related TCO

The telco’s use case epitomizes Altibase’s compatibility with Oracle: Altibase can replace Oracle or can interoperate with Oracle when replacement of all Oracle databases is not feasible.

The cost savings are manifesting greatly as Altibase is now open source.

NEW YORKAug. 13, 2018 /PRNewswire/ — The telco is the largest mobile service provider in Korea with 26 million subscribers.

Before the telco chose to deploy Altibase, it had been adopting Oracle on a legacy mainframe-based IT infrastructure for its real time rating system. However, it identified the following limitations of its legacy DBMS:

  • Its billing service suffered from major delays as the number of subscribers grew substantially.
  • With growing demands on the legacy system, database-related TCO became progressively onerous.
  • The company was unable to detect and shut off service when prepaid balances were depleted.
  • The inability to accurately detect customer balances resulted in negative balances and uncollectible funds.

The company tested various databases and eventually chose Altibase. Altibase was used as a front-end to Oracle, which was used for hosting historical data with a view to enhancing the performance and lowering database-related TCO. The results are:

  • It has been able to precisely check and act on customer balances.
  • It was enabled to process customer usage on a per-second basis.
  • Revenue losses resulting from undetectable free usage and uncollected negative balances were eliminated.
  • It has the ability to efficiently integrate billing services for subscribers using multiple services.
  • Customers can have access to their balances in real time and without error.
  • It replaced an aging and expensive mainframe-based legacy system with an open UNIX platform, which resulted in lower TCO.
  • Most importantly, it was able to reduce its reliance on Oracle and to achieve higher performance with lower TCO.

Altibase is a hybrid database which can be utilized in a hybrid, in-memory only or on-disk only mode.

Learn more about Altibase at https://youtu.be/pooexk0glK8, and download its open source database at https://altibase.com.

Contact:
Paul Nahm
Chairman
40 Wall St. 28th Fl.
New York, NY 10005
1-888-837-7333 X901

CisionView original content with multimedia:http://www.prnewswire.com/news-releases/a-telco-with-over-26-million-subscribers-utilizes-altibase-as-a-front-end-to-oracle-for-higher-performance-and-lower-database-related-tco-300695383.html

SOURCE Altibase