A dynamic microservices framework for building, connecting, and deploying cloud-native applications.

An extremely common, modern application stack includes three services: a frontend webapp, a server-side API, and a database. In this example, you'll learn how that stack can be captured in an Architect component to enable automated deployments, networking, and network security for your application wherever it gets deployed to.

In the architect.yml file for this project, we describe all three of these services as deployable runtimes. However, we also leverage Architect's service discovery features to populate environment secrets by reference. This not only allows us to automatically connect the services to each other, but it also allows Architect to build strict network policies to whitelist the traffic between these services. Now we won't have any work ahead of us to promote this stack from local dev all the way through to production readiness!

Learn more about the architect.yml file

Architect component specs are declarative, so it can be run locally or remotely with a single deploy command:

# Clone the repository and navigate to this directory
$ git clone https://github.com/architect-community/react-app.git
$ cd ./react-app

# Deploy using the dev command
$ architect dev ./architect.yml

Once the deploy has completed, you can reach your new service by going to https://app.localhost.architect.sh/.

Want to try deploying this to a cloud environment? Architect's got you covered there too! if you've already created your account, you can run the command below to deploy the component to a sample Kubernetes cluster powered by Architect Cloud:

$ architect deploy ./architect.yml -e example-environment

See this readme for an advanced configuration and deployment example which includes steps to create your own AWS infrastructure all the way to automated deployments using Architect.