New post

Pesquisar

Article
· Oct 21, 2015 1m read

InterSystems Caché as an Alternative to In-Memory Databases

#Caché

Introduction

To overcome the performance limitations of traditional relational databases, applications - ranging from those running on a single machine to large, interconnected grids - often use in-memory databases to accelerate data access. While in-memory databases and caching products increase throughput, they suffer from a number of limitations including lack of support for large data sets, excessive hardware requirements, and limits on scalability.

InterSystems Caché is a high-performance object database with a unique architecture that makes it suitable for applications that typically use in-memory databases. Caché's performance is comparable to that of in-memory databases, but Caché also provides:

  • Persistence - data is not lost when a machine is turned off or crashes
  • Rapid access to very large data sets
  • The ability to scale to hundreds of computers and tens of thousands of users
  • Simultaneous data access via SQL and objects: Java, C++, .NET, etc.

This paper explains why Caché is an attractive alternative to in-memory databases for companies that need high-speed access to large amounts of data.

superior-alternative-to-in-memory-databases-key-value-stores.pdf
Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 1m read

InterSystems Caché Benchmark: Achieving Millions of Database Accesses per Second Inexpensively

#Caché

Abstract

In a recent benchmark test of an application based on InterSystems Caché, a sustainable rate of 8.9million database accesses/second, with peaks of 16.9 million database accesses/second, was achieved. These results were from a test performed on a connected system of eight applications servers, using Intel Xeon 5570 processors, and running Linux as the operating system. This benchmark shows that:

  1. Caché can achieve unheard of levels of performance for an object database. It provides full persistence of data at speeds that are normally only reached by in-memory databases.
  2. Caché demonstrates this high performance while running on inexpensive servers.
  3. Caché offers excellent horizontal scalability, with throughput scaling linearly as application servers are added.
Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 1m read

Caché and XML-based Data Exchange Standards

#Caché #Interoperability #XML

Introduction

Because of increasing business and governmental pressures to integrate their operations, the financial services industry is developing a number of standards for data exchange and other common functions. Standards such as XBRL, FpML, MDDL, RIXML, and FIXML are all specialized dialects of XML (Extensible Markup Language). Any financial services application with good support for XML will be able to communicate effectively using one or more of the emerging industry standards.

Efficient data exchange increases the need for fast, scalable data persistence. Financial services applications must be able to process and persist large amounts data very quickly. Plus, the data must be easily accessible via SQL for analysis and reporting purposes. This paper will examine various database technologies with regards to their suitability for use with XML-based standards. It will show that Caché, with its Unified Data Architecture and seamless XML parsing, is the ideal database for use with the XML-based standards of the financial services industry.

Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 1m read

20X Faster SQL. How Does Caché Do That?

#Caché #SQL

Customers who switch to Caché from relational databases report that their average performance is up to 20 time faster, running on the same hardware, with no changes to the application. What is it about Caché that lets applications run so fast?

Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 1m read

Fighting Impedance Mismatch at the Database Level

#Caché #SQL

Introduction

With the maturation and wide acceptance of Java, object-oriented programming has moved to the foreground of the application development landscape. Because of their rich data models and support for productivity-enhancing concepts such as encapsulation, inheritance, and polymorphism, object technologies like Java, C++, and COM, are favored by today's application developers.

However, much of the world's data still resides in relational databases. Developers of database applications (that is, any application that accesses stored data) often find themselves fighting impedance mismatch: the inherent disconnect between the object and relational data models. Efforts to "map" relational data into a usable object format are often detrimental to both programmer productivity and application performance.

However, impedance mismatch can be mitigated by the proper choice of database technology. This paper defines impedance mismatch and gives two simple examples of how it affects application development. It then discusses, with regards to impedance mismatch, the pros and cons of three kinds of database: relational, object, and Caché, the multidimensional database from InterSystems.

Discussion (0)0
Log in or sign up to continue