This document provides an overview of an in-memory database company and its product capabilities. It discusses the company's history and growth, the changing data landscape driving demand for real-time analytics, and how the company's in-memory and hybrid database technologies provide extremely fast transaction processing, high availability, scalability, and flexibility for deploying on-premise or in the cloud. Example customer use cases and implementations are described to demonstrate how the database has helped organizations tackle challenges of high volume data processing and analytics.

1. Solutions Overview

2. Company Overview
Market Overview
Unique Capabilities
AGENDA

3. + 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

4. + 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

5. Company Overview
Market Overview
Unique Capabilities
AGENDA

6. + 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

7. +
Interactivity/Speed
Availability
Scalability
CRM, ERP, SFA
POS, ATM
Custom Apps
Data Warehouse
Data Marts
Reporting Apps
Bandwidth
Customization
Scalability
Transactional & Analytical
OLAP - Analytical Systems OLTP - Transactional Systems
Provides an enterprise with data to act on
Many users
Continuous updates
Tactical activity
Many short transactions
MB - TB of data
Mission critical
Operational Data for day-to-day
Provides an enterprise with answers
Few users
Batch updates
Strategic planning
Long complex lookups
TB - PB of data
Important for Audits
Analytical Data for decision making

8. +
Enterprises have traditionally needed separate data stores
for these technologies. However, as data sizes are growing,
the need for real-time transactional analytics has become a
reality
Databases need to provide applications
with the ability to process data very quickly
and reliably
Databases need to provide applications
with the ability to access large volumes of
data at one time
Transactional & Analytical
OLAP OLTP

9. + Why Companies are turning to Altibase
 Extensive knowledge of and
commitment to in-memory databases
 Extremely fast response times
 Predictable and consistent
 Low latency
 Throughput scalability
 Real time replication
 Persistent and durable
 Flexible architecture for cloud
deployment
 Scalable on commodity platforms
 SQL-92 compliant
 Rich features interfaces
 Proven technology
 Highly available and reliable
 Drivers for all DB connectivity standards
Hybrid (in-memory + on-disk) architecture removes the need to choose
between speed and size, transactional and analytical. One data source, one
platform, and one license provides developers a tool set that allows for one
central target for both high-speed and analytical platforms

10. + How customers are using Altibase
 OCS (Online Charging Systems)
Memory tablespaces enable simultaneous management of call access and customer balances in real
time while permanently storing data
 APM (Application Performance Monitoring)
Real-time status monitoring and control between standard web services becomes simple using the
speed of in-memory
 EES (Equipment Engineering Systems)
Tracking defects and changing requirements in real time while performing analytics increases yield by
opening up dynamic changes to manufacturing
 Location Based Service
Tracking and matching data is completed with ease in-memory. Permanent storage is crucial in the
public sector. HDB provides both.
 IP Authentication
Access routing, address assignment, and authentication are important security barriers. High speed and
huge storage is a must for proper operation.
 Futures/Options Trading
High and stable performance large amounts of financial data is how we were born

11. + 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

12. Company Overview
Market Overview
Unique Capabilities
AGENDA

13. + 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

14. + 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
Application
Transactional Log Checkpoint

15. + Highly Available In-Memory Database
 High Availability via built-in
Replication Feature
 Log-based, TCP/IP Replication
 Additional layer of Durability
 Adaptive Consistency
 Synchronous Replication
 Asynchronous Replication
 Nonstop 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

16. + 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)

17. + Fastest In-Memory Database
0.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
Delete Insert Update Select
1 Client
2 Clients
4 Clients
8 Clients
16 Clients
32 Clients
1,417,164 TPS
1 Client 2 Clients 4 Clients 8 Clients 16 Clients 32 Clients
Insert 59,083 76,289 148,614 244,744 300,921 239,432
Select 82,800 135,011 262,013 478,931 939,977 1,417,164
Update 51,121 56,495 111,457 197,456 274,923 223,703
Delete 68,307 84,259 150,542 259,645 300,004 232,461
IBM X3850, 24Core*Xeon E7-4807@1.87Ghz, 32G MEM, SUSE Linux 11 SP 1 64Bit

18. + 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
Application
Query Processor
Storage Manager
1
23
Transactional Log Checkpoint

19. + 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
Buffer
Disk DBMS
Disk Data
Buffer
Memory
Data
Hybrid DBMS
Data Size
Speed

20. + 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

21. + 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
WareValley
Orange
MigrationCenter
Replication
Manager

22. + 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)

23. + 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

24. + CEP – In-Memory Middleware
ALTIBASE HDB
Or
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 ……….

25. The Company: Hewlett-Packard
The Problem: OpenMCM (Monitoring System)

26. + 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.

27. + 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.

28. The Company: Korea Telecom
The Problem: Abnormal Traffic
Detection, Analysis, and Control system

29. + Problems
In 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.

30. + 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

31. + 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.

32. The Company: Korea Telecom
The Problem: Wired Telephone SMS Service

33. + 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.

34. + 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.

35. + 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.

36. The Company: Ministry of
Land, Transport, and Maritime
Affairs
The Problem: National Spatial Data Infrastructure

37. + Problems
MLTM 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.

38. + 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.

39. + 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).

40. The Company: NH Bank
The Problem: Accounting Processing System

41. + Problems
NH 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.

42. + 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.

43. + 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.

44. The Company: Samsung Securities
The Problem: Trading System Speed

45. + Problems
Samsung 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.

46. + 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.

47. + 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.

48. + 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.

49. The Company: LG Display
The Problem: Real-Time Flaw Detection

50. + Problems
LG Display suffered from inadequate quality control. Its inability to track defects
and change requirements in real-time was at the core. Data stored on multiple
DMBS’s perpetuated LG Display’s incapacity to monitor and react to these
issues, lowering yield and leading to high scrap. Limited to tracking only lots, the
automated system could not exploit the invaluable effects of pinpointing, per
unit, imperfections1.
 Numerous workstation reliance on multiple databases, led to substantial performance
degradation, triggering uncontainable defects.
 Vital quality control protocols went unanswered. Specifically, composition ratios of
active substrates and color filters were unidentified until it was too late.
 Quality control was relegated to 12-hour old data delivered in 10 minute intervals.
 LG Display found itself in a quandary. Increasing customer demand caused further
erosion in quality control, prompting unmanageable blows to profitability and
reputation.
1) The ability to detect even the slightest flaw in a single plate or deposited layer is vital to the quality control process.

51. + Solution
 LG Display implemented ALTIBASE HDB in-memory DBMS in 2008. ALTIBASE
HDB captured defect data immediately and continuously. LG Display’s quality
control personnel could identify and remedy defects at the point and time of
occurrence.
 LG Display deployed ALTIBASE HDB hybrid technology (in-memory and on-disk)
on a 20-core HP Superdome Server.
 LG Display received real-time defect data on a micro-level per product. Data
was further broken down by station, time of process deviation, and composition
layer.
 Prior to implementing ALTIBASE HDB, LG Display’s legacy system processed 21
million transactions per hour consuming 25%-45% CPU usage. With ALTIBASE
HDB, 12 million transactions are processed per half hour with only 10%-20%
CPU usage.

52. + Results
 LG Display possesses an industry leading quality control system.
 Precise product manufacturing processes are wed with exacting defect
detection.
 Personnel isolate problems instantly and act on accurate data, reforming
communication.
 LG Display relies on stringent data streams, quickly identifying root causes of
defects1.
 LG Display implements practices to eliminate recurring breakage points.
 LG Display’s revenues, profits, reputation, customer satisfaction and loyalty are
bolstered by a superior product.

53. + Technical Details
 LG Display achieved outstanding results with their new Advanced LCD
Processing Control system by leveraging the key features of ALTIBASE
HDB, specifically in the areas of high-performance, high availability and
flexibility.
ALTIBASE HDB ALTIBASE HDBReplication
APC
Ahead Processing Control
Active-ActiveMonitoring &
Control
LG Display
ALTIBASE HDB
Active-Active Architecture
And
Application Interfaces

54. + Performance, Flexibility and High Availability
 Before LG Display implemented ALTIBASE HDB, each manufacturing process was
managed by a dedicated conventional on-disk DBMS. LG Display desired to
manage all manufacturing processes by using a single DBMS for more efficient
administration of the monitoring systems and to have an integrated view of all
manufacturing processes. However the idea of a centralized DBMS system was
not possible due to poor performance of the conventional DBMS. LG Display’s
performance requirements of 5800 TPS (transactions per second) for INSERT
statements and 2100 records/hour for data migration were not met by the
conventional DBMS.
 Besides the performance issues, the need to maintain a dedicated DBMS for
each manufacturing process created major challenges in the areas of application
development and maintenance, as well as database administration and tuning.
The developers had to deal with an extremely complex application
infrastructure. The database administrators had a difficult job of administering a
large number of DBMS’s, for software updates and data integration tasks. The
challenging administration tasks also resulted in numerous unplanned and
planned system outages.

55. + Performance, Flexibility and High Availability
 ALTIBASE HDB allowed LG Display to consolidate all existing DBMS’s into a single
high performing DBMS to monitor all manufacturing processes in real-time.
Taking advantage of both the unique hybrid functionality and the built-in
replication feature, LG Display implemented ALTIBASE HDB based on a 2-
node, Active-Active architecture. In this architecture, both ALTIBASE HDB
instances were configured in hybrid DBMS mode; in-memory DBMS + on-disk
DBMS.
 This architecture was the perfect fit for eliminating performance, administration
and reliability issues of LG Display’s older systems. ALTIBASE HDB in-memory
DBMS delivered extreme speed for real-time monitoring of all manufacturing
processes by delivering mind-blowing 50,000 TPS performance for INSERT
statements. ALTIBASE HDB on-disk DBMS was used as the repository for 12-hour
and older manufacturing process data. Migrating data from memory to disk was
a simple task attributable to ALTIBASE HDB’s unique MOVE SQL statement. With
MOVE statement, LG Display was able to migrate data from memory to disk at a
10,000 TPS performance.
 Active-Active HA architecture was realized using the built-in replication
feature, allowing synchronous replication in a shared-nothing configuration with
a zero downtime topology. With the new architecture, day to day tasks for both
application developers and database administrators were greatly simplified.

56. THANK YOU
www.altibase.com
info@altibase.com