| |
|
Why M-Tech chose Caché for its database engine:
When AMO was first written over 10 years ago it was developed using
the predecessor to Caché. The language and the hierarchical database
systems were (unusually) combined to create a unique integrated development
environment.
Since then it has grown and developed into Caché, the post-relational
database that exists today with a complete suite of development tools
(including e-commerce) to rival any in the market.
During that time M-Tech has experienced dramatic growth for a number
of it's clients, some turning into PLC's, one expanding into Europe,
another going global (USA, Canada, Europe and the Far East), another
launching TV shopping channels with live, streaming web sites, all of
which have thoroughly tested the scalability and performance of Caché.
Using the same code, same database engine, same database layout, and
very similar hardware infrastructure (slightly more powerful servers)
clients have grown from six users to hundreds of users, and have grown
from taking ten's of orders an hour to hundreds of orders a minute.
This, combined with our "Lifetime Approach" to meeting clients
continued demands would have been simply impossible using a "comparable"
database engine.
|
Deal yourself a better hand
with M-Tech and Caché
Caché, the high performance, post-relational database is
essential for the service and scalability we offer our clients
|
Caché Features & Benefits:
Caché, the post-relational database from
InterSystems, has the features professional developers need
to quickly create Web and client/server applications. Caché
benefits developers by giving them their choice of development
tools, programming languages, and methods of data access. Caché
benefits transaction processing applications by providing outstanding
performance, massive scalability, real-time data analytics, and
robust reliability.
All these capabilities are tied together in an easy-to-use rapid
development environment. With Caché, you can make applications
faster.
Caché Data Server Features
When it comes to transaction processing, performance is critical.
Caché's data server technology lets you scale applications
up to serve tens of thousands of users without sacrificing speed.
| Features |
Benefits |
| Multidimensional
Data Engine |
| All data is stored in sparse multidimensional
arrays that eliminate the processing overhead related to the
"joins" common to relational databases. |
High performance. Massive scalability. Realistic
modeling of complex data. Efficient data storage consumes
less disk space, and requires less hardware. |
| Object Data Access |
| Data can be modeled as objects. Caché
supports encapsulation, multiple inheritance, polymorphism,
embedded objects, references, collections, relationships,
BLOBs. |
Rapid application development. Intuitive modeling
of complex data. |
| SQL Data Access |
| Allows relational access to Caché database.
Supports both ODBC and JDBC. |
Boosts performance of legacy relational applications.
Provides SQL connectivity to standard query, reporting and
analysis tools. |
| Multidimensional
Data Access |
| Provides direct control of the multidimensional
structures in the Caché database. |
High performance. Enables connectivity
to legacy systems. |
| Unified
Data Architecture |
| Object classes and relational tables
are automatically generated from a single data definition. |
Rapid development. Eliminates "impedance
mismatch" between objects and tables. |
| Transactional
Bit-Map Indexing |
| Caché's bit-map indexes can
be updated extremely quickly, making them suitable for use
with "live" data. |
Fast response to complex queries.
Quick updating enables real-time data analysis while maintaining
high-performance transaction processing. |
| Performance
Monitoring API |
| Connects to popular monitoring tools
like BMC's Patrol and Fortel's Sightline. |
Aids in application optimization.
Provides a method of demonstrably meeting performance specification |
What's wrong with relational databases?
Analyst
Whitepaper - The Failure of Relational Database, The Rise of Object
Technology, The Need for the Hybrid Databases
|
|
