Abstract: A database is stored as a plurality of database shards in a distributed database grid comprising a plurality of grid elements, each including a mid-tier database system. A first grid element receives, from an application executing in the same memory as a mid-tier database system of the first grid element, a first database transaction including at least one database operation on specific data stored in a first database shard that belongs to the first grid element. The first grid element performs and commits the first database transaction without participation of another grid element of the plurality of grid elements. The first grid element receives a second database transaction that requires access to another database shard that does not belong to the first grid element. Multiple grid elements of the plurality of grid elements perform the second database transaction and commit the second database transaction using a two-phase commit protocol.

Abstract: An approach for consistent database recovery for distributed database systems uses “synchronization points”. A synchronization point is a global timestamp for which across all nodes of a distributed database system, the nodes have stored change records for any transaction occurring at and before the synchronization point in persistent logs. Each node may employ asynchronous flushing. However, on a periodic basis, each node coordinates to establish a synchronization point, which may entail ensuring change records for transactions that committed at or before the synchronization point are stored in persistent logs. In effect, a synchronization point represents that any transaction committed at or before the synchronization point has been durably committed.

Abstract: An approach for consistent database recovery for distributed database systems uses “synchronization points”. A synchronization point is a global timestamp for which across all nodes of a distributed database system, the nodes have stored change records for any transaction occurring at and before the synchronization point in persistent logs. Each node may employ asynchronous flushing. However, on a periodic basis, each node coordinates to establish a synchronization point, which may entail ensuring change records for transactions that committed at or before the synchronization point are stored in persistent logs. In effect, a synchronization point represents that any transaction committed at or before the synchronization point has been durably committed.

Abstract: A database is stored as a plurality of database shards in a distributed database grid comprising a plurality of grid elements, each including a mid-tier database system. A first grid element receives, from an application executing in the same memory as a mid-tier database system of the first grid element, a first database transaction including at least one database operation on specific data stored in a first database shard that belongs to the first grid element. The first grid element performs and commits the first database transaction without participation of another grid element of the plurality of grid elements. The first grid element receives a second database transaction that requires access to another database shard that does not belong to the first grid element. Multiple grid elements of the plurality of grid elements perform the second database transaction and commit the second database transaction using a two-phase commit protocol.

Abstract: The present invention provides a method of rendering a thin client application in a network device, for parsing the internet data so as convert the internet data into a common data format which can be rendered in set-top box using any type of middleware. The invention would be equipped to handle any type of application and also would be cost-efficient to be developed in a middleware layer of a network device like set-top box.

Abstract: The present invention provides a method of rendering a thin client application in a network device, for parsing the internet data so as convert the internet data into a common data format which can be rendered in set-top box using any type of middleware. The invention would be equipped to handle any type of application and also would be cost-efficient to be developed in a middleware layer of a network device like set-top box.

Abstract: The present invention provides a method of rendering a thin client application in a network device, for parsing the internet data so as convert the internet data into a common data format which can be rendered in set-top box using any type of middleware. The invention would be equipped to handle any type of application and also would be cost-efficient to be developed in a middleware layer of a network device like set-top box.

Abstract: The present invention provides a method of rendering a thin client application in a network device, for parsing the internet data so as convert the internet data into a common data format which can be rendered in set-top box using any type of middleware. The invention would be equipped to handle any type of application and also would be cost-efficient to be developed in a middleware layer of a network device like set-top box.