Package Exports
- @jetkit/cdk
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@jetkit/cdk) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
JetKit/CDK
An opinionated toolkit for building cloud-native serverless applications.
This module provides tools for defining RESTful API views with code and generating cloud infrastructure using AWS CDK.
Motivation
We want to build maintainable and scalable cloud-first applications, with cloud resources generated from application code.
Using AWS CDK we can automate generating API Gateway routes and Lambda functions from class and function metadata. Each class or function view is a self-contained Lambda function that only pulls in the dependencies needed for its functioning, keeping startup times low and applications modular. Get the utility of a minimal web framework without cramming your entire app into a single Lambda.
Optional support for TypeORM using the Aurora Serverless Data API and convenient helpers for CRUD, serialization, tracing, and error handling will be added soon.
Documentation
Guides and API reference can be found at https://jetbridge.github.io/jetkit-cdk/.
Installation
@jetkit/cdk runs on Node.js and is available as a NPM package.
npm install @jetkit/cdk
Examples
API View
import { HttpMethod } from "@aws-cdk/aws-apigatewayv2"
import { badRequest, methodNotAllowed } from "@jdpnielsen/http-error"
import { APIGatewayProxyHandlerV2 } from "aws-lambda"
import { APIEvent, ApiViewBase, RequestHandler, apiViewHandler, ApiView, Route, SubRoute } from "@jetkit/cdk"
// define optional properties for our functions
const lambdaOpts = {
memorySize: 512,
bundling: {
minify: true,
sourceMap: true,
},
environment: {
LOG_LEVEL: "DEBUG",
},
}
@ApiView({
// base route
path: "/album",
...lambdaOpts,
})
export class AlbumApi extends ApiViewBase {
// define POST handler
post: APIGatewayProxyHandlerV2 = async () => "Created new album"
// custom endpoint in the view
// routes to the ApiView function
@SubRoute({
path: "/{albumId}/like", // will be /album/123/like
methods: [HttpMethod.POST, HttpMethod.DELETE],
})
async like(event: APIEvent) {
const albumId = event.pathParameters?.albumId
if (!albumId) throw badRequest("albumId is required in path")
const method = event.requestContext.http.method
// POST - mark album as liked
if (method == HttpMethod.POST) return `Liked album ${albumId}`
// DELETE - unmark album as liked
else if (method == HttpMethod.DELETE) return `Unliked album ${albumId}`
else return methodNotAllowed()
}
}
// entry point for the file
export const handler = apiViewHandler(__filename, TopicCrudApi)
Handler Function With Route
// a simple standalone function with a route attached
export async function topSongsHandler(event: APIEvent) {
return JSON.stringify({
message: "function route",
rawQueryString: event.rawQueryString,
})
}
// define route and lambda properties
Route({
path: "/top-songs",
methods: [HttpMethod.PUT],
...lambdaOpts,
})(topSongsHandler)
// alternate, uglier way of writing the same thing
const topSongsFuncInner = Route({
path: "/top-songs-inner",
methods: [HttpMethod.PUT],
...lambdaOpts,
// this function name should match the exported name
// or you must specify the exported function name in `handler`
})(async function topSongsFuncInner(event: APIEvent) {
return `cookies: ${event.cookies}`
})
export { topSongsFuncInner }