Abstract:
The invention discloses a method for storing data and a device of implementing the same. The method comprises receiving a request for storing data sent by a user and storing the data to an SSD according to the received request. The device comprises a request receiving module used to receive the request storing data and an SSD storage module used to store the data to an SSD according to the received request. The invention ensures consistency of data storage by storing data to an SSD according to the received request, thereby reducing data redundancy caused by using a cache layer to cache the data in the prior art. Additionally, the use of a single layer of an SSD to store data avoids the need of reloading data in the cache layer once a machine is power-down, thereby reducing the complexity of system design and the cost of operation and maintenance.
Abstract:
The present disclosure relates to a common message sending method, an electronic device, and a non-transitory storage medium. According to user numbers on a platform, followers of a first user are acquired to construct a first subset, followers of a second user are acquired to construct a second subset. Common followers in the first subset and the second subset are acquired. A common message is sent to the common followers. The present disclosure further relates to an electronic device and a non-transitory storage medium. The common message sending method, the electronic device, and the storage medium according to the present disclosure achieve efficient, fast sending of a common message by massive, comparison of followers to send a common message.
Abstract:
Method, system and device for acquiring directionally published microblog messages are disclosed. A first client acquires an instruction for reading a microblog message from a first user, wherein the instruction comprises a keyword of the first user; the first client extracts directionally published microblog messages matching with the keyword of the first user from an outbox of a second user, wherein the second user is followed the first user and has a directional publishing authority; and the first terminal displays the extracted directionally published microblog messages to the first user. Through the solutions provided the present disclosure, a first user only needs to access an outbox of a second user for acquiring a microblog message, and thus the first user does not need to delete the microblog message. The operation of the first user is simplified, and thereby the user experience will be improved.
Abstract:
Provided are a method for synchronization of UGC master and backup data and a system there of, and a computer storage medium. The method includes the steps of: determining, when performing data synchronization of a master storage site and a backup site of UGC data, whether a version identifier stored satisfies a predetermined full synchronization condition, the version identifier corresponding to UGC data update of each user identifier in the master storage site; acquiring, when it is determined that the version identifier stored satisfies the predetermined full synchronization condition, from the master storage site full amount of UGC data corresponding to the user identifier, and synchronizing the UGC data to the backup site; otherwise, acquiring from the master storage site the UGC update data corresponding to the user identifier, and synchronizing the UGC update data to the backup site. By the method and system, synchronization consistency of the UGC master and backup data is realized, and the synchronization data will not occupy excessive communication resources; thereby the influence of UGC data expansion on the synchronization efficiency is relatively low.
Abstract:
A data synchronization method for a multi-level associative storage architecture includes: receiving, by a master module, a request of an external write operation, writing data into a write buffer of the master module, and recording a digit sequence according to the write operation on the write buffer of the master module; flushing data from the write buffer to solid-state disk (SSD) files when a data amount in the write buffer of the master module reaches a threshold; recording, by the master module, a digit sequence for a flush operation; separately synchronizing, by the master module, the write operation and the flush operation to a slave module according to orders of digits in different digit sequences; and receiving, by the slave module, the synchronous write operation and synchronous flush operation, and separately synchronizing the data of the master module to corresponding locations of a local write buffer and local SSD files.
Abstract:
A method and apparatus for releasing services on a server in stages is provided, the method comprising setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and releasing the new service to the entire server in a third time period. In accordance with the method and apparatus for releasing services on a server in stages in this embodiment, new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Abstract:
A method and a system for data migration are described, the method for data migration including: slicing data in an original system to obtain a data slice; importing the data slice into a new system; and redoing, in the new system, respective data corresponding to at least one pre-recorded write request according to a sequence number order of the at least one pre-recorded write request, wherein the at least one pre-recorded write request above is to simultaneously write to both the original system and the new system. In the method and the system, data in an original system can be seamlessly imported to a new system without forbidding writes to the original system, and the data in the new system can be recovered to the latest by a redo technique. Without any awareness of users, the data migration can be achieved in the background.
Abstract:
A data synchronization method is provided. The data synchronization method includes providing a first server with a master flag and a write flag for a data block; providing a second server; and importing a snapshot of the data block to the second server. The method further includes configuring a synchronizing flag for the data block on the second server; synchronizing, by a synchronizing component, data of the data block on the first server to the second server; and removing the write flag of the data block on the first server when the data block is to be migrated out of the first server. The method also includes synchronizing, by the synchronizing component, latest data of the data block on the first server to the second server; removing the master flag of the data block on the first server and removing the synchronizing flag of the data block on the second server after data of the data block on the second server and the data of the data block on the first server are completely synchronized; and configuring a master flag and a write flag for the data block on the second server.
Abstract:
An invitation information push method includes after receiving an invitation request sent by a microblog user, a server sending invitation information to a number of clients corresponding to invited users carried in the invitation request, wherein the invited users are users who have not registered microblog, and the number of the invited users N is greater than or equal to 1. Each client, upon receiving the invitation information, creating an invitation information guide to guide the users who have not registered the microblog to register the microblog. The method further comprises, when a predetermined time is reached, a server actively sending invitation information to at least one client corresponding to at least one user who has not registered the microblog.
Abstract:
Devices and methods are provided for sending messages. For example, a receiving user list corresponding to a specific message to be sent is acquired; a first timeline refresh request associated with a first receiving user in the receiving user list is received; and upon the capture of the first timeline refresh request, the specific message is sent to a client associated with the first receiving user that refreshes a timeline.