Skip to content

Monorepo or monopackage #4

Closed
Closed

Description

@sam-goodwin

I am leaning mono-package because of the circularity:

  1. AWS Lambda has bindings for Cloudflare
  2. Cloudflare has bindings for AWS

This means they need to be aware of each other's types (to build bindings for resources). It's possible in a mono-package but requires additional "coordinating packages" in a monorepo

Activity

  1. suddenlyGiovanni commented on Nov 3, 2025

    @suddenlyGiovanni

    One doesn't exclude the other, necessarily...
    You could start with a mono-package and eventually migrate to a monorepo as needs arise, but the inverse is not feasible... (same comparison of modular monolith and microservice arch once you still have to start with the implementation)

  2. sam-goodwin commented on Nov 3, 2025

    @sam-goodwin
    MemberAuthor

    You're right. Standalone services like prisma/neon/etc. could be in their own package. Circularity is only a problem when a cloud provider has a service that can host runtime code (e.g. Lambda Function, Cloudflare Worker)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions