Techniques for metadata-driven dynamic content serving
First Claim
Patent Images
1. A method comprising:
- storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content;
publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein each runtime pod is located and isolated away from the source instance of 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 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, wherein the runtime pods access the metadata content via a version-aware interface to allow accesses to be accomplished using calls to the source instance when available and to other versions of the content when the source instance is not available;
receiving a request for content with a selected one of the one or more runtime pods;
providing content in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance or from the other versions of the content when the source instance is not available.
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 to be utilized to provide dynamically-constructed pages of content. The metadata content is published to one or more runtime pods communicatively coupled to receive the metadata content. A request for content is received with a selected one of the one or more runtime pods. Content is provided in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance.
140 Citations
14 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; publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein each runtime pod is located and isolated away from the source instance of 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 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, wherein the runtime pods access the metadata content via a version-aware interface to allow accesses to be accomplished using calls to the source instance when available and to other versions of the content when the source instance is not available; receiving a request for content with a selected one of the one or more runtime pods; providing content in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance or from the other versions of the content when the source instance is not available. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. An apparatus comprising:
-
means for storing metadata content as a source instance, the metadata content to be utilized to provide dynamically-constructed pages of content; means for publishing the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein each runtime pod is located and isolated away from the source instance of the metadata content, wherein the dynamic data for serving pages in the runtime pods, wherein 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, wherein the runtime pods access the metadata content via a version-aware interface to allow accesses to be accomplished using calls to the source instance when available and to other versions of the content when the source instance is not available; means for receiving a request for content with a selected one of the one or more runtime pods; means for providing content in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance or from the other versions of the content when the source instance is not available. - View Dependent Claims (8)
-
-
9. An article comprising a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, 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; publish the metadata content to one or more runtime pods communicatively coupled to receive the metadata content, wherein each runtime pod is located and isolated away from the source instance of 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 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, wherein the runtime pods access the metadata content via a version-aware interface to allow accesses to be accomplished using calls to the source instance when available and to other versions of the content when the source instance is not available; receive a request for content with a selected one of the one or more runtime pods; provide content in response to the request as a response with the selected runtime pod utilizing the metadata content published from the source instance or from the other versions of the content when the source instance is not available. - View Dependent Claims (10, 11, 12, 13, 14)
-
Specification