Simplifying serverless workflows using cloud Functors.
tc defines, creates and manages the lifecycle of serveless entities such as functions, mutations, events, routes, states, queues and channels collectively known as a cloud functor.
tc defines, creates and manages the lifecycle of serveless entities such as functions, mutations, events, routes, states, queues and channels collectively known as a cloud functor.
A composable, namespaced, sandboxed, recursive, versioned and isomorphic topology of serverless entities is called a Cloud Functor. A functor has six unique features:
At it's core, tc provides 7 entities (functions, events, mutations, queues, routes, states and channels) that are agnostic to any cloud provider.
Scope and group your functions, events, routes and other entities like modules in a programming language.
Sandboxing is fundamental to canary-based routing and deploys.
Generate infrastructure boilerplate such as permissions, sane default configurations.
Functors can be created at any level in the code repository's heirarchy. They are like fractals where we can zoom in or out.
Diffable infrastructure between generated and rendered topologies.