Phased Analytics based on Data Staging

Analytica provides the concept of calculated properties that are used to augment the documents from the base database. This is the mechanism to add dynamically properties to documents that are relevant for analysis. These additional properties exist within Analytica, but

Tagged with: , , ,
Posted in Architecture, Concepts

Computation based on Order of Documents

In many cases it is necessary to compute a property value based on the values of a property in a subsequent document. For example, to show growth over time. Analytica provides several functions that can be of help. One function

Tagged with: , ,
Posted in Concepts

Schema Transformation: Null Values

Indicating that a property does not have a value can be done in several ways in schema-free databases. In context JSON it is possible to omit the property set the property value to “null” How can documents be transformed so

Tagged with: , , , ,
Posted in Concepts

Analytics: “Query – Result” Approaches Lack Conceptual Power

Traditional Approach “Traditional Analytics” follows the query – result approach. For example, a query is formulated determining an aggregation over a subset of the base data to be analyzed, and the system returns the requested aggregation as a query result.

Tagged with: , , , ,
Posted in Architecture, Concepts

Analytica and Snapshot Semantics for Reporting

In many cases, analytics is performed on a transactional data set that is constantly changing due to end user activities or B2B connections. The rate of change might be small or large, depending on the application system, the date and

Tagged with: ,
Posted in Architecture, Concepts

Why Analytics over a REST API?

Analytica is making all its functionality available over a REST API. Why is that important? Cool and Interesting Technology From a distributed computing viewpoint, REST is cool technology due to the programming language and platform independence, paired with the availability

Tagged with: ,
Posted in Architecture

Virtual Collections: Document Selection for Analytics

The document-oriented data model suggests to collect all properties for a concept or object within one document. In addition, the application system decides on the properties it needs in order to provide the required functionality to end users. Furthermore, documents

Tagged with: , , ,
Posted in Architecture, Concepts

Accessing MongoDB serverStatus, dbStats and collStats

Aside from analyzing business or application data, sometimes it is important to analyze the behavior of a MongoDB server, database or individual collections. Special Operational Collections In order to support users in accomplishing this, Analytica makes key operational data sets

Tagged with: , , , ,
Posted in Concepts

Document ‘Uniformification’

A contrasting situation is building up between the ‘schema-less’ approach of document-oriented NoSQL databases and JSON-native analytics tools like Analytica. Documents that do not have to comply to a global document schema are being regarded as a plus in terms

Tagged with: , , ,
Posted in Data Modeling

Global vs. Document-Local Calculated (‘Virtual’) Properties

Analytica supports the concept of calculated properties, aka, virtual properties. The name ‘calculated’ comes from the fact that the values are not retrieved from the database, but are dynamically calculated. ‘Virtual’ has the same co-notation, i.e., not coming from the

Tagged with: , ,
Posted in Architecture, Concepts