![[The AI Show Episode 144]: ChatGPT’s New Memory, Shopify CEO’s Leaked “AI First” Memo, Google Cloud Next Releases, o3 and o4-mini Coming Soon & Llama 4’s Rocky Launch](https://www.marketingaiinstitute.com/hubfs/ep%20144%20cover.png)
![Is This Programming Paradigm New? [closed]](https://miro.medium.com/v2/resize:fit:1200/format:webp/1*nKR2930riHA4VC7dLwIuxA.gif)
-Classic-Nintendo-GameCube-games-are-coming-to-Nintendo-Switch-2!-00-00-13.png?width=1920&height=1920&fit=bounds&quality=70&format=jpg&auto=webp#)
![M4 MacBook Air Drops to New All-Time Low of $912 [Deal]](https://www.iclarified.com/images/news/97108/97108/97108-640.jpg)
![New iPhone 17 Dummy Models Surface in Black and White [Images]](https://www.iclarified.com/images/news/97106/97106/97106-640.jpg)
Architecture for TypeScript backend with multiple entry points or apps [closed]
I suspect this is a solved problem because I'm not doing anything very unusual, and yet I'm struggling to work out a sensible structure for my TypeScript/Node.js backend. Briefly, the project consists of: a database (Postgres) a data access layer encapsulating database queries a service layer encapsulating business logic several executable entry points: an API server some scheduled jobs some Lambda functions We're a small team and we don't want to manage a herd of microservices. But at the same time I want to avoid a tightly coupled monolithic architecture that's hard to reason about and makes CI pipelines slow. Ideally I would like to separate the data access and service layers into packages which the apps then consume (all in a monorepo). But where I'm falling over is how to manage shared configs. I'm looking for a solution that: Ensures each app has the config that it needs, type checked at build time and validated at runtime Allows the packages to make use of shared services which themselves need config. e.g. a database connection or a logger object The project is deployed to AWS but I'd like to avoid vendor-specific solutions if possible.
![Architecture for TypeScript backend with multiple entry points or apps [closed]](https://cdn.sstatic.net/Sites/softwareengineering/Img/apple-touch-icon@2.png?v=1ef7363febba)
I suspect this is a solved problem because I'm not doing anything very unusual, and yet I'm struggling to work out a sensible structure for my TypeScript/Node.js backend.
Briefly, the project consists of:
- a database (Postgres)
- a data access layer encapsulating database queries
- a service layer encapsulating business logic
- several executable entry points:
- an API server
- some scheduled jobs
- some Lambda functions
We're a small team and we don't want to manage a herd of microservices. But at the same time I want to avoid a tightly coupled monolithic architecture that's hard to reason about and makes CI pipelines slow.
Ideally I would like to separate the data access and service layers into packages which the apps then consume (all in a monorepo). But where I'm falling over is how to manage shared configs.
I'm looking for a solution that:
- Ensures each app has the config that it needs, type checked at build time and validated at runtime
- Allows the packages to make use of shared services which themselves need config. e.g. a database connection or a logger object
The project is deployed to AWS but I'd like to avoid vendor-specific solutions if possible.