Evolution of Data Management Solutions in Modern Businesses

undefined
Solutions Overview
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
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 100
th
 client and 500
th
 deployment
2006
 – Support for Spatial data (GEOMETRY Data Type) is added
2009
 – Complex Events Processing (CEP) engine is developed
2013 – 2014
:
Altibase acquires its 500
th
 client and 4000
th
 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
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
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
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
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
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
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.
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
Transactional Log
Checkpoint
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
Replication
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)
Fastest In-Memory Database
1,417,164 TPS
 
IBM X3850, 24Core*Xeon E7-4807@1.87Ghz, 32G MEM
,
  
SUSE
 Linux 11 SP 1 64Bit
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)
Transactional Log
Checkpoint
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
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)
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
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)
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
CEP – 
In-Memory Middleware
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 ……….
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
Hewlett-Packard OpenMCM
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.
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.
Korea Telecom
Abnormal Traffic Detection,
Analysis, and Control
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.
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
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.
Korea Telecom
Wired Telephone SMS Service
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.
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.
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.
Ministry of Land, Transport, and
Maritime Affairs’ National Spatial
Data Infrastructure
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.
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.
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).
NH Bank
Accounting Processing System
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.
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.
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.
Samsung Securities
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.
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.
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.
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.
THANK YOU
info@altibase.com
Slide Note
Embed
Share

Explore the journey of a leading provider of in-memory data solutions, Altibase, from its founding in 1999 to its milestones in technology advancements and client acquisition. Learn about the changing landscape of data management, the importance of balancing transactional and analytical systems, and the reasons behind companies shifting towards innovative data solutions.

  • Data Management
  • Altibase
  • In-memory Solutions
  • Business Evolution
  • Technology Advancements

Uploaded on Jul 16, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Solutions Overview

  2. AGENDA Company Overview Market Overview Unique Capabilities

  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. AGENDA Company Overview Market Overview Unique Capabilities

  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. + Transactional vs. Analytical Analytical Systems Transactional Systems Bandwidth Customization Data Warehouse Data Marts CRM, ERP, SFA POS, ATM Interactivity/Speed Availability Scalability Reporting Apps Custom Apps Scalability OLAP OLTP Few users Many users Batch updates Continuous updates Strategic planning Tactical activity Long complex lookups Many short transactions TB-PB of data MB to TB of data Important for Audits Mission critical

  8. +Why Companies are turning to Altibase Extremely Fast Response Times Scalable on Commodity Platforms Predictable and Consistent Response Times Flexible Architecture for the Cloud Standards Compliant Low Latency Rich Features & Rich Interfaces Throughput Scalability Extensive Knowledge of and Commitment to In-memory Computing Real time Replication Highly Available and Reliable Proven Technology Persistent and Durable

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

  10. +Example Applications Risk Management Transportations Operations Management Fraud Detection Software-as-a-Service Algorithmic Trading Real time Analytics Security Intelligence Profitability Analysis Supply Chain Tracking Global Web Commerce Telecom/Media Revenue Leakage Sales Incentive Promotions Management Service Delivery Online Gaming . Many More Inventory Forecasting

  11. AGENDA Company Overview Market Overview Unique Capabilities

  12. +In-Memory Database Technology Extremely Fast Transaction processing Entire database resides in computer s memory Application Powered by special algorithms and data structures that are highly optimized for in- memory computing Connectivity Query Processor Hundreds of thousands of transactions per second Storage Manager Short and Predictable Response times In-Memory Database DRAM Optimized for fastest transactional processing with the shortest response times measured in microseconds Checkpoint Transactional Log The improved response times fuel High Throughput.

  13. +Persistent In-Memory Database Persistent and Durable In-Memory DBMS Full ACID support for all database transactions Application Atomicity Connectivity Consistency Isolation Application 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 Checkpoint Transactional Log Relaxed Durability Enhanced Durability Strict Durability

  14. +Highly Available In-Memory Database High Availability via built-in Replication Feature Application Log-based replication Adaptive Consistency Synchronous Replication Asynchronous Replication Non-Stop Service Architecture Active-Active Replication Active-Standby Near Performance Standalone Replication 90% in Active-Active 96% Active-Standby Conflict Detection and Resolution Offline Replication

  15. +Highly Scalable In-Memory Database Horizontal Scalability via built-in Replication Feature Leveraging TCP/IP protocol Unlimited nodes Horizontal Scaling via Replication Flexible Load Balancing Architecture Vertical Scalability Scales On Commodity Platforms Increased RAM Increased CPU Dynamic sizing of In-Memory database with no system AutoExtend feature Vertical Scaling (CPU, RAM) downtime via

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

  17. +XDB Optimized for In-Memory Customizable application performance via Innovative and Rich Interfaces Application Conventional client/server protocols TCP/IP and IPC for compatibility (1) TCP/IP or IPC 1 Query Processor 2 Direct Access Mode to completely eliminate network overhead (2) Application Storage Manager 3 Direct Access API Mode eliminates not only network overhead but also query processing overhead (3) Checkpoint Transactional Log

  18. +HDB Superior Deployment Flexibility Hybrid Architecture Combines the benefits of in-memory storage and on-disk storage in a single relational database In-Memory DBMS Flexible Deployment Modes Speed Memory Data In-Memory Database Only Hybrid DBMS On-Disk Database Only Buffer Memory Data Hybrid Database (In-Memory + On-Disk) Disk Data Disk DBMS Support for different workloads Buffer Data Size Real-time access to time critical Hot data Disk Data Access to historical Cold data for analytics Complex transactions through integrated data Easy bidirectional data migration between Hot and Cold data zones

  19. + Standards Compliant In-Memory Database Support for SQL Standards SQL:1999 Application Support for all common data types SQL ODBC JDBC Support Database Connectivity Standards .Net CLI OLEDB ODBC (Microsoft 3.5.1 API) JDBC (Type 2 & 4) TCP/IP UDS IPC .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)

  20. +Rich Set of Tools and Utilities Productivity and Administration iSQL WareValley Orange (GUI) WareValley Orange ReplicationManager (GUI) iSQL altiProfile Orange Audit Application iLoader MigrationCenter ETL aExport altiProfile aExport Replication Manager Audit iLoader Interoperability and Migration MigrationCenter (GUI) oraAdapter

  21. +Open Platform In-Memory Database Sun Solaris OS IBM AIX SPARC (64bit) PowerPC (64bit) Intel (64bit) PowerPC (32-bit) Client Only Intel (32bit) Client Only Linux HP HPUX Intel (32bit) PARISC (64bit) Intel (64bit) PARISC (32bit) Client Only IA (64bit) Microsoft Windows IA (32bit) Client Only Intel (32bit) Intel (64bit)

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

  23. + CEP In-Memory Middleware ALTIBASE CEP is an In-Memory Middleware for real-time processing, querying and analyzing data streams Data Characteristics Data & Event Sources Continuously flowing Transactional Systems Other Systems Too large to store Sensors Data & Event Sources Rapidly changing Mobile Devices ALTIBASE CEP Time-sensitive RFID . Extremely fast processing/filtering Continuous Query Processing (CQL) Dropped Data Continuous execution of registered SQL queries ALTIBASE HDB Or ALTIBASE XDB 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

  24. + 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 Java Java Application Application ALTIBASE MAS Optimized for in-memory computing Shared Memory Breakthrough Java application performance Enables Java applications to directly access to ALTIBASE XDB In-Memory database via shared memory Extreme Low Latency ALTIBASE XDB Greater scalability Runs on low-cost commodity hardware Log Checkpoint

  25. Hewlett-Packard OpenMCM

  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. Korea Telecom Abnormal Traffic Detection, Analysis, and Control

  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. Korea Telecom 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. Ministry of Land, Transport, and Maritime Affairs 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. NH Bank 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. Samsung Securities

  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. THANK YOU info@altibase.com

Related


More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#