Serverless.cr

Serverless runtime for crystallang. Currently, only AWS Lambda is supported. Open an Issue or PR if you think another provider should be supported!

Installation

You can include this as a dependency in your project in shards.yml file

dependencies:
  serverless:
    github: andrewc910/serverless.cr
    branch: master

Now run the the shards command to download the dependency. You can now create your own lambda handlers like this:

require "json"
require "serverless/lambda"

def self.handler(ctx : SLS::Lambda::Context) : Nil
  response = do_something

  ctx.res.body = response.content
  ctx.res.status_code = response.status_code
end

SLS::Lambda::Runtime.run_handler(->handler(SLS::Lambda::Context))

The ctx variable is of type SLS::Lambda::Context which inherits from HTTP::Server::Context. Due to the nature of the compiler, ctx.request & ctx.response are types HTTP::Request+ & HTTP::Server::Response+ while ctx.req & ctx.res are types SLS::Lambda:HTTPRequest & SLS::Lambda:HTTPResponse. Make sure to set the body and status code using ctx.res otherwise you will run into compilation errors.

Supported Frameworks

Serverless.cr is looking to support crytal frameworks out of the box. We currently support Athena & Lucky but PR's are welcome!

Note: The examples below will run the frameworks HTTP server when the environment variable SERVERLESS is not set aka dev environments. In AWS lambda, ensure you set the env var SERVERLESS to true to ensure the lambda runtime is intialized and not the HTTP server.

Athena

Your main entry file for Athena should look like this:

require "json"
require "Athena"
require "serverless/lambda"
require "serverless/ext/athena"

# Run the server
if ENV["SERVERLESS"]?
  SLS::Lambda::Runtime.run_handler(->SLS::Ext::Athena.handler(SLS::Lambda::Context))
else
  ART.run
end

Lucky

Open start_server.cr include these changes:

require "./app"
require "serverless/lambda"
require "serverless/ext/lucky"

Habitat.raise_if_missing_settings!

if Lucky::Env.development?
  Avram::Migrator::Runner.new.ensure_migrated!
  Avram::SchemaEnforcer.ensure_correct_column_mappings!
end

app_server = AppServer.new

if ENV["SERVERLESS"]?
  SLS::Ext::Lucky.handler(app_server)
else
  Signal::INT.trap do
    app_server.close
  end

  puts "Listening on http://#{app_server.host}:#{app_server.port}"
  app_server.listen
end

Deployment

Make sure the serverless framework is set up properly. The next step is to create a proper serverless configuration file like this

service: crystal-hello-world

provider:
  name: aws
  runtime: provided

package:
  artifact: ./bootstrap.zip

functions:
  httpevent:
    handler: httpevent
    events:
      - http:
          memorySize: 128
          path: hello
          method: get

If you are using osx, make sure you are building your app using docker, as an AWS lambda runtime environment is based on Linux. You can create a linux binary using docker like this

docker run --rm -it -v $PWD:/app -w /app crystallang/crystal:latest crystal build src/bootstrap.cr -o bin/bootstrap --release --static --no-debug

Single Binary Deployment

Now package the zip file required for deployment and deploy

zip -j bootstrap.zip bin/bootstrap
sls deploy

Auxiliary File Deployment

If you require files that are not baked into your binary, follow this guide below.

Create a .gitattributes file and add the following:

.github export-ignore
.serverless export-ignore
lib export-ignore
spec export-ignore
tmp export-ignore

*.cr export-ignore
.keep export-ignore

Feel free to add any other files you don't want uploaded

Build

docker run --rm -it -v $PWD:/app -w /app crystallang/crystal:latest crystal build src/bootstrap.cr -o bin/bootstrap --release --static --no-debug

Move your binary to the top level

mv ./bin/boostrap ./
Commit to git
Run git archive -v HEAD -o bootstrap.zip

Archive will zip the contents of the latest commit so make sure you commit beforehand.

You should now have a bootstrap.zip at the top level of your project directory.
Run sls deploy to deploy

Monitoring

In order to monitor executions you can check the corresponding function logs like this

sls logs -f httpevent -t

You can also get some very simple metrics per functions (this might require additional permissions)

sls metrics -f httpevent

Example

If you want to get up and running with an example, run the following commands

git clone https://github.com/andrewc910/serverless.cr
cd serverless.cr/example

# download dependencies
shards

# built binary (using docker under osx) and creates the zip file
make

# deploy to AWS, requires the serverless tool to be properly set up
sls deploy

This will start a sample runtime, that includes a single HTTP endpoint.

Contributing

Fork it (https://github.com/andrewc910/serverless.cr/fork)
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature'), also run bin/ameba
Push to the branch (git push origin my-new-feature)
Create a new Pull Request
Don't forget to add proper tests, if possible

Contributors

Andrew Crotwell - maintainer
Alexander Reelsen - creator

CrystalDoc.info

serverless