Microsoft Technology Licensing, LLC

Ramesh Nagarajan

Subramanian Muralidhar

Sean B House

Stephen Frederick Starck

Simon Cavanagh

Michael Pizzo

Lijiang Fang

Rodger N Kline

Maxim Mazeev

Michael Eric Deem

Benjamin Albahari

Edward G Sheppard

Yanbiao Zhao

Katica Iceva

Arthur T Whitten

Fabio Meireles Fernandez Valbuena

Fabio Meireles F Valbuena

Systems and methods that translate queries defined by an entity model, to a dialect recognizable by storage provider (e.g., relational store). A bridge component facilitates translation of a rich object structure into flat relational constructs, which can then be executed by a relational store. Accordingly, queries defined by applications in terms of entity concepts can readily be employed in conjunction with relational data stores. Similarly, results obtained from executing the query can be converted back to a form understandable by the application.

Extensible command execution for entity data model platform

A query language has support for rich data types. A query language system contains an application configured to generate queries according to the query language. In addition, the system has a platform for handling queries that are generated using the provided query language. The platform contains an object services layer, a map provider layer, and a bridge layer which may ultimately interface with a variety of commercially available databases.

Extensible query language with support for rich data types

To provide data from a database in response to an application query, the database is queried an initial time to provide a first set of data. For example, a 'fast first page' may be requested, by requesting that all data which might appear on a first page to be displayed is obtained from the database first. After this, one or more subsequent asynchronous queries obtain the remaining information responsive to the query. Or, certain columns from the database ('spine columns') may be requested in the initial query of the database, and the rest of the data requested subsequently. Thus, information needed to make an initial presentation to a user can be obtained first, and other information filled in subsequently.

Fast rich application view initiation

An application program interface (API) for a data platform. The API includes a generic data access component that exposes at least one of stores, sessions, transactions, and query services of the data platform, which data platform is associated with a data store. A data classes component of the API provides canonical, application-independent classes that expose types and relationships of a data model of the data platform. The API includes a domain data classes component of application-specific and framework-specific classes that expose domain-specific properties and behaviors of the data platform. The data platform can be a common data platform that interfaces to the data store to provide data services accessible by a plurality of disparate application frameworks, which data services allow a corresponding application of the different frameworks to access the data store.

Storage API for a common data platform

Growing community of inventors

Seattle, WA, United States of America

Ramesh Nagarajan