Scope types
A scope type defines what kind of infrastructure backs your deployment environment: how it's provisioned, how your application runs, and how traffic reaches it.
Nullplatform maintains sample scope types that cover the most common deployment patterns. They are examples, not the limit of what you can run: Sample scopes lists every one of them with its repository, and you can adapt one or craft your own.
Choosing a scope type
| Workload | Start from |
|---|---|
| Web apps, APIs, microservices | Containers |
| Scheduled tasks, batch jobs | Scheduled tasks |
| SPAs, static websites, front-end bundles | Static files |
| Serverless functions | AWS Lambda, in Sample scopes |
| Containers on self-managed or on-premise clusters | Containers On-Premise, in Sample scopes |
| Mobile apps (Android, iOS) | Mobile store, in Sample scopes |
| PL/SQL or other custom workloads | Craft a scope from scratch |
Legacy scope types
Nullplatform also supports legacy scope types for existing workloads. Unlike agent-backed scopes, nullplatform deploys them directly in your cloud account, using the cloud credentials you give it, instead of through workflows your agent runs:
- Kubernetes: container-based deployments on EKS
- Server instances (EC2): VM-based deployments with auto-scaling groups
- Serverless (AWS Lambda): serverless function deployments
These remain available for backward compatibility. For new serverless workloads, use the agent-backed AWS Lambda scope in Sample scopes. See Legacy scopes for existing workloads.
Next steps
- Sample scopes: every sample scope type, with its repository
- Containers: deep dive into the default scope type
- Scheduled tasks: configure periodic jobs on Kubernetes
- Static files: deploy SPAs and static websites with CDN distribution
- Craft a scope from scratch: build your own scope type for workloads that don't fit the samples
- Legacy scopes: reference for existing Kubernetes, EC2, and Lambda workloads