JAWS: The Server-less Framework V1 (BETA)
Welcome to JAWS V1 BETA. We're still fixing many quirks. Please provide fixes and feedback. If you want to help, please view the JAWS V1 Google Document.
Goals:
- No Servers: The JAWS back-end is comprised entirely of AWS Lambda Functions. You can develop/update/configure each separately without affecting any other part of your application. Your app never goes down. There is no app. Only individual lambda functions can go down.
- Scale Infinitely: A back-end comprised of Lambda functions comes with a ton of concurrency.
- Be Cheap As Possible: Lambda functions run only when they are called, and you pay only when they are run.
- All Lambda Runtimes While first release is
nodejsonly, we plan on adding supoport for all languages. This means each lambda in your JAWS project can be coded in the lang that best suites the problem. - API Gateway Auto-Deploy Creates your API endpoints for you on API Gateway.
- Multi-stage & Multi-Region: Define stages for your project, and multiple regions with a stage. Driven by CloudFormation.
Architecture
Graphics coming soon...
Quick Start
The guide below gets you started quickly. Later, check out the best practices guide in our wiki for tips on security and more.
-
$ npm install jaws-framework -g -
$ jaws new project -
$ cd <new-project-name> -
$ jaws new action users create -b -
$ jaws dash
This will create a new jaws project, create a lambda function and endpoint, which you can immediately deploy via
jaws dash. After deployment is complete, you will be given a url. In the above example, you can access your
deployed lambda at your_url/users/create.
Where do I go from here?
We're currently working on our docs, wiki, best practices and FAQ pages.
Once you become familar with JAWS, you can read the JAWS plug-in module guide to start contributing JAWS modules to the community.
How can I help?
Please check out the JAWS V1 Google Document and our CONTRIBUTING.md for coding and PR guidelines.