Techniques for metadata-driven dynamic content serving
First Claim
1. A method comprising:
- storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request;
publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods comprise at least a domain mapping server to map the site identifier to a tenant identifier, a metadata server coupled with the domain mapping server, the metadata server to store the metadata content, and a render engine to dynamically generate metadata-driven content in response to requests received from client devices;
receiving a request for content with a selected one of the one or more runtime pods for a specific site;
mapping the specific site to a user, wherein the user is identified by a user identifier, wherein the user identifier is one of one or more user identifiers associated with the tenant identifier;
using the user identifier to retrieve site metadata from the site metadata server;
providing content, with the render engine, in response to the request with the selected runtime pod utilizing the metadata content.
1 Assignment
0 Petitions
Accused Products
Abstract
Techniques for metadata-driven dynamic content serving. Metadata content is stored as a source instance. The metadata content is utilized to provide dynamically-constructed pages. The metadata content is published to runtime pods communicatively coupled to receive the metadata content. The source instance includes a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods. The runtime pods are groups of multiple servers that act as a single entity to dynamically generate metadata-driven content in response to requests received from client devices. A request for content is received with a selected one of the runtime pods for a specific site. The specific site is mapped to a user identified by a user identifier. The user identifier is utilized to retrieve site metadata from a site metadata server. Content is provided in response to the request with the selected runtime pod utilizing the metadata content.
267 Citations
18 Claims
-
1. A method comprising:
-
storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods comprise at least a domain mapping server to map the site identifier to a tenant identifier, a metadata server coupled with the domain mapping server, the metadata server to store the metadata content, and a render engine to dynamically generate metadata-driven content in response to requests received from client devices; receiving a request for content with a selected one of the one or more runtime pods for a specific site; mapping the specific site to a user, wherein the user is identified by a user identifier, wherein the user identifier is one of one or more user identifiers associated with the tenant identifier; using the user identifier to retrieve site metadata from the site metadata server; providing content, with the render engine, in response to the request with the selected runtime pod utilizing the metadata content. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. An article comprising a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, are configurable to cause the one or more processors to:
-
store metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; publish the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein the source instance comprises a metadata definition repository and is a primary source of dynamic data for serving pages in the runtime pods, wherein the runtime pods comprise at least a domain mapping server to map the site identifier to a tenant identifier, a metadata server coupled with the domain mapping server, the metadata server to store the metadata content, and a render engine to dynamically generate metadata-driven content in response to requests received from client devices; receive a request for content with a selected one of the one or more runtime pods for a specific site; map the specific site to a user, wherein the user is identified by a user identifier, wherein the user identifier is one of one or more user identifiers associated with the tenant identifier; use the user identifier to retrieve site metadata from the site metadata server; provide content, with the render engine, in response to the request with the selected runtime pod utilizing the metadata content. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A system comprising:
-
a metadata repository having at least one hardware processor and at least one memory device coupled to the at least one hardware processor, the metadata repository to store metadata content to be utilized to provide dynamically-constructed pages of content, wherein the metadata comprises at least a site definition stored according to a site identifier to allow the metadata to be retrieved and converted to a format indicated by a request; a domain mapping server to map the specific site to a user, wherein the user is identified by a user identifier, wherein the user identifier is one of one or more user identifiers associated with the tenant identifier; a metadata server coupled with the domain mapping server, the metadata server to store the metadata content; and a render engine to generate a response to the request. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification