This blog post provides some information about the three major phases for data access in content delivery solution lifecycles for headless content management solutions. If you have additional perspective on this topic, please comment on this blog post.
For background information, see this previous blog post:
Content delivery solutions can retrieve data (both JSON text and binary media) from the CMS during three phases of the solution lifecycle:
- Statically during the build process.
- Dynamically from application services.
- Dynamically from the client application.
Statically During the Build Process
The main disadvantages of static solutions are the need to regenerate, deploy, and deliver the solution to incorporate any changes. At some scale, the size of the deployed artifact may make it unwieldly for certain purposes.
Dynamically from Application Services
Content delivery solutions can use application servers or application services such as .NET, Java, and NodeJS to implement HTTP/JSON services that consume data from the CMS dynamically, increasingly in a serverless context where customers do not need to be aware of or manage server infrastructure. Applications running in visitor devices or elsewhere access services implemented by the customer that access data from the CMS. In addition to services, application servers may use content delivery services while generating HTML to service page requests.
Dynamically from the Client Application
5 thoughts on “Three Major Phases for Data Access in Headless Content Management Solutions”