49
Solutions Overview

0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Embed Size (px)

Citation preview

Page 1: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Solutions Overview

Page 2: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Company OverviewMarket OverviewUnique Capabilities

AGENDA

Page 3: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Company Overview

Company Description Provider of in-memory data solutions for real-time access, analysis, and

distribution of high volumes of data in mission-critical environments Founded 1999 Privately Owned 200+ Employees

Page 4: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Company Overview

Milestones 1991 – Research begins in SK about future effects that RAM will have on

RDBMSs 1999 – Founded as a private in-memory RDBMS provider 2000 – Acquisition of first client: Hyundai 2005:

HDB, a hybrid DBMS with both memory and disk storage, is released Altibase acquires its 100th client and 500th deployment

2006 – Support for Spatial data (GEOMETRY Data Type) is added 2009 – Complex Events Processing (CEP) engine is developed 2013 – 2014:

Altibase acquires its 500th client and 4000th deployment Created partnerships will major companies: Dell; Intel; RedHat; Amazon Listed in Gartner’s Magic Quadrant for Operational DBMSs XDB, a DBMS optimized for in-memory only, is released

Page 5: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Company OverviewMarket OverviewUnique Capabilities

AGENDA

Page 6: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Changing World of Data

Data volumes explode: Big data: machine generated, continuous Less structure Making sense of unstructured data – databases on the TB scale for metadata

Massive parallelization: Commodity hardware & appliances: SANs, File Servers Software: Hadoop, Sharding etc..

OLTP and OLAP Both are necessary Performance is key

Page 7: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+

Interactivity/Speed

Availability

Scalability

CRM, ERP, SFA

POS, ATM

Custom Apps

Data Warehouse

Data Marts

Reporting Apps

Bandwidth

Customization

Scalability

Transactional vs. Analytical

Analytical Systems Transactional Systems

OLTP

Many users

Continuous updates

Tactical activity

Many short transactions

MB to TB of data

Mission critical

OLAP

Few users

Batch updates

Strategic planning

Long complex lookups

TB-PB of data

Important for Audits

Page 8: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Why Companies are turning to Altibase

Extremely Fast Response Times

Predictable and Consistent Response Times

Low Latency

Throughput Scalability

Real time Replication

Highly Available and Reliable

Persistent and Durable

Scalable on Commodity Platforms

Flexible Architecture for the Cloud

Standards Compliant

Rich Features & Rich Interfaces

Extensive Knowledge of and Commitment to In-memory Computing

Proven Technology

Page 9: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ How customers are using Altibase OCS (Online Charging System)

For simultaneously managing call access and customer balances in real time

Location Based Service For tracking the location of mobile users, and optionally other people or objects

IP Authentication For controlling Internet access and monitoring IP address assignment

APM (Application Performance Monitoring) Real-time status monitoring and control between standard web services

EES (Equipment Engineering Systems) For tracking defects and changing requirements in real time

Futures/Options Trading High and stable performance of processing large amounts of financial data

Page 10: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Example Applications Risk Management

Fraud Detection

Algorithmic Trading

Security Intelligence

Supply Chain Tracking

Telecom/Media Revenue Leakage

Service Delivery

Online Gaming

Inventory Forecasting

Transportations Operations Management

Software-as-a-Service

Real time Analytics

Profitability Analysis

Global Web Commerce

Sales Incentive Promotions Management

…. Many More

Page 11: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Company OverviewMarket OverviewUnique Capabilities

AGENDA

Page 12: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ In-Memory Database Technology Extremely Fast Transaction processing

Entire database resides in computer’s memory Powered by special algorithms and data

structures that are highly optimized for in-memory computing

Hundreds of thousands of transactions per second

Short and Predictable Response times Optimized for fastest transactional processing

with the shortest response times measured in microseconds

The improved response times fuel High Throughput.

Connectivity

In-Memory Database

Application

Query Processor

Storage Manager

DRAM

Transactional Log Checkpoint

Page 13: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Persistent In-Memory Database Persistent and Durable In-Memory DBMS

Full ACID support for all database transactions Atomicity Consistency Isolation Durability

Durability is achieved via use of transaction logs and checkpoint images Fully Recoverable

Multiple Durability Levels to control a balance between performance and durability No Durability Relaxed Durability Enhanced Durability Strict Durability

Connectivity

Application

Appl

icati

on

Transactional Log Checkpoint

Page 14: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Highly Available In-Memory Database

High Availability via built-in Replication Feature Log-based replication Adaptive Consistency

Synchronous Replication Asynchronous Replication

Non-Stop Service Architecture Active-Active Active-Standby

Near Standalone Replication Performance 90% in Active-Active 96% Active-Standby

Conflict Detection and Resolution Offline Replication

Application

Replication

Page 15: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Highly Scalable In-Memory Database

Horizontal Scalability via built-in Replication Feature Leveraging TCP/IP protocol Unlimited nodes Flexible Load Balancing Architecture

Vertical Scalability Scales On Commodity Platforms

Increased RAM Increased CPU

Dynamic sizing of In-Memory database with no system downtime via AutoExtend feature

Horizontal Scaling via Replication

Vertical Scaling (CPU, RAM)

Page 16: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Fastest In-Memory Database

Delete Insert Update Select0.00

200,000.00

400,000.00

600,000.00

800,000.00

1,000,000.00

1,200,000.00

1,400,000.00

1,600,000.00

1 Client2 Clients4 Clients8 Clients16 Clients32 Clients

1,417,164 TPS

1 Client 2 Clients 4 Clients 8 Clients 16 Clients 32 ClientsInsert 59,083 76,289 148,614 244,744 300,921 239,432Select 82,800 135,011 262,013 478,931 939,977 1,417,164Update 51,121 56,495 111,457 197,456 274,923 223,703Delete 68,307 84,259 150,542 259,645 300,004 232,461

IBM X3850, 24Core*Xeon [email protected], 32G MEM, SUSE Linux 11 SP 1 64Bit

Page 17: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ XDB – Optimized for In-Memory

Customizable application performance via Innovative and Rich Interfaces

Conventional client/server protocols TCP/IP and IPC for compatibility (1)

Direct Access Mode to completely eliminate network overhead (2)

Direct Access API Mode eliminates not only network overhead but also query processing overhead (3)

TCP/IP or IPC

Application

Appl

icati

on

Query Processor

Storage Manager

1

23

Transactional Log Checkpoint

Page 18: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ HDB – Superior Deployment Flexibility

Hybrid Architecture Combines the benefits of in-memory storage

and on-disk storage in a single relational database

Flexible Deployment Modes In-Memory Database Only On-Disk Database Only Hybrid Database (In-Memory + On-Disk)

Support for different workloads Real-time access to time critical Hot data Access to historical Cold data for analytics Complex transactions through integrated data Easy bidirectional data migration between Hot

and Cold data zones

Memory Data

In-Memory DBMS

Disk Data

BufferDisk DBMS

Disk Data

BufferMemory Data

Hybrid DBMS

Data Size

Speed

Page 19: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Standards Compliant In-Memory Database

Support for SQL Standards SQL:1999 Support for all common data types

Support Database Connectivity Standards ODBC (Microsoft 3.5.1 API) JDBC (Type 2 & 4) .NET Provider .NET Entity Framework OLE DB Embedded SQL CLI Perl DBD

Support for common communication protocols TCP/IP (IPv4 and IPv6) Unix Domain Socket IPC (Shared Memory)

Application

SQL ODBC JDBC

OLEDB.Net CLI

TCP/IP UDS IPC

Page 20: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Rich Set of Tools and Utilities Productivity and Administration

iSQL WareValley Orange (GUI) ReplicationManager (GUI) altiProfile Audit

ETL aExport iLoader

Interoperability and Migration MigrationCenter (GUI) oraAdapter

Application

iSQL

Orange

iLoader

aExport

altiProfile

Audit

WareValleyOrange

MigrationCenter

ReplicationManager

Page 21: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Open Platform In-Memory Database

Sun Solaris OS SPARC (64bit) Intel (64bit) Intel (32bit) – Client Only

HP HPUX PARISC (64bit) PARISC (32bit) – Client Only IA (64bit) IA (32bit) – Client Only

IBM AIX PowerPC (64bit) PowerPC (32-bit) – Client Only

Linux Intel (32bit) Intel (64bit)

Microsoft Windows Intel (32bit) Intel (64bit)

Page 22: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ In-Memory Database For The Cloud Altibase DBaaS (Database as a Service) enables:

Large Enterprise Customers for consolidation of data management Small/Medium Business Customers for outsourcing data management

Altibase DBaaS Benefits Provisioning

Ease of installation and configuration Amazon AMI on RHEL 6.4 OpenShift Gear Docker Container

High Performance Low Latency High Throughput Scalability

Ease of administration Elasticity Monitoring/Tuning Scalability

High Availability

Page 23: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ CEP – In-Memory Middleware

ALTIBASE HDBOr ALTIBASE XDB

ALTIBASE CEP

Data & Event Sources

Other Systems

Dropped Data

ALTIBASE CEP is an In-Memory Middleware for real-time processing, querying and analyzing data streams Data Characteristics Continuously flowing Too large to store Rapidly changing Time-sensitive

Extremely fast processing/filtering Continuous Query Processing (CQL)

Continuous execution of registered SQL queries Bounded ranges such as time windows or tuples Support for JOIN operations between streaming or

persistent data sets Publish-Subscriber Model Tight integration with ALTIBASE HDB and XDB

Data & Event Sources Transactional Systems Sensors Mobile Devices RFID ……….

Page 24: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ MAS – In-Memory Application Server

ALTIBASE MAS is an in-memory application server that combines the high-processing power of ALTIBASE XDB In-Memory Database with high-performance/high-scale Java Applications Optimized for in-memory computing Breakthrough Java application performance Enables Java applications to directly access to

ALTIBASE XDB In-Memory database via shared memory

Extreme Low Latency Greater scalability Runs on low-cost commodity hardware

ALTIBASE MAS

Checkpoint

ALTIBASE XDB

Java Application

Log

Shared Memory

Java Application

Page 25: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Hewlett-Packard OpenMCM

Page 26: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Problems

HP OpenMCM combines several types of monitoring systems, including Mission Critical Management, Application Process Monitoring, and Marketing Communication Management. As such, there was significant load on their monitoring servers, as well as exponentially growing data storage from these monitoring triggers. HP’s OpenMCM data processing requirement was a minimum of 30,000 transactions

per second (TPS). HP then tested another company’s in-memory processing technology which

produced better performance, but still fell short of the mark with only 20,000 TPS. TCO presented a massive hurdle. System memory limitations of an in-memory only

DBMS necessitated the purchase of a supplemental on-disk DBMS. Facing such pervasive impediments, HP could not implement key, additional

features, such as real-time analytics.

Page 27: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution

Born from ALTIBASE HDB’s core capabilities, speed, and limitless storage size, HP OpenMCM possesses robust features, including transactional performance of over 45K TPS and real-time analytics.

Because of the ability to support application loads with significantly less infrastructure, combined with a more cost effective licensing model, HP gained tremendously lower TCO.

Page 28: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Korea TelecomAbnormal Traffic Detection,

Analysis, and Control

Page 29: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ ProblemsIn order to maintain normal operating speeds in their network, KT used a set of applications that detected abnormal web traffic patterns (botnets & DDoS, malware), but as their user base increased, their disk-resident database was unable to keep up with the detection and logging associated with these services:

The old system configuration was unstable when high volumes of data were being processed. KT tried third-party solutions with the hopes of increasing overall performance. While their performance did increase, it still did not solve the issues, and also introduced instability that did not exist previously.

Upgrading the system for this type of expansion was difficult to implement and came with a hefty price tag. The total related costs were untenable.

Page 30: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution

Altibase HybridDB was a perfect fit for this specific set of problems: The ability to store, write, and retrieve data directly from memory

tables completely resolved all issues regarding lag due to detection and storage.

With an exponentially larger amount of speed available, KT was able to expand their applications to detect more kinds of threats in realtime.

HDB’s hybrid functionality also provided KT with the ability to store all of the gathered data permanently on disk, thus allowing them to use the historical data to increase preemptive detection based on past threats

Page 31: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Results KT was empowered with the ability to analyze data in real-time and react

accordingly. KT has profited from ALTIBASE HDB’s Hybrid architecture capitalizing on

in-memory storage for frequently accessed, current data while keeping less active, historical data on-disk.

KT’s reputation, bolstered by unilateral increases in customer satisfaction, loyalty, attraction and retention, is at an all-time high.

KT was able to move away from batch processing to real-time processing. ALITBASE HDB’s built-in replication feature and resultant Active-Standby

system allowed KT to deliver real-time and non-stop service. The number of active servers has been reduced to 4 from over 20

servers. System resource usage is down by 65%. By using the parallel architecture model, on-demand system expansion

became a reality.

Page 32: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Korea TelecomWired Telephone SMS Service

Page 33: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Problems

Built on an Oracle DBMS backend, KT’s Wired Telephone SMS Service was overrun with heavy traffic and stability issues. Transactions that were being processed per second were on the rise, and KT was in immediate need of replacing their legacy system with a significantly more robust solution. Three areas called for a rapid overhaul:

The current system configuration restricted usable data management and flow. Data loss occurred due to a lag in data migration when the active system failed.

With piling demands on the legacy system, and reactive attempts for resolutions, total cost of operating and maintaining the system became untenable.

KT’s system infrastructure found itself obsolete. Data management and interrelated processes were timeworn and further, associated hardware was becoming non-responsive.

Page 34: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution

KT implemented ALTIBASE HDB In-Memory DBMS into their Wired Telephone SMS Service in 2010. ALTIBASE HDB’s built-in support of Geographic Information System (GIS) functionalities became a natural augment to KT’s business.

ALTIBASE HDB enabled KT to utilize real-time detection and analysis while maintaining data integrity and high availability with the built-in data replication features.

Page 35: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Results The number of active servers was reduced from 30 to 4. System resource usage decreased by 73%. Active demand on the

system was reduced to 15% from 88%. KT’s IT spending was reduced significantly, while performance and

system availability was dramatically increased. KT’s reputation, bolstered by unilateral increases in customer

satisfaction, loyalty, attraction, and retention, is at an all-time high. KT’s processing speed was increased by over 600%. Before

deploying ALTIBASE HDB, processing speeds were 100 transactions per second. HDB was able to deliver over 600 TPS.

Even in the event of an unexpected server crash, KT provides uninterrupted service due to HDB’s built-in replication.

Page 36: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Ministry of Land, Transport, and Maritime Affairs’ National Spatial

Data Infrastructure

Page 37: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ ProblemsMLTM hosts several spatial information systems that are used by utility providers and other regional government departments. Fragmentation amongst these systems made integration and interconnectivity nearly impossible.

Lacking a single interface and corresponding integration, data access was constrained. As a result, the availability of essential, spatial information was unreliable.

Existing spatial data was duplicated across multiple systems to facilitate load balancing and application availability. This redundancy wasted storage space and created inconsistencies.

The independent systems, with their data overlap, drove operating expenses up without merit.

Page 38: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution

MLTM implemented ALITBASE HDB In-Memory DBMS to serve as a single system, integrating all spatial information systems into one.

The new system is accessed by various government agencies, including: the Ministry of Land, Transport, and Maritime Affairs; the Ministry of Public Administration and Security; regional and municipal government organizations; academic and research organizations; and the general public.

Information flows freely from the municipal and regional level down to districts, cities and provinces with ease.

Page 39: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Results MLTM was empowered with a systems architecture that has functionality similar

to Google Earth.

MLTM has the ability to tap into above-ground and underground data 24/7.

The system integrated 114 unique spatial information databases into one, leveraging non-redundant data of numerous government agencies across South Korea.

With the utility and ease of standardized Spatial SQL, MLTM advanced application development based on ALTIBASE HDB’s integrated system.

ALTIBASE HDB gave MLTM a comprehensive solution while slashing total cost of operation (TCO).

Page 40: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

NH BankAccounting Processing System

Page 41: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ ProblemsNH was spending inordinate amounts of excess capital supporting employee overtime and extended office hours, which resulted in inefficiencies.

The vast majority of NH’s branches were forced to prolong operating hours on a regular basis. The culprit was performance issues with its financial accounting information system.

The system could not effectively manage loading and processing large volumes of data feeds from its 20 application servers. Representative data feeds included tasks such as transaction processing, branch teller support, and error management.

The underperformance wasted valuable resources in the form of needless overtime pay while sparking an uncontrollable deterioration of company morale and overall productivity.

Page 42: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution

Realizing that the root cause of its performance failures stemmed from the pervasive limitations of its traditional on-disk DBMS, NH deployed ALTIBASE HDB’s In-Memory database to enhance its accounting processing system.

ALTIBASE HDB resolved NH’s large volume data management deficiencies, shortening office hours, increasing worker productivity and reducing spend.

The Hybrid architecture of HDB provided NH with the ability to process data in real-time while meeting governmental data storage requirements on disk.

Page 43: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Results NH reduced the operating hours of its 1,172 branches by an average of over 1

hour per day.

NH’s accounting processing system increased the performance of loading and processing data feeds from its 20 application servers by 500%.

NH’s accounting processing system seamlessly handles 3,000 TPS and over 50 million transactions per day.

NH provides customers with uninterrupted 24×7 service by leveraging ALTIBASE HDB’s HA feature that comes out-of-the-box and is deployed with ease.

NH no longer wastes capital on office overhead and overtime pay and has repositioned itself for high productivity.

Page 44: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

Samsung Securities

Page 45: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ ProblemsSamsung Securities had three critical areas that suffered from inadequate DBMS performance and reliability:

■ Customer Retention: Samsung Securities had pinpointed significant decreasing revenue as well as lost opportunity stemming directly from inadequate retention of global institutional investors. The problems were uncovered by identifying customer complaints indicating that they had lost transactions due to insufficient speed in their futures/options trading.

■ Customer Acquisition: Concurrently, Samsung Securities realized that new client acquisitions were facing hurdles that originated from the very same problems with speed.

■ Growth: Samsung Securities was not able to keep up with the increasing trading volumes in the futures/options market. Simply put, Samsung Securities was being limited by its speed.

Page 46: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Problems

Samsung Securities, prior to switching to ALTIBASE HDB, was utilizing a Sybase conventional on-disk DBMS. Growing trading volumes resulted in a significant increase in the number of database transactions.

This increase put a big burden on the abilities of their existing conventional on-disk DBMS which quickly became a bottleneck. Even attempts to use caching to improve performance did not solve the problems, as Samsung Securities could only process 750 trading orders per minute

In addition, the burden on system resources grew rapidly resulting in up to 60% CPU consumption to handle database transactions.

Page 47: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ Solution After Samsung Securities deployed ALTIBASE HDB using in-memory only mode to

replace the Sybase DBMS, there was a dramatic improvement in system performance.

ALTIBASE HDB in-memory DBMS enabled Samsung Securities to process 20,000 trading orders per minute with an average execution time of 3 milliseconds per order. While delivering extreme speed, ALTIBASE HDB utilized less than 20% of CPU, resulting in significantly low resource consumption.

ALTIBASE HDB, as a full-featured and standards-compliant DBMS, made it easy for Samsung Securities to migrate existing database objects and data. All existing Sybase tables and stored procedures were converted to ALTIBASE HDB by four technical staff within two months using familiar programming languages and standard SQL.

Page 48: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

+ High Availability (HA)

■ Samsung Securities implemented our native replication feature based on Active-Standby HA architecture. In this architecture, an up-to-date backup of the database is maintained on a second system. If the master server unexpectedly becomes unavailable, service immediately resumes from an identical database on an alternate server. This provides a nonstop operating environment with improved reliability and fault-tolerance. This architecture ensures that Samsung Securities’ mission-critical data remains uncompromised. Unplanned downtimes (system crash), malfunctions or planned downtimes are issue-free due to patches or upgrades to its DBMS.

Page 49: 0 61 125 0 37 73 000000 113 112 115 230 231 232 122 193 67 Gradation (0,61,128)) (0, 47, 101) Gradation (255, 255, 255) (230, 231, 232) 255 Gradation (0,61,

THANK YOU

[email protected]