JP4921570B2 - Blog service providing system, method and program - Google Patents

Description

  The present invention relates to a blog service providing system, method, and program for providing a blog service to a user.

  In recent years, with the spread of the Internet and the improvement of search technology, users can easily obtain various contents from the Internet. In addition, the user not only obtains information desired to be obtained through the Internet, but also allows the user to send information through the Internet. As a typical method for a user to transmit information through the Internet, a blog (abbreviation of web log) can be cited.

The blog is updated when a user connects to a website of a system that provides a blog service using a browser of a terminal and uploads text data such as a diary and image data such as a photograph to the system. In addition, the blog is composed of a plurality of component data constituting the blog page. Whenever there is a browsing request from the terminal, the server providing the blog service reads each component from a database or the like and transmits it to the terminal that requested the browsing so that it can be configured as a Web page. For this reason, it takes time until the server providing the blog service receives the browsing request and transmits the blog page.
Therefore, an apparatus is disclosed that caches each part page (part data), reconfigures the cached part page into one page, and transmits the page to the terminal (for example, Patent Document 1).

JP 2006-227671 A

In Patent Document 1, a server device temporarily stores a component page constituting a Web page as a cache, and when the requested Web page includes a cached component page, the component page is re-executed. It is disclosed that a web page is configured by using it. However, in the case of a blog system, different parts are often used for each blog creator, and there are few Web pages on which parts can be reused.
The part data constituting the blog includes not only text but also image data, moving image data, a program for performing a predetermined operation, and the like. And when displaying a blog consisting of multiple parts, every time a blog page request is made, if these parts that are not cached are read and configured, the blog requested to be browsed after receiving the browse request It does not change that it takes time to compose and send a page.

  Therefore, an object of the present invention is to provide a blog service providing system, method, and program capable of improving response performance.

  (1) Component data storage means for storing component data relating to a Web page composed of a plurality of components, a front-end server that generates and transmits the Web page in response to a request from a user terminal or a handler, A blog service providing system comprising: a cache server that caches data necessary for creation, wherein the cache server is a unit part data that includes a plurality of part data used for configuring the Web page as a unit First cache means for temporarily storing the second cache means for temporarily storing the component data, and the front-end server receives a Web page browsing request from the user terminal or the handler. Request accepting means to accept and before relating to the web page browsing request When the unit part data is stored in the first cache unit, the unit part data is acquired. When the unit part data is not stored in the first cache unit, the second cache unit is acquired. Alternatively, part data acquisition means for acquiring the part data stored in the part data storage means, and page creation for generating the Web page based on the unit part data or the part data acquired by the part data acquisition means A blog service providing system comprising: means; and transmitting means for transmitting the Web page created by the page creating means to the user terminal or the handler.

  According to the configuration described in (1), when the front-end server receives a web page browsing request, the unit part data with a plurality of parts data as one unit is acquired, and when there is no unit part data, Acquire component data and create a Web page. First, since the unit part data composed of a plurality of part data is read in advance to create a Web page, the response performance can be improved as compared to reading each part data and creating a Web page.

  (2) The front-end server, when the component data acquisition unit acquires a plurality of the component data from the second cache unit or the component data storage unit, The blog service providing system according to (1), further comprising: cache generating means for registering in the first cache means.

  According to the configuration described in (2), in addition to the configuration described in (1), the front-end server does not have unit component data in the first cache unit, and the plurality of units from the second cache unit or the component data storage unit. Even when a web page is created by reading component data, a plurality of component data read at that time can be registered as unit component data. For this reason, when the browsing request for the same Web page is received again, the unit component data is generated, so that the response speed can be made faster than the previous browsing request.

  (3) The blog service providing system according to (1) or (2), wherein the unit part data includes layout information related to a plurality of the part data constituting the unit part data.

  According to the configuration described in (3), in addition to the configuration described in (1) or (2), the unit part data includes layout information. Therefore, the front-end server can create a Web page simply by reading unit part data.

  (4) The blog service providing system includes a database server that stores the component data, and the database server includes the component data storage unit. (1) to (3) .

  According to the configuration described in (4), in addition to the configuration described in any one of (1) to (3), the blog service providing system includes a database server having component data storage means for configuring component data. .

  (5) Component data storage means for storing component data relating to a Web page composed of a plurality of components, a front-end server that generates and transmits the Web page in response to a request from a user terminal or a handler, A blog service providing a blog service, wherein the cache server uses a plurality of component data used for configuring the Web page as a unit. A step of temporarily storing unit component data, a step in which the cache server temporarily stores the component data, and a step in which the front-end server receives a Web page browsing request from the user terminal or the handler And the front-end server browses the Web page When the unit part data related to the request is temporarily stored, the unit part data is acquired, and when the unit part data is not temporarily stored, the unit part data is temporarily stored. Acquiring the component data or the component data stored in the component data storage means, and creating the Web page based on the acquired unit component data or the component data by the front-end server. And the front-end server transmitting the created web page to the user terminal or the handler.

  According to the configuration described in (5), it is possible to provide a method capable of producing the same effect as in (1).

  (6) Component data storage means for storing component data relating to a Web page composed of a plurality of components, a front-end server that generates and transmits the Web page in response to a request from a user terminal or handler, A cache server that caches data necessary for creation, the program providing the blog service to the front-end server and the cache server, the cache server being used to create the web page A first cache unit that temporarily stores unit component data having a plurality of component data as a unit; and the cache server that functions as a second cache unit that temporarily stores the component data. End server from the user terminal or the handler When the unit part data related to the web page browsing request and the unit part data related to the web page browsing request are stored in the first cache unit, the unit part data is acquired, and the unit part data Is not stored in the first cache unit, the component data acquisition unit that acquires the component data stored in the second cache unit or the component data storage unit, and the component data acquisition unit acquires And functioning as page creation means for creating the web page based on the unit part data or the part data, and transmission means for sending the web page created by the page creation means to the user terminal or the handler. Program for.

  According to the configuration described in (6), it is possible to provide a program capable of producing the same effect as in (1).

  ADVANTAGE OF THE INVENTION According to this invention, the blog service provision system, method, and program which can improve response performance can be provided.

It is a figure which shows the whole structure and functional structure of the blog service provision system which concerns on embodiment of this invention. It is a figure which shows the concept of the unit component data which concern on embodiment of this invention. It is a figure which shows the example of the data stored in the 1st cache part which concerns on embodiment of this invention. It is a figure which shows the example of the data stored in the 2nd cache part which concerns on embodiment of this invention. It is a figure which shows the example of the data stored in components data DB which concerns on embodiment of this invention. It is a figure which shows the example of the data stored in layout information DB which concerns on embodiment of this invention. It is a figure which shows the flow which shows the flow of a process of the front end server which concerns on embodiment of this invention, a cache server, and DB server. It is a flowchart which shows the flow of a process of the front end server which concerns on embodiment of this invention, a cache server, and DB server.

  Embodiments of the present invention will be described below with reference to the drawings. The embodiment described below is merely an example, and the technical scope of the present invention is not limited to this.

With reference to FIG. 1, an overall configuration of a blog service providing system 1 and an exemplary configuration of each unit, which is an example of the present embodiment, will be described.
FIG. 1 is a diagram showing an overall configuration and functional configuration of a blog service providing system 1 according to an embodiment of the present invention.

  The blog service providing system 1 is a system that provides a service that creates a blog page that can be edited by the user of the user terminal 40 and publishes it on the communication network N in response to a browsing request from the user terminal 40. The blog service providing system 1 can communicate with the user terminal 40 through the communication network N.

  The user terminal 40 is connected to the blog service providing system 1 via a communication network N by a web browser, and is a web page (blog page) described in HTML (HyperText Markup Language) language, XML (extensible Markup Language) language, or the like. Download information. Then, the user terminal 40 analyzes and displays these languages. Examples of the user terminal 40 include an information terminal having a communication function such as a personal computer (PC), a mobile phone, and a PDA (Personal Digital Assistants). The user terminal 40a shown in FIG. 1 is a so-called personal computer, and the user terminal 40b is a mobile terminal such as a mobile phone (hereinafter collectively referred to as the user terminal 40). In FIG. 1, one user terminal 40 a and 40 b are shown, but a plurality of user terminals 40 a and 40 b may be provided.

  The communication network N is formed by a wired communication network (public line network) such as an optical fiber or an ADSL (Asymmetric Digital Subscriber Line), or a mobile (wireless) communication network such as a mobile phone, PHS, or wireless LAN. Specifically, the communication network N is configured by a computer network such as a LAN (Local Area Network) or the Internet.

  The blog service providing system 1 includes a blog providing server 10, a cache server 20, a front-end server 30, and a database server 50 (hereinafter referred to as a DB server 50).

  The blog providing server 10 manages processing performed in the blog service providing system 1 such as receiving a request for creating a new blog page from the user terminal 40 or managing a user who uses the blog service providing system 1. Do.

  The cache server 20 temporarily stores (caches) unit component data or component data that has been requested from the front-end server 30 in the past. In response to a request from the front end server 30, the cache server 20 reads the cached unit part data or part data and transmits it to the front end server 30.

  The cache server 20 includes at least a first cache unit 21 and a second cache unit 22. The first cache unit 21 temporarily stores unit component data that was previously displayed as a blog page.

Here, the unit component data will be described with reference to FIG. FIG. 2 is a diagram showing the concept of unit part data according to the embodiment of the present invention.
The unit component data is data in which a plurality of component data included in a Web page previously displayed as a blog page is a unit. In the present embodiment, as shown in FIG. 2, the unit part data is a Web made up of all part data 61, 62, 63, 64, 65 and layout information 60 included in the blog page displayed on the user terminal 40. This is page unit data. Therefore, when the first component data acquisition unit 342 described later acquires unit component data, the front-end server 30 can display the Web page on the user terminal 40 using only the unit component data.

With reference to FIG. 3, the unit component data stored in the first cache unit 21 will be described. FIG. 3 is a diagram showing an example of a table stored in the first cache unit 21 according to the embodiment of the present invention.
The first cache unit 21 stores a user ID, unit component data, and registration time in a “user ID” column, a “unit component data” column, and a “registration time” column, respectively. The user ID is the user ID of the blog page stored as unit part data. The registration time is the time when the unit component data is stored in the first cache unit 21. The unit component data stored in the first cache unit 21 is erased from the first cache unit 21 when a predetermined period has elapsed from the time registered as the cache time.

  Returning to FIG. 1, the second cache unit 22 temporarily stores the component data previously displayed on the blog page. Here, the component data stored in the second cache unit 22 will be described with reference to FIG. FIG. 4 is a diagram showing an example of a table stored in the second cache unit 22 according to the embodiment of the present invention.

The second cache unit 22 stores user ID, component data, component data type, and registration time data in a “user ID” column, a “component data” column, a “type” column, and a “registration time” column, respectively. Has been. The component data is data that forms a part of a certain Web page. This component data includes, for example, advertisement data displayed on a Web page, tools such as a calendar, scripts for causing a dynamic display on a Web page such as a counter and a clock, and texts such as articles on a blog This is data of content that can be displayed on a Web page, such as data, images such as photographs, or moving image data.
The type of component data is information indicating what type of data the component data is, as described above.

  The registration time is the time when the component data is stored in the second cache unit 22. Then, the component data stored in the second cache unit 22 is deleted from the second cache unit 22 when a predetermined period has elapsed from the time registered as the registration time. This predetermined period may be longer than the “predetermined period” in the first cache unit 21. As a result, even if the unit part data is erased after a predetermined period from the registration time in the first cache unit 21, the part data constituting the erased unit part data is still stored in the second cache unit 22. There may be a cached state. For this reason, even when a browsing request is made for the Web page of the unit component data deleted from the first cache unit 21, the Web page can be configured from the component data cached in the second cache unit 22, so that it is quick. Response performance can be realized.

Returning to FIG. 1, the front-end server 30 will be described.
The front-end server 30 creates a blog page in response to a blog page browsing request from the user terminal 40 or a blog page acquisition request from an existing blog system handler such as the blog providing server 10. Then, the front-end server 30 transmits the created blog page to the user terminal 40 or the blog providing server 10.

  The front end server 30 includes at least a storage unit 31, a display unit 32, an operation unit 33, and a control unit 34.

  The storage unit 31 is a non-volatile memory such as a hard disk device, a magneto-optical disk device, or a flash memory, a volatile memory such as a RAM (Random Access Memory), or a computer-readable and writable storage using a combination thereof. It shall consist of media.

  The display unit 32 displays a screen for accepting data input to the administrator of the front-end server 30 or displays a screen of a result of calculation processing by the front-end server 30. The display unit 32 is a cathode ray tube display (CRT), A display device such as a liquid crystal display (LCD) is included.

  The operation unit 33 receives input to the front end server 30 and is configured by a keyboard, a mouse, a touch pen, a touch panel, and the like.

The control unit 34 controls the execution of each process of the front end server 30. The control unit 34 includes a CPU (Central Processing Unit) and the like. The control unit 34 may realize a function by reading a program for realizing the function of each unit below into a memory (not shown) and executing the program, or by using dedicated hardware. It may be realized.
Note that the blog providing server 10 and the cache server 20 described above can also have the same hardware configuration of the control unit, the storage unit, the display unit, and the operation unit as the front end server 30.

  The control unit 34 includes a request reception unit 341, a first component data acquisition unit 342, a second component data acquisition unit 343, a cache generation unit 344, a page generation unit 345, and a page transmission unit 346.

  The request reception unit 341 is a handler for a browsing request for the blog page from the user terminal 40 or an acquisition request for the blog page from the blog providing server 10 (for example, an HTTP handler (HyperText Transfer Protocol)) (hereinafter referred to as a user terminal). 40 or a request from the blog providing server 10). The request from the user terminal 40 or the blog providing server 10 includes URL and user ID data of the blog page requested to be browsed. The request reception unit 341 outputs various data included in the request from the user terminal 40 or the blog providing server 10 to the first component data acquisition unit 342.

  The first component data acquisition unit 342 transmits an acquisition request for unit component data to the cache server 20 in response to input of information included in the request from the request reception unit 341. Then, when receiving the unit part data from the cache server 20, the first part data acquisition unit 342 outputs the received unit part data to the page generation unit 345. When the first part data acquisition unit 342 does not receive the unit part data from the cache server 20, the first part data acquisition unit 342 outputs information included in the request input from the request reception unit 341 to the second part data acquisition unit 343.

  The second component data acquisition unit 343 transmits a component data acquisition request to the cache server 20 or the DB server 50 in response to input of information included in the request from the first component data acquisition unit 342. The second component data acquisition unit 343 first transmits a component data acquisition request to the cache server 20. Then, when there is no corresponding component data in the second cache unit 22 of the cache server 20, the second component data acquisition unit 343 transmits a component data acquisition request to the DB server 50. When receiving the component data and the layout information from the cache server 20 or the DB server 50, the second component data acquisition unit 343 outputs the received component data and the layout information to the cache generation unit 344.

  In response to the input of the component data and the layout information from the second component data acquisition unit 343, the cache generation unit 344 generates unit component data from these data and transmits the unit component data to the cache server 20, thereby The cache unit 21 caches (temporarily stores). The cache server 20 stores the unit component data in the table of the first cache unit 21 together with the registration time. When the second component data acquisition unit 343 acquires component data and layout information from the DB server 50 described later, the cache generation unit 344 transmits these data to the cache server 20 as component data. The second cache 22 is cached.

  When the unit component data is input from the first component data acquisition unit 342, the page generation unit 345 outputs the input unit component data to the page transmission unit 346 as a blog page. Further, when the part data and the layout information are input from the second part data acquisition unit 343, the page generation unit 345 generates a blog page based on the part data and the layout information and outputs the blog page to the page transmission unit 346. To do.

  The page transmission unit 346 transmits the request to the blog providing server 10 or the user terminal 40 in response to the input of the blog page from the page generation unit 345.

  Next, the DB server 50 will be described. The DB server 50 includes a component data DB 51 and a layout information DB 52.

The component data DB 51 stores a plurality of component data for creating a blog page. Here, the data stored in the component data DB 51 will be described with reference to FIG. FIG. 5 is a diagram showing an example of a table stored in the component data DB 51 according to the embodiment of the present invention.
In the component data DB 51, for example, as shown in FIG. 5, the component data ID, the component data, and the user ID are stored in the “component data ID” column, the “component data” column, and the “user ID” column, respectively. The data stored in the same row is data associated with each other.

  The component data ID is data that uniquely indicates the component data. The part data ID may be indicated by a predetermined number or number, or may be indicated by a part data path or the like. The component data is various data constituting the blog page, such as text data, audio data, image data, moving image data, background data, or a program that performs a predetermined operation (for example, so-called banner advertisement data or script file), etc. Any data that can be expressed on a blog page is not particularly limited. The user ID is the same as the user ID in FIGS. The user ID may not be associated with all the component data. For example, for component data that is commonly used, no user ID is stored in the “user ID” column.

The layout information DB 52 stores blog page layout information. Here, the data stored in the layout information DB 52 will be described with reference to FIG. FIG. 6 is a diagram showing an example of a table stored in the layout information DB 52 according to the embodiment of the present invention.
In the layout information DB 52, for example, as shown in FIG. 6, a user ID and layout information are stored in a “user ID” column and a “file name” column, respectively.

The user ID is data that uniquely indicates a user who uses the blog service providing system 1, similarly to the user ID of FIG. 3.
The “file name” column stores files describing layout information, and “abc” and “cde” in the “file name” column of FIG. 6 indicate these file names. The layout information is data indicating the layout information of the blog page created by the user with the associated user ID. For example, the layout information is data indicating the shape of the frame for displaying the blog page, the display color of the frame, layout, background and the like, the type of display font, the position and size of component data such as a character string and an image, and the like. Further, the layout information may be a file such as CSS (Cascading Style Sheets) in which design information of a document created in a markup language such as HTML language or XML language is structured.

  With reference to FIG.7 and FIG.8, the flow of a process of the front end server 30, the cache server 20, and the DB server 50 is demonstrated. 7 and 8 are flowcharts showing the processing flow of the front-end server 30, the cache server 20, and the DB server 50 according to the embodiment of the present invention.

  In step S <b> 11 of FIG. 7, the request reception unit 341 of the front-end server 30 receives a request from the user terminal 40 or the blog providing server 10 and outputs information included in the request to the first component data acquisition unit 342.

  In step S <b> 12, the first part data acquisition unit 342 of the front-end server 30 transmits a unit part data acquisition request to the cache server 20.

  In step S <b> 13, the cache server 20 searches the first cache unit 21 in response to receiving the unit component data acquisition request from the front-end server 30. Then, the cache server 20 transmits the search result data to the first part data acquisition unit 342 of the front-end server 30 (step S14). The search result data includes the unit component data when the unit component data corresponding to the first cache unit 21 is cached. When the corresponding unit part data is not cached in the first cache unit 21, the search result data includes data indicating that no unit part data is present.

  In step S15, the first part data acquisition unit 342 of the front end server 30 receives the search result data. Then, the first part data acquisition unit 342 determines whether or not the unit part data is included in the search result data (step S16). If the search result data includes unit part data (YES in step S16), the first part data acquisition unit 342 moves the process to step S32 in FIG. Further, the first part data acquisition unit 342 moves the process to step S17 when the unit part data is not included in the search result data (NO in step S16). At this time, the first component data acquisition unit 342 transmits information included in the request input from the request reception unit 341 to the second component data acquisition unit 343.

  In step S <b> 17, the second part data acquisition unit 343 transmits a part data acquisition request to the cache server 20.

  In step S <b> 18, the cache server 20 receives a component data acquisition request from the second component data acquisition unit 343 of the front-end server 30. And the cache server 20 searches the 2nd cache part 22, and transmits search result data to the front end server 30 (step S19).

In step S20, the second part data acquisition unit 343 of the front-end server 30 receives the search result data from the cache server 20, and determines whether or not the search result data includes part data (step S21). The second component data acquisition unit 343 moves the process to step S29 when the search result data includes component data (YES in step S21).
The second part data acquisition unit 343 moves the process to step S22 when the part data is not included in the search result data (NO in step S21).

  In step S <b> 22, the second part data acquisition unit 343 transmits a part data acquisition request to the DB server 50. This acquisition request includes at least information about the user ID of the blog page that has received the browsing request. Upon receiving this acquisition request, the DB server 50 searches the layout information DB 52 based on the user ID, reads the layout information (step S23), analyzes the read layout information, and converts the component data contained therein into the component data Obtained from the data DB 51 (step S24). Then, the DB server 50 transmits these layout information and component data to the front end server 30 (step S25).

  In step S <b> 26, the second part data acquisition unit 343 of the front-end server 30 receives layout information and part data from the DB server 50 and transmits these data to the cache generation unit 344. The cache generation unit 344 transmits layout information and component data to the cache server 20 (step S27). When the cache server 20 receives the component data and the layout information from the front-end server 30, the cache server 20 caches these component data in the second cache unit 22 (step S28).

  In step S29, the cache generation unit 344 generates unit component data based on the component data and layout information received from the second component data acquisition unit 343. Then, the cache generation unit 344 transmits the generated unit component data to the cache server 20 (step S30 in FIG. 8).

  In step S <b> 31, the cache server 20 receives the unit part data from the front-end server 30 and causes the first cache unit 21 to cache the unit part data.

  In step S32, the page generation unit 345 of the front-end server 30 generates a blog page, and the page transmission unit 346 transmits the blog page to the user terminal 40 or the blog providing server 10 (step S33). When the unit component data is input from the first component data acquisition unit 342, the page generation unit 345 transmits the unit component data to the page transmission unit 346, and displays the blog page expressed by the unit component data as the user terminal 40. Alternatively, it is transmitted to the blog providing server 10. In addition, when the page generation unit 345 receives the component data and the layout information from the second component data acquisition unit 343, the page generation unit 345 configures a blog page using the component data based on the layout information and causes the page transmission unit 346 to transmit the blog page. .

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

  According to the present embodiment, the blog service providing system 1 includes the cache server 20 and the front-end server 30, and the first cache unit 21 of the cache server 20 stores unit part data. The unit component data is data composed of a plurality of component pages and layout information, and can generate a web page (blog page) with only the unit component data. And when the request reception part 341 receives a request, the 1st component data acquisition part 342 will acquire unit part data first, Therefore The response performance of the blog service provision system 1 can be improved.

  Further, according to the present embodiment, the front-end server 30 can perform processing by a higher-level handler, so that a system including the front-end server 30 and the cache server 20 can be easily incorporated into an existing blog system. . For this reason, the response performance of the entire blog service providing system 1 can be improved using an existing system.

  In the present embodiment, the DB server 50 includes the component data DB 51 and the layout information DB 52. However, the present invention is not limited to this. For example, the component data DB 51 and the layout information DB 52 may be provided in the cache server 20.

  In the present embodiment, the second component data acquisition unit 343 transmits a component data acquisition request to the cache server 20, and when the component data is not received from the cache server 20, the layout information and the component data are transmitted to the DB server 50. Although the acquisition request is transmitted, the present invention is not limited to this. For example, if there is a part data constituting the blog page from the second cache part 22 of the cache server 20, the second part data acquisition part 343 acquires only the part data and then runs short. The part data may be acquired from the DB server 50.

DESCRIPTION OF SYMBOLS 1 Blog service provision system 10 Blog provision server 20 Cache server 21 1st cache part 22 2nd cache part 30 Front end server 40 User terminal 50 DB server 51 Component data DB
52 Layout information DB
341 Request reception unit 342 First component data acquisition unit 343 Second component data acquisition unit 344 Cache generation unit 345 Page generation unit 346 Page transmission unit N Communication network

Claims (6)

Component data storage means for storing component data relating to a web page composed of a plurality of components;
A front-end server that creates and transmits the web page in response to a request from a user terminal or handler;
A blog service providing system comprising: a cache server that caches data necessary for creating the web page;
The cache server is
First cache means for temporarily storing unit component data in which a plurality of component data used for configuring the Web page is a unit;
Second cache means for temporarily storing the component data,
The front-end server is
Request accepting means for accepting a web page browsing request from the user terminal or the handler;
When the unit part data related to the Web page browsing request is stored in the first cache unit, the unit part data is acquired, and the unit part data is not stored in the first cache unit In this case, component data acquisition means for acquiring the component data stored in the second cache means or the component data storage means;
Page creation means for creating the Web page based on the unit part data or the part data acquired by the part data acquisition means;
A blog service providing system, comprising: a transmission unit configured to transmit the Web page created by the page creation unit to the user terminal or the handler. The front-end server is
When the component data acquisition unit acquires a plurality of the component data from the second cache unit or the component data storage unit, the acquired plurality of component data is registered in the first cache unit as the unit component data. The blog service providing system according to claim 1, further comprising a cache generation unit.   The blog service providing system according to claim 1, wherein the unit part data includes layout information regarding a plurality of the part data constituting the unit part data. The blog service providing system includes:
A database server for storing the component data;
The blog service providing system according to any one of claims 1 to 3, wherein the database server includes the component data storage unit. Component data storage means for storing component data relating to a web page composed of a plurality of components;
A front-end server that creates and transmits the web page in response to a request from a user terminal or handler;
A cache server that caches data necessary for creating the web page, and provides a blog service,
The cache server temporarily storing unit component data including a plurality of component data used for configuring the Web page as a unit;
The cache server temporarily storing the component data;
The front-end server receiving a web page browsing request from the user terminal or the handler;
When the unit part data related to the Web page browsing request is temporarily stored, the front end server acquires the unit part data, and the unit part data is not temporarily stored. In this case, the step of acquiring the component data stored temporarily or the component data stored in the component data storage means;
The front-end server creating a web page based on the acquired unit component data or the component data;
The front-end server sending the created web page to the user terminal or the handler. Component data storage means for storing component data relating to a web page composed of a plurality of components;
A front-end server that creates and transmits the web page in response to a request from a user terminal or handler;
A cache server that caches data necessary for creating the Web page, and a program for providing a blog service to the front-end server and the cache server,
First cache means for temporarily storing unit component data in which the cache server is a unit of a plurality of component data used for creating the Web page;
Causing the cache server to function as second cache means for temporarily storing the component data;
The front-end server,
Request accepting means for accepting a web page browsing request from the user terminal or the handler;
When the unit part data related to the Web page browsing request is stored in the first cache unit, the unit part data is acquired, and the unit part data is not stored in the first cache unit In this case, component data acquisition means for acquiring the component data stored in the second cache means or the component data storage means;
Page creation means for creating the Web page based on the unit part data or the part data acquired by the part data acquisition means;
A program for causing a Web page created by the page creation means to function as a transmission means for sending to the user terminal or the handler.

Images