Starting footprint
Start with the resources the application needs.
- Smaller initial capacity
- Review shared resources
- Document availability trade-offs
An application walkthrough
One application, connected decisions.
Explore a Node.js / TypeScript API with PostgreSQL and Redis. This illustrative scenario follows the decisions from application dependencies to AWS deployment planning.
Node.js / TypeScript APIOne application. Four connected decisions.
Understand the relationships
The API is only part of the application.
Database and cache dependencies shape the architecture, the running cost and the order of migration.
Dependency manifests → application inventory
Node.js APIRequest handling
PostgreSQLApplication data
RedisCache
When to consider it
A server-based application with a conventional runtime and deployment model.
What to review
Review runtime configuration, dependencies and the generated container recipe.
Supported compute deployment path
Decide what to optimize for.
Compare resource and availability assumptions before committing to an architecture.
This walkthrough shows the decision structure. An actual assessment provides estimates with region, sizing and usage assumptions.
From a decision to delivery
Review the plan. Then approve the work.
For a supported Amazon EC2 workload, review the generated infrastructure and delivery artifacts before applying the plan in your AWS account.
Explore deployment scope- Inspect the artifactsInfrastructure, container recipes and CI/CD
- Review and approvePlan preview, requirements and blockers
- Deploy supported workloadsEC2 or EKS · your AWS account
Let’s map your next step on AWS.
Discuss your codebase, target architecture and delivery requirements in a technical demo.
Have an open-source application? Request a public repo assessment.
Requests are reviewed before analysis. Public reports are published with your consent.