Abstract: A relational database replication system includes a client, at least one primary database, a plurality of secondary databases and replication agents which coordinate database transactions. The system provides a high level of performance, reliability, and scalability with an end result of efficient and accurate duplication of transactions between the primary and secondary databases. In one implementation, the client transmits sets of database update statements to the primary database and primary agent in parallel; the primary agent replicates the statements to at least one secondary agent. A transaction prepare and commit process is coordinated between the primary database and the primary agent, which in turn coordinates with the at least one secondary agent.

Abstract: Implementations of database systems and methods of processing database data are provided. For example, a method includes: transforming data from one or more source databases into at least one stream of data; coupling the at least one stream of data to at least one stream processing node for processing; and processing the at least one stream of data at the at least one stream processing nodes. Another method includes: writing a record to a database in an append-only log file; indexing the append-only log file; referencing a history of at least one version of an index structure, such as a key, if the record exists in the database with the same index structure; look up the record in the database by index structure of the append-only log file; and exposing an ordered queue including an order in which transactions were written in addition to using an index structure look up.

Abstract: A self-optimizing database machine is provided in which data structures are evolved (e.g., added, dropped and changed) in response to database commands received from a client at a database. Algorithms may be pushed to one or more processors located at a drive and performed in parallel (e.g., via vector or other processing) to increase operational speed of a database. New or modified database structures and/or algorithms may be compiled into object code (e.g., native low-level assembler code that can be run directly on the processor) to be executed on a processor co-located or embedded in a storage device. New or modified database structures and/or algorithms may be dynamically loaded into the chip pathways as custom gate arrays (e.g., in an FPGA) at a component of a database system (e.g., a processor co-located or embedded in a storage device storing a shard or a collection of micro-shards of a database).

Abstract: A relational database replication system includes a client, at least one primary database, a plurality of secondary databases and replication agents which coordinate database transactions. The system provides a high level of performance, reliability, and scalability with an end result of efficient and accurate duplication of transactions between the primary and secondary databases. In one implementation, the client transmits sets of database update statements to the primary database and primary agent in parallel; the primary agent replicates the statements to at least one secondary agent. A transaction prepare and commit process is coordinated between the primary database and the primary agent, which in turn coordinates with the at least one secondary agent.

Abstract: A sharded database system configured for partitioning data amongst a plurality of shard servers is provided. In one implementation the sharded database system comprises a sharded database including a first shard server, a second shard server, and a shard control record. The shard control record is configured to define a first data structure for distributing a first plurality of data records or rows based on a first sharding by monotonic key range across the first and second shard servers. The sharded database is also configured to further distribute the first plurality of records or rows across the first shard server and the second shard server via a subsidiary hashing method. A method of partitioning data of a database is also provided.

Abstract: A relational database replication system includes a client, at least one primary database, a plurality of secondary databases and replication agents which coordinate database transactions. The system provides a high level of performance, reliability, and scalability with an end result of efficient and accurate duplication of transactions between the primary and secondary databases. In one implementation, the client transmits sets of database update statements to the primary database and primary agent in parallel; the primary agent replicates the statements to at least one secondary agent. A transaction prepare and commit process is coordinated between the primary database and the primary agent, which in turn coordinates with the at least one secondary agent.

Abstract: A system and method for managing contact information is provided. In one implementation, for example, a method comprises accessing a contact record associated with a user of a user communication device, the contact record comprising at least one originating identifier identifying the user communication device and at least one contact field identifying contact information of a contact associated with the user. A contact record map is generated in which an alias identifier is assigned for the contact record. A destination identifier is selected from a plurality of available destination identifiers and assigned to the contact associated with the user. The assigned destination identifier is unique with respect to other contacts associated with the user. The alias identifier and the destination identifier are to the origination identifier identifying the user communication device within the contact record map.

Abstract: A system and method for managing contact information is provided. In one implementation, for example, a method comprises accessing a contact record associated with a user of a user communication device, the contact record comprising at least one originating identifier identifying the user communication device and at least one contact field identifying contact information of a contact associated with the user. A contact record map is generated in which an alias identifier is assigned for the contact record. A destination identifier is selected from a plurality of available destination identifiers and assigned to the contact associated with the user. The assigned destination identifier is unique with respect to other contacts associated with the user. The alias identifier and the destination identifier are to the origination identifier identifying the user communication device within the contact record map.

Abstract: A system and method for managing contact information is provided. In one implementation, for example, a method comprises accessing a contact record associated with a user of a user communication device, the contact record comprising at least one originating identifier identifying the user communication device and at least one contact field identifying contact information of a contact associated with the user. A contact record map is generated in which an alias identifier is assigned for the contact record. A destination identifier is selected from a plurality of available destination identifiers and assigned to the contact associated with the user. The assigned destination identifier is unique with respect to other contacts associated with the user. The alias identifier and the destination identifier are to the origination identifier identifying the user communication device within the contact record map.

Abstract: A system and method for managing contact information is provided. In one implementation, for example, a method comprises accessing a contact record associated with a user of a user communication device, the contact record comprising at least one originating identifier identifying the user communication device and at least one contact field identifying contact information of a contact associated with the user. A contact record map is generated in which an alias identifier is assigned for the contact record. A destination identifier is selected from a plurality of available destination identifiers and assigned to the contact associated with the user. The assigned destination identifier is unique with respect to other contacts associated with the user. The alias identifier and the destination identifier are to the origination identifier identifying the user communication device within the contact record map.

Abstract: A relational database replication system includes a client, at least one primary database, a plurality of secondary databases and replication agents which coordinate database transactions. The system provides a high level of performance, reliability, and scalability with an end result of efficient and accurate duplication of transactions between the primary and secondary databases. In one implementation, the client transmits sets of database update statements to the primary database and primary agent in parallel; the primary agent replicates the statements to at least one secondary agent. A transaction prepare and commit process is coordinated between the primary database and the primary agent, which in turn coordinates with the at least one secondary agent.

Abstract: A system and method for of identifying a semantic meaning of searchable elements are provided. In one implementation, a system includes an adaptive machine-learning module including a pattern recognition processor. The pattern recognition processor is configured to recognize searchable elements in source information and identify a semantic meaning of the searchable elements based on contingency measures of their relationships within the source information without requiring a predefined ontology of terms. In another implementation, a method includes recognizing searchable elements in source information; and identifying a semantic meaning of the searchable elements using a pattern recognition processor based on contingency measures of searchable element relationships within the source information without requiring a predefined ontology of terms.