×

Synchronous data replication in a content management system

  • US 10,169,440 B2
  • Filed: 01/27/2014
  • Issued: 01/01/2019
  • Est. Priority Date: 01/27/2014
  • Status: Active Grant
First Claim
Patent Images

1. A computer program product for data replication during ingestion of data in a content management system, the computer program product comprising a non-transitory computer readable storage medium having program code embodied therewith, the program code being executable by a processor to:

  • receive, by the processor and in response to instructions by an application programming interface, blocks of data to be written into a content management system;

    retrieve a replication rule from a replication rule repository, wherein the replication rule includes instructions for handling the blocks of data in a strict mode and in a tolerant mode, respectively;

    replicate the blocks of data to different live replication nodes in the content management system using the strict mode in situations that require strict data consistency and no data losses in response to writing the blocks of data to the first node in the content management system by the processor and in response to instructions by the application programming interface, wherein the strict mode requires that the blocks of data be persisted synchronously to the first node and all its replica nodes before the data node returns a success status;

    replicate the blocks of data to different live replication nodes in the content management system using the tolerant mode in situations that require high throughput and high availability in data ingestion, in response to writing the blocks of data to the first node in the content management system by the processor and in response to instructions by the application programming interface, wherein the tolerant mode requires that the blocks of data be persisted synchronously to a user-assigned number of replica nodes of the first data node before the first data node returns a success status and the data blocks be asynchronously persisted to any failed data nodes at a later point in time; and

    receive either a success status or a failure status for persisting the data in the content management system.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×