In order to achieve Lift goals, we first draw a picture of the current AWS serverless ecosystem. We chose to focus on 3 main evaluation criterion to rate existing solutions.
- Is it feature-oriented ? Being an AWS oriented framework requires the developer to have some existing knowledge of AWS services. It is not made for serverless beginners.
- How many steps required to get started ? Solution with a complicated onboarding process are cumbersome
- Can I eject easily ? In case the solution does not fit my requirements anymore, can I easily opt-out without loosing everything I implemented ?
- Which common web features can I easily implement with the solution ?
Criterion \ Solution | Stackery | Architect | Laravel Vapor | Amplify | CDK | SST | SLS | SLS Components |
---|---|---|---|---|---|---|---|---|
Underlying technology | SAM | SAM | CDK | CFN | ||||
Onboarding: Feature-oriented | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ |
Onboarding: Steps quantity | ❌ | ✅ | ❌ | ❌ | ✅ | ✅ | ✅ | ✅ |
Lock-in: Ejectable | ✅ | ✅ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ |
Feature: File upload | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
Feature: Authentication | ❌ | ❌ | ❌ | ✅ | ❌ | ✅ | ❌ | ❌ |
Feature: Asynchronous jobs | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
Feature: Database | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
Feature: Real-time feedback | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
Feature: File storage | ✅ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
Feature: Static website | ✅ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ✅ |
Feature: Server-side rendering | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ✅ |
Feature: HTTP API | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Feature: Webhook | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |