Simple functional processing inspired by ServerLess and AWS Lambda
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Maven Central Build Status Codacy Badge

Simple HTTP handler supporting dynamic loading of HTTP handler functions. Intended for running within your existing infrastructure as a gateway or integration layer embedded with your current framework like, but not limited to, Spring MVC or Spring Flux.

It Really Whips The Lambda's Ass!

Example use-cases

  • Ad-hoc API services and integration projects - Changes in the integration code can evolve freely from the core service
  • Transactional support across multiple API calls
  • Batch multiple API calls to avoid chatty data exchange
  • API prototyping
  • A powerful support tool for extracting data or changing state (think JMX on steroids)

Getting started

Integrating with your project

NOTE: If you want to try the bleeding edge, please add this snapshot repository


Usage with Spring Boot and Spring MVC

Add dependency to your pom.xml


Add the following properties to


Invocation/delegation from a standard HttpServlet

public class MyLamebdaServlet implements HttpServlet
    String contextPath = "/servlet";
    String sourceDir = "/var/lib/lamebda";
    final ClassResourceLoader classResourceLoader = new FileSystemClassResourceLoader(f->f, sourceDir);

    public void service(HttpServletrequest req, HttpServletResponse res)
        final HttpRequest request = new ServletHttpRequest(contextPath, request);
        final HttpResponse ressponse = new ServletHttpResponse(response);
        functionManager.handle(request, response);

Directory structure

  • A root folder, example: /var/lib/lamebda
  • Project directory, example: var/lib/lamebda/test
  • A Project configuration file: /var/lib/lamebda/

Project configuration

  • - Human-readable name of the project
  • project.version - The project version
  • mapping.project-context-path - Project context path. Default is the project directory name.
  • mapping.use-project-context-path - Whether to prepend the request path with the project context name, i.e /servlet/gateway/<project>/my-function
  • function.static.enabled - Turn static content serving on/off. Default true
  • function.static.prefix - The path that static content is served under, default static
  • function.static.path - The folder that static content is served from, default is <project-dir>/static

Extra preparations if you have an Open API Specification (OAS) file

  1. Create a home directory for Lamebda. We will use /var/lib/lamebda as an example.

  2. Put your API specification file and put it in location /var/lib/lamebda/specification/oas.yaml

  3. Create directory .generator in the root folder, so we have /var/lib/lamebda/.generator.

  4. Download openapi-generator-cli and groovy-models and put it into the .generator folder.

Setup a project folder

Create a project folder. This folder is a logical grouping for your API functions. We will go with the create test for now. We now have the folder /var/lib/lamebda/test.

Add your first script

  1. Create a folder for the functions in the test project: /var/lib/lamebda/test/scripts

  2. Add a simple script in the scripts folder:

class MyFunction extends SimpleServerFunction {
    void get(HttpRequest request, HttpResponse response) {
        response.json(HttpStatus.OK, [requestmethod: request.method, message:'Hello world'])

Access your first function

Your function should be available under /gateway/test/my-function

Built in functions

  • /servet/gateway/test/status/ - Simple status page requiring authentication specified with admin.credentials.username and admin.credentials.password in the file.