Project Philosophy

.arc frees your architecture from infra and vendor cruft so you can focus on the real business logic of your app. Ship only the code that matters, iterate faster and enjoy unprecedented availability guarantees.

The iron age of compute began with racked physical servers. Early cloud compute evolved past physical servers into virtual machines.

Virtual machines eventually gave way to containers and quickly containers have given rise to cloud functions.

Each cycle has taught new lessons in software architecture and this most recent iteration brings new challenges.

  • Config and tooling is designed for the last generation of metaphors
  • AWS is massive and overwhelming with many similar — but not the same — products with divergent interfaces between interlocking services
  • Deep proprietary knowledge is required to configure and maintain common infrastructure primitives
  • Configuration and infrastructure can drift, leaving systems in states that are difficult to repeat / reproduce, and thus scale
  • Painful manifest files; JSON is difficult to read, has no comments, and is unforgiving to edit; YAML isn't much better and is in some ways far worse (i.e. deeply nested statements)

Some of these problems have been tamed with infrastructure as code, creating repeatable and reproducible systems. The trade-off there is: you're committing AWS configuration knowledge into your revision control systems.

.arc views infrastructure as a build artifact. And we prefer to not check build artifacts in with our code.

The .arc file

architect defines a high level vendor agnostic plaintext format, .arc, as a manifest file to solve the specific problems laid out above.

With .arc you:

  • Focus on defining your app architecture with a subset of service primitives as high level definitions
  • Use npx to generate local code, configure, provision, and deploy cloud infrastructure from the .arc manifest
  • You can still safely use the console tactically to access and administer primitives defined in .arc
  • The format, parser, and tooling are completely open to extension

In theory, .arc is also entirely portable between cloud vendors. (However no ports to clouds other than AWS have been made as of today.)

The .arc format

The .arc format follows a few simple rules:

  • Comments start with #
  • Sections start with @
  • Everything between sections becomes instructions for generating AWS infrastructure

.arc files are made up of the following sections:

  • @app [required] defines your application namespace
  • @aws defines AWS variables
  • @domain defines DNS for a custom domain name
  • @events defines application events you can publish and subscribe to
  • @http defines HTTP (i.e. text/html) handlers
  • @indexes defines table global secondary indexes
  • @scheduled defines functions that run on a schedule
  • @static defines S3 buckets for static assets
  • @tables defines DynamoDB database tables and trigger functions for them
  • @ws defines Web Socket handlers

This is a complete .arc file example:

# .arc


get /
post /likes
get /likes


daily-affirmation rate(1 day)

staging test-hello-bucket
production hello-bucket

  likeID *String
  update Lambda

  date *String

Running npx create in the same directory as the .arc file above generates the following function code:

| |-http
| | |-get-index/
| | |-get-likes/
| | '-post-likes/
| |-events
| | '-hit-counter/
| |-scheduled
| | '-daily-affirmation/
| |-tables
| | '-likes-update/
| '-ws
|   |-ws-connect/
|   |-ws-default/
|   '-ws-disconnect/

The code was also immediately deployed to the cloud in fully isolated staging and production environments.

The .arc format is terse, easy to read, and quickly learnable to author. The expressions in a .arc file unlock the formerly complex tasks of cloud infrastructure provisioning, deployment, and orchestration.

Next: Check out the quickstart