Posts

MEZMO adopts Altibase for its mobile app for the hearing impaired

Altibase Announces that MEZMO has Adopted Altibase for its Mobile Communication App for the Hearing Impaired

INNOCAPTION

Altibase is pleased to announce that MEZMO, the communication provider approved by the FCC as a TRS provider for the deaf in the US, has switched from MySQL to Altibase. Altibase will now function as its core database for telecommunication replay  service (TRS), which enables phone calls to the hearing impaired by showing the voice of the other party by letter.

MEZMO, headquartered in the US, operates the service, InnoCaption. The company found its MySQL database service inadequate in meeting its specific requirements. The challenges it was facing included performance deterioration as the number of subscribers increased and more services were added. Another issue was no real time updates of information on subscribers, billing status and logs. The process also requires some manual handling from time to time in batch mode. In addition, product instability, mediocre performance scaling and heavy dependence on add-ons of MySQL were often a cause for concern.

MEZMO required a database that could update and process its data without performance degradation. It also wanted to address the performance degradation issue with minimal investment in hardware additions or upgrade. The new database was required to allow for easy migration of data objects from MySQL and allow for easy adoption in the Amazon cloud. SQL databases, moreover, could pose problems with inter-operating with other systems built by the company on relational databases.

The above considerations were met by Altibase, and MEZMO adopted Altibase in 2014. Since then, Altibase has served MEMZO as a core database that provides both performance and reliability. MEZMO has been able to avoid performance degradation even when more subscribers and services are added.

Data processing and updating is now executed at a fraction of the cost that could have incurred with hardware addition for equal performance. Altibase’s hybrid architecture is utilized to store frequently used, recent data in memory, and less frequently used, historical data on disk.

The migration was easy and straightforward between relational databases, MySQL and Altibase.

MEZMO currently updates its system to analyze big data using Altibase in light of the performance and reliability Altibase has provided in the past 3 years.

After nearly 20 years as a closed source database, Altibase is now open source, and that includes its state-of-the-art sharding.

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

 

What is sharding? @Alexander Lielacher

What Is Sharding?

 by 

What Is Sharding?

Sharding is a concept in database design, and as implied by its name, sharding involves creating smaller parts from a larger one. In the context of databases, sharding results in the creation of smaller partitions in the ledger. These partitions are thus referred to as shards.

It is important to note that in sharding, the partitioning is done horizontally as opposed to vertically. A shard may contain data that is in all the other shards; however, these partitions are designed to include data that is accessible only through it, which means that the data in each shard is unique to it. To access the data and use it, one must queue the specific shard that contains said data.

Sharding is employed in database architecture because it can improve the performance of a database or search engine. The design tool does this because it reduces the index size of a ledger. As a result, the ledger can provide search results quicker. Additionally, because different shards can be stored on different servers, the tool can be beneficial for large corporations with large data sets that they need to store separately such as multinational corporations operating in different countries.

Sharding in Distributed Ledgers

Sharding has grown in popularity within the cryptocurrency community as a result of widespread concerns over blockchain scalability issues. For instance, the Bitcoin Network processes about seven transactions per second, and Ethereum is only slightly faster, handling around 15 operations per second. These are both paltry compared to large payment processors like Visa and Mastercard.

While the bitcoin community has dealt with its scaling issues in various ways, the Ethereum project has outlined a more streamlined approach to solving its scalability concerns. Ethereum’s approach involves switching to a Proof of Stake (PoS) algorithm, which will work in tandem with a sharded database design.

How Would Sharding Work on Ethereum?

During his keynote speech at an event held at the School of Business of the Singapore University of Social Sciences, Ethereum’s cocreator Vitalik Buterin attempted to explain the concept of sharding the Ethereum ledger in a straightforward manner. In his talk entitled “The Road Ahead,” he stated:

“Imagine that Ethereum has been split into thousands of islands. Each island can do its own thing. Each of the islands has its own unique features and everyone belonging on that island, i.e., the accounts, can interact with each other and they can freely indulge in all its features. If they want to contact with other islands, they will have to use some sort of protocol.”

Currently, on the Ethereum network, as well as other blockchains, each node stores the global state. The globals state refers to the account balances, contract code and storage and all additional relevant information. Additionally, all nodes process all transactions. While this provides for a very secure ledger, it dramatically limits to what extent the network can scale because, within this design, a blockchain is only as good as a single node on its network.

In other words, the speed of a blockchain is defined by how quick a single node is as all nodes must perform the same transaction over and over.

A telco with over 250 million subscribers utilizes Altibase to implement real time billing with its prepaid services

A Telco With Over 250 Million Subscribers Utilizes Altibase to Implement Real Time Billing With its Prepaid Services

Altibase Was Chosen Over Oracle TimesTen and SolidDB

NEW YORKJuly 23, 2018 /PRNewswire/ — The telco is the third largest telecommunications provider in China with 250 million subscribers.

Historically, the company suffered from payment defaults and operational deficiencies for its online charging system. Those problems manifested themselves in three core areas.

1. Inability to effectively terminate service. The company was unable to identify and cut customer usage when prepaid balances were exhausted. Essentially, customers who chose to game the system would continue to talk for free until its systems “caught up.” The company’s legacy DBMS could not efficiently detect negative balances. Worse yet, losses shadowed increasing latency. The result was a vast amount of uncollectible receivables.

2. Inability to reinstate timely service.Unfortunately, customers who inadvertently exhausted their balances and subsequently paid their overages suffered as well. Limitations in its legacy DBMS speed prevented swift reactivation of service to these loyal customers. The result was a catastrophic loss of consumer confidence, customer satisfaction and, ultimately, retention.

3. Inability for customers to accurately check remaining balances. Since customers could not accurately check their current balances, they could not preemptively replenish their accounts. The balance information was stale, and loyal customers paid the price with defunct service.

The company tested various database products including Oracle TimesTen, soildDB and Altibase. It chose Altibase in 2010. Since then, the company has adopted Altibase in consideration of performance, reliability and functionality all with the underpinnings of a complete solution.

The results are:

  1. The company has the capacity to precisely check and act on balances.
  2. Its system latency was reduced, which corrected errors that some customers took advantage of.
  3. Outstanding balances, when paid, coincided with swift restoration of service.
  4. Customers can accurately check remaining balances, knowing when to reload funds.
  5. Customer satisfaction, loyalty, attraction and retention are maximized.
  6. Customer attrition is minimized.

After nearly 20 years as an enterprise grade closed source database, Altibase went open source in February this year.

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

A world leading steelmaker chooses Altibase over Oralce

A World Leading Steelmaker Chooses Altibase over Oracle and Lowers Database-Related TCO by over 60%

 NEWS PROVIDED BY

Altibase Corp. 

Jun 11, 2018, 08:32 ET

NEW YORKJune 11, 2018 /PRNewswire/ — This June, Altibase completed installation of its in-memory/hybrid database for a blast furnace of one of the world’s biggest steel manufacturers. The company, headquartered in South Korea, is a multinational steel-making company and the world’s fourth-largest steelmaker.

In late 2017, the company decided to upgrade its database that provided real-time monitoring and analysis of one of its blast furnaces. The company first considered Oracle for the job, but then rejected Oracle because its license and maintenance costs were too costly.

The company then turned to Altibase. With nearly 20 years’ experience serving more than 600 enterprise clients, including those in the Fortune Global 500, Altibase offered performance and reliability comparable to Oracle at a fraction of the cost.

In choosing Altibase, the company considered these five factors:

1. Performance. It required a database that could handle over 100,000 transactions per second with response rates measured in microseconds. Altibase’s in-memory capabilities met this standard with ease.

2. Hybrid Technology. With Altibase’s all-in-one hybrid technology, the company’s data could be stored and manipulated in main memory alone, on physical disk alone, or on a combination of both. As Altibase is a hybrid database, the company did not need to purchase a disk-resident database separately to store and manipulate historical and less frequently used (cold) data.

3. Reliability. Altibase’s built-in replication features provided the company with peace of mind even in the unexpected failure of its master server.

4. Speed of Installation. Altibase’s installation took only three months: two months for application development and one month for performance tuning. Most of its applications are built on relational databases. It eliminated the need for the company to make any radical architectural changes to existing applications. And, the company’s existing DBAs found that Altibase is easy to learn and adopt.

5. Cost. By adopting Altibase, the company lowered database-related TCO by over 60%.

Altibase chairman, Paul Nahm, says, “With the company’s successful adoption, Altibase has again demonstrated that you can have an enterprise grade database that provides reliable, comprehensive solutions for mission critical applications at a much lower TCO. And now that we went open source in February, Altibase lowers TCO even more.”

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

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

SOURCE Altibase Corp.

Related Links

http://www.altibase.com

Altibase introduction in 01net

Chi è Altibase, il database opensource che vuole sfidare Ibm, Microsoft e Oracle

Altibase è un database relazionale di livello enterprise opensource.

Come afferma il presidente di Altibase, Paul Nahm «L’ industria dei database sta diventando opensource, la tendenza è chiara. Ma per i clienti aziendali esigenti e prudenti con le applicazioni mission critical c’è ancora una grande domanda: esiste un database open source di cui ci siuò fidare e che possa essere affidabile 24 ore su 24,7 giorni su 7?» Ovviamente per Nahm la risposta è Altibase.

La società è partner di Red Hat, Microstrategy, Aws e Intel. E Altibase è un database maturo e collaudato. Per quasi 20 anni (19 per l’esattezza), la società ha servito oltre 600 clienti aziendali, tra cui 8 aziende Fortune Global 500, in oltre 6.000 implementazioni.

Andando in opensource Altibase intende sfidare dichiaratamente Oracle, Ibm e Microsoft fornendo pari funzionalità a costi molto inferiori.

Altibase, dichiara la società, fornisce tecnologia di sharding allo stato dell’arte, per la creazione di un database distribuito in cui ogni nodo contiene una porzione del database.

Con il database relazionale opensource le aziende non devono apportare modifiche ai loro sistemi esistenti che funzionano su database relazionali.

Inoltre, Altibase riduce al minimo l’uso di coordinatori di shardoing, in modo che le imprese non incontrino quasi nessun problema di coordinamento.

Indipendentemente dal numero di server aggiunti, dicono da Altibase, viene mantenuto il miglioramento lineare delle prestazioni, con conseguente riduzione del TCO.

 

Di seguito, la tabella comparativa, fornita dalla società, che evidenzia le principali funzionalità dei database relazionali di taglio enterprise, sottolineando la disponibilità opensource di Altibase.


Fornitori di database enterprise
Oracle IBM Microsoft Altibase
Anni di attività 41 35 29 19
In-memory storage Si Si Si Si
Replication Si Si Si Si
Relational Si Si Si Si
Full ACID compliance Si Si Si Si
SQL standards Si Si Si Si
GUI tool Si Si Si Si
Hybrid table Si Si Si Si
On-disk storage Si Si Si Si
Sharding Si Si Si Si
Spatial Si Si Si Si
Opensource Si
Se questo articolo ti è piaciuto e vuoi rimanere sempre informato sulle novità tecnologiche iscriviti alla newsletter gratuita.