The team-centric
deployment platform for
microservice applications
Architect is everything teams need to accelerate cloud development and harbor collaboration from local dev to global distribution.
|
Resolve relationships between microservices
Connect related microservices to better collaborate in cloud environments. Architect resolves dependencies at deploy-time to guarantee availability and connectivity with every deploy.
Automatically protect ingress & egress traffic
Architect minimizes your app's attack surface by globally locking down networking and only whitelisting traffic between related services
Deploy with ease & confidence to any platform
Services in Architect's registry are infrastructure-agnostic and ready to be deployed to any platform. Deploy safely and code-free to Kubernetes, ECS, and even local environments!
Approach
Works with any provider and tools.
Architect provisions resources in your cloud and on your terms. Environment owners and operators are given full control over which container platform, security tools, and network gateways each environment uses. Better yet, operators can easily provision new environments with entirely different tools with zero code changes!
How It Works
Create. Integrate. Deploy.
{
"name": "e-market/checkout-service",
"description": "Runs the checkout process for a shopping cart",
"api": {
"type": "rest"
},
"dependencies": {
"e-market/email-service": "v1.1",
"pay-buddy/payments-service": "v2.1.3",
"chore-rabbit/shipping-service": "v1",
"e-market/cart-service": "latest"
}
}Configure services
Configuring services to be deployed via Architect requires only the addition of an architect.json manifest file that tells the platform what your service is named, what other services it depends on, and various other details the platform uses for indexing, discovery, versioning, and of course deployment.
Service manifests are intentionally scoped to application specs and will never include coupling to infrastructure providers or tools ensuring services can be deployed to multiple locations.
{
"services": {
"e-market/frontend:v2.0": {
"ingress": {
"subdomain": "shop"
},
"parameters": {
"DEFAULT_CURRENCY": "USD"
}
}
}
}Configure environments
Environments consist of one or more services to be deployed, the parameters values each service will use during runtime, and the networking rules to apply to traffic from both internal and external sources.
The separation of environments creation from service creation enables operators to maintain global control of provisioning and security for high-risk environments without impeding on day-to-day development efforts.
# Run the whole stack locally
$ architect deploy env-config.json --local
# Deploy the stack to a new "dev" environment hosted on AWS ECS
$ architect env:create "dev" --type "ecs"
$ architect deploy env-config.json --env "dev"
# Deploy the stack to an existing "prod" environment
$ architect deploy env-config.json --env "prod"Deploy
Application complexity historically makes it difficult to create new services and provision new end-2-end environments, but not any more. Architect is able to push any service and all it's dependencies to any environment with ease! No matter how complex your application gets, Architect ensures consistent and reliable deployments to any cloud provider.
Learn More
Use Cases
Architect is great when you need to...
Perfect For:
Big engineering teams
Companies switching to microservice architecture
Teams that embrace DevOps
