Sanfran

A small JavaScript handler may need a way to receive web requests without the developer building a complete service around it. SanFran provided a Kubernetes function engine using a Node.js-style request and response interface, with its own controller for managing function execution. The original repository is archived, so this is a historical platform rather than a fresh-install recommendation. Migrating a function means checking its route, dependencies and process-state assumptions as well as saving its source code.

Current guidance

The recovered description matches dosco/SanFran, a Kubernetes function engine with a Node.js-style request/response interface and custom controller. Its upstream repository is archived. The README still demonstrates a 0.1.0 chart and an older Glide-based build workflow; these establish the original identity but do not establish compatibility with a current cluster or JavaScript runtime.

An existing deployment should first export function code, dependency versions, routes, environment variables and secrets. Determine which functions depend on process reuse, local memory, filesystem writes or SanFran-specific management APIs. Those behaviors affect whether a function can move into an ordinary service container or a different function platform without changing its semantics.

Evaluate a replacement using the workload’s actual event sources, concurrency limits, authentication and latency requirements. Reproduce one representative request path, including errors and timeouts, before switching traffic. The historical sub-30-millisecond startup claim is not a current benchmark and should not determine platform selection. No authoritative drop-in successor was identified; retain the old configuration as migration evidence rather than redeploying its historical package.