Laconia

Laconia

  • Getting Started
  • API
  • Help

›Laconia vs. Other

Introduction

  • Getting Started
  • Motivation
  • Core Concepts
  • Philosophy
  • Examples
  • FAQ
  • Support Me

Laconia vs. Other

  • Claudia
  • Express, Koa, Hapi, etc.
  • Middy
  • Serverless, SAM, Apex, etc.

Guides

  • Injecting Dependencies
  • Unit Testing
  • Adapting Events
  • Creating API Endpoints
  • Retrieving Secrets
  • Retrieving Config
  • Warming Up
  • Invoking Other Lambdas
  • Long Running Tasks
  • Creating Middleware

API Reference

  • API Reference: Intro
  • core
  • event
  • adapter
  • adapter-api
  • invoker
  • config
  • batch
  • middleware-lambda-warmer
  • middleware-serverless-plugin-warmup
Edit

Laconia vs. Claudia

Claudia as a framework consists of multiple components. Claudia's deployment tool is theoretically compatible and can be used together with Laconia. Claudia's deployment tool is designed to be totally separate from its runtime dependencies, and Laconia is designed to be totally separate from its deployment tooling.

Claudia's API Builder, on the other hand, is incompatible with Laconia. Although both of them are trying to tackle a similar problem, fundamentally they follow a contradicting principle. Claudia's API Builder is focused on the web and encourage multiple HTTP endpoints on a single module. Laconia deals with not only web, and encourage one HTTP endpoint per function. Naturally, in a serverless architecture, you can use both of them together in separate serverless functions if needed. Do however note that Laconia features will not be able to be used in the Claudia Lambdas.

← Support MeExpress, Koa, Hapi, etc. →
Laconia
Docs
Getting StartedCore ConceptsAPI Reference
Community
Stack OverflowChat
More
TwitterGitHubStar
Copyright © 2022 Wisen Tanasa
Logo designed by Suzie Nam