washpost/fusion-resolver repository overview

⁠resolver

The resolver lambda is invoked as part of a rendering request.

The purpose of this lambda is to resolve the trailing URI segment into a piece of global content and an associated page/template.

The resolver-generator creates a new version of the resolver when resolvers.json is updated in S3. This process copies the resolvers.json into the lambda's filesystem to avoid DB queries or network latency. Resolvers don't actually change that often, so it is more performant to create a new lambda with the resolvers inside it than it is to query the DB on every request. This avoids hot keys in memcached.

⁠Routes

There are two supported routes, which are variants of each other.

⁠/resolve/*

The resolve endpoint will resolve the trailing URI segment into a piece of global content and an associated page/template and return the result as JSON.

⁠/make/*

The make endpoint will resolve the trailing URI segment into a piece of global content and an associated page/template, and then render the content into the template, returning HTML. This is performed by invoking the engine lambda.