CN103516765A - Storage method and system of social networking service background data - Google Patents
Storage method and system of social networking service background data Download PDFInfo
- Publication number
- CN103516765A CN103516765A CN201210227159.8A CN201210227159A CN103516765A CN 103516765 A CN103516765 A CN 103516765A CN 201210227159 A CN201210227159 A CN 201210227159A CN 103516765 A CN103516765 A CN 103516765A
- Authority
- CN
- China
- Prior art keywords
- dynamic message
- saved
- index
- user
- data base
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a storage method and system of social networking service background data. The method comprises the steps that when a user issues dynamic information, the entity content of the dynamic information is stored into an entity content database and is stored into an entity content cache, indexes of the dynamic information are stored into a three-category index table stored in the index database and are stored into an index cache. According to the technical scheme of the storage method and system, the problems of blocking and time delaying of the massive social networking service background data are resolved.
Description
Technical field
The present invention relates to Internet technical field, particularly the storage means of social network services back-end data and system.
Background technology
Social network services (SNS, Social Networking Services) specially refers to be intended to help people to set up the internet, applications service of social network.As instantly popular multiple social network sites, and the interpersonal relational network service that provides of other portal websites, the good friend who provides as microblogging, instantaneous communication system is related to service etc.
For this interpersonal relationships service is provided, need to preserve on backstage the dynamic message (being commonly referred to as feed) that SNS user issues, for user oneself or its good friend, mutually inquire about dynamic message.
Because SNS has obtained liking of users, its back-end data is also the order of magnitude and explodes, and easily occurs the phenomenons such as data obstruction and access time delay, and this storage to SNS back-end data has proposed challenge.
Existing a kind of SNS back-end data storage mode is as follows: be divided into feed entity stores and newsfeed storage, in feed table, institute's content of depositing and the newsfeed feedid in showing is corresponding relation.Newsfeed table is a db(database) index, there is the id of current feed the inside and sends out feed user's good friend id, if any n good friend, just has n bar record, and good friend id and useid are corresponding relations.Although this scheme only has two tables, easy to use, but there is following defect: when getting good friend feed, to first remove to inquire about associated user's friend information, will cause like this doing a step inquiry more, if data volume is large, have the phenomenons such as data obstruction and time delay, can produce corresponding database bottleneck.
Summary of the invention
In view of this, the invention provides a kind of storage means and system of social network services back-end data, to alleviate betting contest and the latency issue of the social network services back-end data of magnanimity.
For achieving the above object, technical scheme of the present invention is achieved in that
The storage means that the invention discloses a kind of social network services back-end data, the method comprises:
When user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in portion in entity content caching, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a;
Wherein, the three class concordance lists that the index of this dynamic message are saved in index data base comprise:
Together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in dynamic message concordance list;
With, together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in time shaft concordance list;
With, for each good friend of user of issue dynamic message, together with the index of this dynamic message and this good friend's user ID, be saved in distribution concordance list.
In said method, described index data base is comprised of a plurality of word banks, and the user ID span that each word bank is corresponding is different, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Describedly the index of this dynamic message is saved in to dynamic message concordance list together with user's the sign of issue dynamic message comprises: according to the user's of issue dynamic message sign, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank;
Describedly the index of this dynamic message is saved in to time shaft concordance list together with user's the sign of issue dynamic message comprises: according to the user's of issue dynamic message sign, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank;
Describedly the index of this dynamic message and this good friend's user ID are saved in to distribution concordance list together comprise: according to this good friend's user ID, find corresponding word bank, together with the index of this dynamic message and this good friend's user ID, be saved in the distribution concordance list of found word bank.
In said method, each word bank comprises a plurality of dynamic message concordance list/time shaft concordance list/distribution concordance lists corresponding to different date ranges;
Described user's the sign by the index of this dynamic message and issue dynamic message is saved in the dynamic message concordance list of found word bank together: be saved in found word bank with dynamic message concordance list corresponding to current date in;
Described user's the sign by the index of this dynamic message and issue dynamic message is saved in the time shaft concordance list of found word bank together: be saved in found word bank with time shaft concordance list corresponding to current date in;
In the described distribution concordance list that the index of this dynamic message and this good friend's user ID is saved in together to found word bank, be: be saved in found word bank with distribution concordance list corresponding to current date in.
In said method, described entity content data base comprises: our station content data base and outer station content data base;
The described entity content by this dynamic message is saved in entity content data base and comprises: if the message of this dynamic message for issuing in this social network services, its entity content is saved in our station content data base, if the message of this dynamic message for issuing in other social network services, is saved in its entity content in the content data base of outer station.
In said method, if the message of this dynamic message for issuing in other social network services, is saved in outer station content data base by its entity content and comprises: according to the time, the entity content of this dynamic message is saved in the difference table in the content data base of outer station;
The method further comprises: for the dynamic message entity content of not crossed by subsequent treatment over Preset Time in the content data base of outer station, delete, and for the dynamic message entity content of being crossed by subsequent treatment in Preset Time, transferred in the appointment table in our station content data base;
The method further comprises: by the filing storehouse of the data schedule backup in our station content data base.
The method further comprises:
For index data lab setting time delay queue, index data is first put into time delay and is lined up;
Sweep delay queue, if having data in time delay queue, fetches data in from time delay team and puts into index data base.
The invention also discloses a kind of storage system of social network services back-end data, this system comprises: entity content data base, entity content caching, index data base, indexed cache and master controller, wherein,
Master controller, for when user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in entity content caching a, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a;
Wherein, three class concordance lists in index data base are respectively: in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller, specifically for being saved in dynamic message concordance list together with user's the sign of the index of this dynamic message and issue dynamic message; With, for be saved in time shaft concordance list together with user's the sign of the index of this dynamic message and issue dynamic message; With, for each good friend of user of issue dynamic message, for be saved in distribution concordance list together with the index of this dynamic message and this good friend's user ID.
In said system, described index data base comprises a plurality of word banks, and the user ID span that each word bank is corresponding is different, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller, specifically for finding the corresponding word bank in index data base according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank; With, for find the corresponding word bank of index data base according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank; With, for each good friend who issues the user of dynamic message, for find the corresponding word bank of index data base according to this good friend's user ID, together with the index of this dynamic message and this good friend's user ID, be saved in the distribution concordance list of found word bank.
In said system, described entity content data base comprises: our station content data base and outer station content data base;
Described master controller, also for when this dynamic message is the message of issuing in this social network services, its entity content is saved in our station content data base, when this dynamic message is the message of issuing in other social network services, its entity content is saved in the content data base of outer station.
In said system, described master controller, also for being saved in the entity content of this dynamic message in the difference table of outer station content data base according to the time; Delete with the dynamic message entity content of not crossed by subsequent treatment over Preset Time being further used in the content data base of outer station, and for the dynamic message entity content of being crossed by subsequent treatment in Preset Time, transferred in the appointment table in our station content data base; With, be further used in the filing storehouse of the data schedule backup in our station content data base.
From above-mentioned, the present invention is this when user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in entity content caching a, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a; Wherein, the index of this dynamic message is saved in three class concordance lists in index data base and is specially: together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in dynamic message concordance list; With, together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in time shaft concordance list; With, for each good friend who issues the user of dynamic message, together with the index of this dynamic message and this good friend's user ID, be saved in the technical scheme in distribution concordance list, owing to all having adopted buffer memory to add the mode of database for entity content and index, therefore greatly improved reading speed, and realized the distribution of dynamic message to good friend owing to adopting three class concordance lists, therefore after good friend's login, can directly take index, get entity content, and no longer need first to go inquiring user friend information, therefore improved access speed.
Accompanying drawing explanation
Fig. 1 is the storage schematic diagram of the SNS back-end data in the embodiment of the present invention;
Fig. 2 is that data when user issues dynamic message under storage organization described in Fig. 1 are moved towards schematic diagram;
Fig. 3 is the structure chart of the storage system of a kind of social network services back-end data in the present invention.
Embodiment
The storage means that the invention provides a kind of social network services back-end data, the method comprises:
When user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in portion in entity content caching, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a; Adopt index+entity content, and the mode of buffer memory+database carries out the storage of data, wherein, the index of this dynamic message is saved in three class concordance lists in index data base and is specially:
Together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in dynamic message concordance list (newsfeed);
With, together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in time shaft concordance list (Timelines);
With, for each good friend of user of issue dynamic message, together with the index of this dynamic message and this good friend's user ID, be saved in distribution concordance list (DispatchBuddy).
This entity content and index have all adopted buffer memory to add the storage mode of database, greatly improved reading speed, and realized the distribution of dynamic message to good friend owing to adopting three class concordance lists, therefore after good friend's login, can directly take index, get entity content, and no longer need first to go inquiring user friend information, therefore improved access speed.
For an index minute storehouse submeter, store in the present invention, specifically: index data base is comprised of a plurality of word banks, the user ID span different (for example dividing according to the span of latter 2 of user ID) that each word bank is corresponding, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Like this, when index is saved in to index data base, according to user's the sign of issue dynamic message, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank; According to user's the sign of issue dynamic message, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank; Each good friend of user for issue dynamic message, finds corresponding word bank according to this good friend's user ID, together with the index of this dynamic message and this good friend's user ID, is saved in the distribution concordance list of found word bank.
In addition, if index data is too much, can also in word bank, store by submeter, specifically: each word bank is set and comprises a plurality of dynamic message concordance list/time shaft concordance list/distribution concordance lists corresponding to different date ranges;
User's the sign of the index of this dynamic message and issue dynamic message is saved in together in the dynamic message concordance list of found word bank and is: be saved in found word bank with dynamic message concordance list corresponding to current date in;
User's the sign of the index of this dynamic message and issue dynamic message is saved in together in the time shaft concordance list of found word bank and is: be saved in found word bank with time shaft concordance list corresponding to current date in;
The index of this dynamic message and this good friend's user ID are saved in together in the distribution concordance list of found word bank and are: be saved in found word bank with distribution concordance list corresponding to current date in.
In the present invention, for entity content, according to its source, divide storehouse submeter storage, specifically: entity content data base is set and comprises: our station content data base and outer station content data base; The entity content of this dynamic message is saved in entity content data base and is specially:
If the message of this dynamic message for issuing in this social network services, its entity content is saved in our station content data base, if the message of this dynamic message for issuing in other social network services, is saved in its entity content in the content data base of outer station.
For the dynamic message of issuing in other social network services, the entity content of this dynamic message is saved in the difference table in the content data base of outer station according to the time; For example, every day is with a table.
Further, for the Preset Time (as 15 days) that surpasses in the content data base of outer station, by subsequent treatment, do not crossed the dynamic message entity content of (not crossed by comment, forwarding or@) and delete, and for the dynamic message entity content of being crossed by subsequent treatment in Preset Time, transferred in the appointment table in our station content data base;
Further, by the filing storehouse of the data schedule backup in our station content data base.
For making technique scheme clearer, below in conjunction with accompanying drawing, be illustrated.
Fig. 1 is the storage schematic diagram of the SNS back-end data in the embodiment of the present invention.As shown in Figure 1, index data base is comprised of 4 groups of word banks, is respectively: index word bank one, index word bank two, index word bank three and index word bank four.Each index word bank is comprised of two equipment, one main one from, do master-slave back-up.
In the embodiment shown in fig. 1, index information is carried out to library of molecules storage by latter 2 of the user ID of 10 systems (UserID), for example the span 0 ~ 24,25 ~ 49,50 ~ 74 and 75 ~ 99 of 2 after user ID, respectively manipulative indexing word bank one to four.
In each index word bank, all store newsfeed, Timelines and DispatchBuddy tri-class concordance lists.
In the embodiment shown in fig. 1, Timelines and DispatchBuddy, being divided into by date suffix is 0 and 1 liang of cover table again, as: DispatchBuddy_0006_0, DispatchBuddy_0006_1, Timelines_0006_0, Timelines_0006_1 name, be used for depositing date in one month 1 ~ 9,9 ~ 17,17 ~ 25, the information in 25 ~ 31 4 time periods.It is in 0 Timelines and DispatchBuddy table that the index of the message that is about to 1 ~ 9 day an of middle of the month and produces for 17th ~ 25 is saved in suffix, and it is during 1 Timelines and DispatchBuddy show that the index of the message producing for 25th ~ 31 for 9th ~ 17 in a middle of the month is saved in to suffix.
In the embodiment shown in fig. 1, the buffer memory of index adopts two-server.
In the embodiment shown in fig. 1, the entity content of the dynamic message of our station, deposits our station content data base in, and by content caching in entity content caching.When preserving the entity content of dynamic message in entity content data base and entity content caching, the actual data that deposit in comprise: dynamic message sign, dynamic message entity content and issuing time, publisher, comment number, forwards the information such as number.
The dynamic message of grabbing from outer station, can deposit in the different table in the content data base of outer station by the time, every day a table, system can be in 0 automatic switchover of every day.If do not commented on, the dynamic message entity content that forwarding or@cross retains 15 days.If had in 15 days by operations such as comment, forwarding or@, this dynamic message is dumped in the DupFeedContent table of our station entity content data base, after 15 days, read commented on ,@crosses or the outer station dynamic message that forwarded, can be automatically to inquiry in DupFeedContent table.
In the embodiment shown in fig. 1, regularly (at the beginning of every month), the content in last month our station entity content data base can be dumped in filing data storehouse.
In the embodiment shown in fig. 1, the buffer memory of entity content adopts 8 redis examples of two-server.
Fig. 2 is that data when user issues dynamic message under storage organization described in Fig. 1 are moved towards schematic diagram.Referring to Fig. 2, user issues proceeding as follows when dynamic:
1, user issues feed(dynamic message) after, if our station issue can be deposited into feed entity content in our station entity content data base, and deposit in entity content caching a; If the issue of outer station can be routed to outer station entity content data base, then according to the date, be routed in the table of corresponding date, content is deposited in, and deposit in entity content caching a.
2, deposit in dynamic message concordance list, what deposit is the contents such as dynamic message sign (feedid), user ID (userid), feed type and creation-time.By user ID, be routed to one of them word bank of index word bank one to four, then by rear two corresponding tables that are routed in word bank of user ID.For example, in index word bank one, there are 25 newsfeed tables that are numbered NewsFeed_0000 ~ NewsFeed_0024, in index word bank two, there are 25 newsfeed tables that are numbered NewsFeed_0025 ~ NewsFeed_0049, in index word bank three, there are 25 newsfeed tables that are numbered NewsFeed_0050 ~ NewsFeed_0074, in index word bank four, have 25 newsfeed tables that are numbered NewsFeed_0075 ~ NewsFeed_0099.Here why with 4 bit digital as suffix, be to use for expansion from now on.Deposit in after index data base, the indexed cache of restoring is a.
3, deposit time shaft index, in concordance list, what deposit is the contents such as feedid, userid, feed type and creation-time, is mainly used for index feed entity content, is convenient to inquiry.By user userid, be routed to one of them word bank of index word bank one to four, by sum-bit current date after userid, be routed in corresponding table Timelines00xx x table again, wherein, the first two xx represents after userid two, and last x is by date, press monthly 1 ~ 9,9 ~ 17,17 ~ 25,25 ~ 31 four time periods, be divided into 0,1,0,1 four table section.Deposit in after database, the buffer memory of restoring is a.
4, deposit distribution index, by user good friend's userid, be routed to one of them storehouse of one of them word bank of index word bank one to four, then be routed in corresponding table DispatchBuddy_00xx_x table by sum-bit current date after this userid, wherein, the first two xx represents after userid two, and last position is by date 1 ~ 9,9 ~ 17,17 ~ 25,25 ~ 31, be divided into 0,1,0,1 four sections.Deposit in after database, the buffer memory of restoring is a.
5, wherein index word bank one to four is rear 2 digit separators by userid, and concrete subregion is the scope of latter 20 ~ 24,25 ~ 49,50 ~ 74,75 ~ 99 of userid, respectively manipulative indexing word bank one, two, three and four.
6, because outer station content only retains 15 days, if comment, forwarding, collection or@stand, capture the feed coming outward, can first this feed be dumped to the DupFeedContent table in our station content data base, in case inquire about less than operations such as related commentary after 15 days.
7, be index data lab setting time delay queue, index data is first put into time delay and is lined up; Sweep delay queue, if having data in time delay queue, fetches data in from time delay team and puts into index data base.
While being index content persistence, adopted time delay queue to store in batches.So-called time delay queue stores is set up Yi Ge queue structure in java virutal machine memory, and the index data of coming is not first put in storage, but is introduced into queue.Service can be enabled a thread after starting simultaneously, and ceaselessly scan queue, if the value in queue is greater than zero, can fetch data from queue, is inserted in database.This function, is for when data volume is excessive, the data insertion pressure of alleviation database.When mass data pours in, can carry mass data by queue, prevent database to collapse under pressure, reach the object of trading space for time
For example: the good friend user B of user A on May 24th, 2012 16:16 issued one dynamically, idiographic flow is:
A) in our station content data base, insert a feed content record, deposit in entity content caching a simultaneously.
B) according to latter two of the 10 system numbers of the userid of user B, be routed to relevant index data base.If the userid=90098743 of user B,, according to latter two 43, can be routed to index word bank two, then according to 43, index content is inserted in NewsFeed_0043 table, and deposits in indexed cache simultaneously.
C) simultaneously, at index word bank two, according to current date, be routed to relevant timelines table.As being today No. 24, can insert an index record at Timelines_00430 table, deposit a in indexed cache simultaneously.
D) same method operation dispatchbuddy table, because this table is the concordance list that is distributed to good friend, to carry out route according to the userid of good friend A, if the userid=100092357 of A, can be routed to index word bank three, according to No. 25, userid and current date, at DispatchBuddy_0057_0 table, insert an index record, in indexed cache, preserve a simultaneously.Other good friends of user B successively method are carried out to corresponding operation.
As the good friend of user B, after user A login, can directly in dispatchbuddy table, find good friend's issue like this.
Fig. 3 is the structure chart of the storage system of a kind of social network services back-end data in the present invention.As shown in Figure 3, this system comprises: entity content data base 31, entity content caching 32, index data base 33, indexed cache 34 and master controller 35, wherein,
Wherein, three class concordance lists in index data base 33 are respectively: in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller 35, for being saved in dynamic message concordance list together with user's the sign of the index of this dynamic message and issue dynamic message; With, together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in time shaft concordance list; With, for each good friend of user of issue dynamic message, together with the index of this dynamic message and this good friend's user ID, be saved in distribution concordance list.
In said system, index data base 33 comprises a plurality of word banks, and the user ID span that each word bank is corresponding is different, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller 35, for find the corresponding word bank of index data base 33 according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank; With, for find the corresponding word bank of index data base according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank; With, for each good friend who issues the user of dynamic message, for find the corresponding word bank of index data base according to this good friend's user ID, together with the index of this dynamic message and this good friend's user ID, be saved in the distribution concordance list of found word bank.
In said system, entity content data base 31 comprises: our station content data base and outer station content data base;
From above-mentioned, technical scheme of the present invention, owing to all having adopted buffer memory to add the mode of database for entity content and index, therefore greatly improved reading speed, and owing to adopting three class concordance lists to realize the distribution of dynamic message to good friend, so can directly take index after good friend's login, get entity content, and no longer need first to go inquiring user friend information, therefore improved access speed.And all feed entity contents are only stored 1 part, have saved in a large number space, the mode that time delay queue is stored has in batches been alleviated the pressure of database.
The foregoing is only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.All any modifications of doing within the spirit and principles in the present invention, be equal to replacement, improvement etc., be all included in protection scope of the present invention.
Claims (10)
1. a storage means for social network services back-end data, is characterized in that, the method comprises:
When user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in portion in entity content caching, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a;
Wherein, the three class concordance lists that the index of this dynamic message are saved in index data base comprise:
Together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in dynamic message concordance list;
With, together with user's the sign of the index of this dynamic message and issue dynamic message, be saved in time shaft concordance list;
With, for each good friend of user of issue dynamic message, together with the index of this dynamic message and this good friend's user ID, be saved in distribution concordance list.
2. method according to claim 1, is characterized in that, described index data base is comprised of a plurality of word banks, and the user ID span that each word bank is corresponding is different, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Describedly the index of this dynamic message is saved in to dynamic message concordance list together with user's the sign of issue dynamic message comprises: according to the user's of issue dynamic message sign, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank;
Describedly the index of this dynamic message is saved in to time shaft concordance list together with user's the sign of issue dynamic message comprises: according to the user's of issue dynamic message sign, find corresponding word bank, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank;
Describedly the index of this dynamic message and this good friend's user ID are saved in to distribution concordance list together comprise: according to this good friend's user ID, find corresponding word bank, together with the index of this dynamic message and this good friend's user ID, be saved in the distribution concordance list of found word bank.
3. method according to claim 1, is characterized in that, each word bank comprises a plurality of dynamic message concordance list/time shaft concordance list/distribution concordance lists corresponding to different date ranges;
Described user's the sign by the index of this dynamic message and issue dynamic message is saved in the dynamic message concordance list of found word bank together: be saved in found word bank with dynamic message concordance list corresponding to current date in;
Described user's the sign by the index of this dynamic message and issue dynamic message is saved in the time shaft concordance list of found word bank together: be saved in found word bank with time shaft concordance list corresponding to current date in;
In the described distribution concordance list that the index of this dynamic message and this good friend's user ID is saved in together to found word bank, be: be saved in found word bank with distribution concordance list corresponding to current date in.
4. method according to claim 1, is characterized in that, described entity content data base comprises: our station content data base and outer station content data base;
The described entity content by this dynamic message is saved in entity content data base and comprises: if the message of this dynamic message for issuing in this social network services, its entity content is saved in our station content data base, if the message of this dynamic message for issuing in other social network services, is saved in its entity content in the content data base of outer station.
5. method according to claim 4, it is characterized in that, if the message of this dynamic message for issuing in other social network services, is saved in outer station content data base by its entity content and comprises: according to the time, the entity content of this dynamic message is saved in the difference table in the content data base of outer station;
The method further comprises: for the dynamic message entity content of not crossed by subsequent treatment over Preset Time in the content data base of outer station, delete, and for the dynamic message entity content of being crossed by subsequent treatment in Preset Time, transferred in the appointment table in our station content data base;
The method further comprises: by the filing storehouse of the data schedule backup in our station content data base.
6. according to the method described in any one in claim 1-5, it is characterized in that, the method further comprises:
For index data lab setting time delay queue, index data is first put into time delay and is lined up;
Sweep delay queue, if having data in time delay queue, fetches data in from time delay team and puts into index data base.
7. a storage system for social network services back-end data, is characterized in that, this system comprises: entity content data base, entity content caching, index data base, indexed cache and master controller, wherein,
Master controller, for when user issues dynamic message, the entity content of this dynamic message is saved in entity content data base, and be saved in entity content caching a, the index of this dynamic message is saved in three class concordance lists in index data base, and is saved in indexed cache a;
Wherein, three class concordance lists in index data base are respectively: in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller, specifically for being saved in dynamic message concordance list together with user's the sign of the index of this dynamic message and issue dynamic message; With, for be saved in time shaft concordance list together with user's the sign of the index of this dynamic message and issue dynamic message; With, for each good friend of user of issue dynamic message, for be saved in distribution concordance list together with the index of this dynamic message and this good friend's user ID.
8. system according to claim 7, is characterized in that, described index data base comprises a plurality of word banks, and the user ID span that each word bank is corresponding is different, and each word bank comprises in dynamic message concordance list, time shaft concordance list and distribution concordance list;
Described master controller, specifically for finding the corresponding word bank in index data base according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the dynamic message concordance list of found word bank; With, for find the corresponding word bank of index data base according to user's the sign of issue dynamic message, together with the index of this dynamic message and the user's of issue dynamic message sign, be saved in the time shaft concordance list of found word bank; With, for each good friend who issues the user of dynamic message, for find the corresponding word bank of index data base according to this good friend's user ID, together with the index of this dynamic message and this good friend's user ID, be saved in the distribution concordance list of found word bank.
9. system according to claim 7, is characterized in that, described entity content data base comprises: our station content data base and outer station content data base;
Described master controller also for: this dynamic message in this social network services, issue message time, its entity content is saved in our station content data base, when this dynamic message is the message of issuing in other social network services, its entity content is saved in the content data base of outer station.
10. system according to claim 9, is characterized in that,
Described master controller, also for being saved in the entity content of this dynamic message in the difference table of outer station content data base according to the time; Delete with the dynamic message entity content of not crossed by subsequent treatment over Preset Time being further used in the content data base of outer station, and for the dynamic message entity content of being crossed by subsequent treatment in Preset Time, transferred in the appointment table in our station content data base; With, be further used in the filing storehouse of the data schedule backup in our station content data base.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210227159.8A CN103516765B (en) | 2012-06-30 | 2012-06-30 | Storage method and system of social networking service background data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210227159.8A CN103516765B (en) | 2012-06-30 | 2012-06-30 | Storage method and system of social networking service background data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103516765A true CN103516765A (en) | 2014-01-15 |
| CN103516765B CN103516765B (en) | 2017-05-17 |
Family
ID=49898791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210227159.8A Active CN103516765B (en) | 2012-06-30 | 2012-06-30 | Storage method and system of social networking service background data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103516765B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105512135A (en) * | 2014-09-25 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Method and system for processing Internet user published information |
| CN105989060A (en) * | 2015-02-09 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Data management method and device |
| CN106227819A (en) * | 2016-07-22 | 2016-12-14 | 乐视控股（北京）有限公司 | A kind of method and device obtaining comment data |
| CN109684363A (en) * | 2018-12-26 | 2019-04-26 | 百度在线网络技术（北京）有限公司 | The polymorphic material processing method of multiterminal, device, server and storage medium |
| CN112861016A (en) * | 2020-12-11 | 2021-05-28 | 深圳市蟠桃树科技有限公司 | Data high-concurrency processing method of Feed stream system of healthy social platform |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090234814A1 (en) * | 2006-12-12 | 2009-09-17 | Marco Boerries | Configuring a search engine results page with environment-specific information |
| CN102387092A (en) * | 2010-09-06 | 2012-03-21 | 腾讯科技（深圳）有限公司 | Method and device for managing message |
-
2012
- 2012-06-30 CN CN201210227159.8A patent/CN103516765B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090234814A1 (en) * | 2006-12-12 | 2009-09-17 | Marco Boerries | Configuring a search engine results page with environment-specific information |
| CN102387092A (en) * | 2010-09-06 | 2012-03-21 | 腾讯科技（深圳）有限公司 | Method and device for managing message |
Non-Patent Citations (2)
| Title |
|---|
| MARS914: "新浪微博技术架构分析", 《HTTP://MARS914.ITEYE.COM/BLOG/1218492》 * |
| 黎瑞瑜: "分布式实时分发微博系统", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105512135A (en) * | 2014-09-25 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Method and system for processing Internet user published information |
| CN105512135B (en) * | 2014-09-25 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Method and system for processing information issued by internet user |
| CN105989060A (en) * | 2015-02-09 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Data management method and device |
| CN106227819A (en) * | 2016-07-22 | 2016-12-14 | 乐视控股（北京）有限公司 | A kind of method and device obtaining comment data |
| CN109684363A (en) * | 2018-12-26 | 2019-04-26 | 百度在线网络技术（北京）有限公司 | The polymorphic material processing method of multiterminal, device, server and storage medium |
| CN112861016A (en) * | 2020-12-11 | 2021-05-28 | 深圳市蟠桃树科技有限公司 | Data high-concurrency processing method of Feed stream system of healthy social platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103516765B (en) | 2017-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102411637B (en) | Metadata management method of distributed file system | |
| CN103853714B (en) | A kind of data processing method and device | |
| CN104346458B (en) | Date storage method and storage device | |
| CN105138571B (en) | Distributed file system and method for storing massive small files | |
| CN104407879B (en) | A kind of power network sequential big data loaded in parallel method | |
| CN103516765A (en) | Storage method and system of social networking service background data | |
| CN102833298A (en) | Distributed repeated data deleting system and processing method thereof | |
| CN102567495A (en) | Mass information storage system and implementation method | |
| CN103399945A (en) | Data structure based on cloud computing database system | |
| CN102541985A (en) | Organization method of client directory cache in distributed file system | |
| CN104134173A (en) | Main and distribution network graph/model/data integrated system based on remote retrieval and information interaction | |
| CN106909595A (en) | A kind of data migration method and device | |
| CN105159845A (en) | Memory reading method | |
| CN107783980A (en) | Index data generates and data query method and device, storage and inquiry system | |
| CN101923571B (en) | Method and device for managing terminal data logging | |
| WO2013143278A1 (en) | Method, device and system for querying data index | |
| CN104834700A (en) | Method for capturing movement data increment based on track change | |
| CN104536908B (en) | A kind of magnanimity small records efficient storage management method towards unit | |
| CN106777387A (en) | A kind of Internet of Things big data access method based on HBase | |
| CN104008199A (en) | Data inquiring method | |
| CN104504030A (en) | Indexing method for power dispatching automation mass messages | |
| CN101534477A (en) | List item management method and device | |
| CN107291881A (en) | Massive logs storage and querying method based on HBase | |
| CN103902693A (en) | Method of read-optimized memory database T-tree index structure | |
| CN105912696A (en) | DNS (Domain Name System) index creating method and query method based on logarithm merging |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP02 | Change in the address of a patent holder |
Address after: Room 810, 8 / F, 34 Haidian Street, Haidian District, Beijing 100080 Patentee after: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. Address before: 100089 Beijing city Haidian District wanquanzhuang Road No. 28 Wanliu new building 6 storey block A room 602 Patentee before: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder |