You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am leaning mono-package because of the circularity:
AWS Lambda has bindings for Cloudflare
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
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)
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)
Activity
suddenlyGiovanni commentedon Nov 3, 2025
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)
sam-goodwin commentedon Nov 3, 2025
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)
refactor(proxmox): unify credentials into ProxmoxEnvironment
fix: restore the floci submodule pin to main's