|
Objectivity/DB enables and empowers our customers to deliver high performance mission-critical applications. However, to do so; one must fully understand the architecture and proper usage to leverage the power of our high end database system. In order to help you grow your knowledge base, we have the following documentation available for your reference.
Included in your installation of Objectivity/DB, there is a directory full of documentation that we call Objectivity Books.
There are 2 ways to get to these books:
- View the Objectivity Books here online click below
- With Objectivity/DB installed: StartMenu>All Programs>Objectivity Rx.x>Objectivity Books (pdf)
Here is a list of the documents that are available in the download:
- Objectivity/DB
- Objectivity/C++
- Objectivity for Java
- Objectivity For C# .NET
- Objectivity/Python
- Objectivity/SmallTalk for VisualWorks
- Objectivity/SQL++
| Product Information and Technical Briefs |
- Objectivity/DB Technical Overview [+/-]
Database management for today’s high-end applications. Objectivity/DB is a distributed object database management system (ODBMS). As an ODBMS, Objectivity/DB is ideal for applications that require complex data models. As a distributed ODBMS, Objectivity/DB supports large numbers of users and provides high-performance access to large volumes of physically distributed data. Its distributed database architecture provides scalability as well as performance. This architecture supports a wide range of application architectures, including client/server, mixed-tier, and service-oriented.
Objectivity/DB integrates easily with application software. It allows you to directly store and manage objects through standard language interfaces—such as, C#/.NET, C++, Java, Python, Smalltalk, SQL and XML—using traditional programming techniques and tools. This overview will give you a very good understanding of Objectivity/DB's overall architecture and it's capabilities.
[View/Download] A must read for Beginning Users of Objectivity/DB
- Physical Design with Objectivity/DB [+/-]
Database application design is often described as a combination of logical and physical design; logical design being the process of creating a logical schema that describes the persistence needs of the application, while physical design being the process of determining how that logical schema is to be represented in the database. Typical physical design for applications built upon relational databases involve creating an internal schema (defining the tables), mapping the logical schema to the internal schema (classes to tables), and choosing various DB specific storage options for the internal schema components (tables and sometimes table fragments).
[View/Download]
- Objectivity Query Engine [+/-]
This White Paper describes the evolution of the general purpose Objectivity/DB object database from a homogeneous, navigational object access tool to a distributed, federated (heterogeneous) query engine.
[View/Download]
- Flexible Deployment [+/-]
Objectivity/DB uses a powerful, distributed processing architecture to manage localized, centralized or distributed databases. This White Paper discusses a wide variety of Objectivity/DB deployment options, ranging from laptops to distributed clusters in High Performance Computing environments. It also covers high availability configurations, in-memory databases, the distributed Parallel Query Engine and data replication issues. We start with a quick introduction to the distributed architecture of Objectivity/DB and then discuss the parameters that affect deployment configurations before describing a range of configurations.
[View/Download]
- Data Inegration [+/-]
This White Paper discusses practical ways of deploying Objectivity/DB as a hub for integrating data from multiple sources. There are many approaches to consolidating multisource data. Data warehouses are popular in traditional information technology departments. Data fusion is a difficult problem confronting users of geospatial and sensor data. Users of criminal investigation or intelligence data need to store and correlate vast amounts of disparate information, ranging from text, images, video and voice to various kinds of specialized intelligence data (such as SIGINT, ELINT, RADINT, TELINT and COMINT).
[View/Download]
- Dynamic Container™ - The Key to Superior Performance [+/-]
In the object oriented design of software applications, architecture is one of the issues at the forefront. That same focus on good architecture has been brought to Objectivity/DB in order to lay a foundation that will enable software developers to build solutions that will stand the test of time. One
basic commonality amongst all ODBMS is that they all store and retrieve objects. However, we strongly suggest that how a given ODBMS achieves that basic goal of storage is the key to choosing an ODBMS. Relational
Database Systems (RDBMS) have had decades in which to refine and perfect their ways of storing rows and columns of data. B-Trees and indexing methods have become a staple in almost all RDBMS. In the ODBMS
world, there are several competing ideas on how storage of objects should be achieved and we will show that Objectivity/DB has an excellent solution to that very crucial question.
This document will give the background to Objectivity/DB storage design decisions and cover key aspects of Objectivity/DB architecture. We will specifically deal with the powerful concept of Objectivity/DB containers and how they may be used to achieve superior designs. We will also show that traditional aspects of software development such as data structures can be used as well as current object oriented development methods.
[View/Download]
- Accelerating Your Object Oriented Development [+/-]
This paper is an overview of the issues that arise from implementing object persistence with a relational database. The basis for this paper is our recent experience with Object-Oriented projects that used relational database technology. Those experiences have shown us that the cost of mixing the two paradigms is very high and can seriously detract from the benefits of Object-Oriented development. There is no question that object-to-relational solutions can be made to work, but at what price? This paper describes approaches to building object-to-relational bridges and highlights problems and compromises that typically arise. This is not a guide to implementing an object-to-relational bridge; instead, its purpose is to explain some fundamental issues and provide information that would be useful in making a database technology selection.
[View/Download]
- Hitting the Relational Wall [+/-]
Relational Database Management Systems (RDBMSs) have been very successful, but their success is limited to certain types of applications. As business users expand to newer types of applications, and grow older ones, their attempts to use RDBMS encounter the "Relational Wall," where RDBMS technology no longer provides the performance and functionality needed. Attempts to scale the wall with relational technology lead to poor performance, poor scalability, and loss of integrity. ODBMSs offer a path beyond the wall. “Hitting the Relational Wall” measures the wall, explains what model and architectural differences cause it, how to foresee it, and how to avoid it.
[View Executive Summary] [View Full Length Paper]
We have many other informative white papers for your viewing on our main site. There, you will find white papers specific to all the verticals that uses Objectivity/DB today:
- Government
- Manufacturing, Process Control & Automation
- Oil and Gas Enterprises
- Data Intensive Sciences
- Telecommunications
- Life Sciences
Goto White Papers
|
|
