node-typescript-architecture
domain-driven-hexagon
node-typescript-architecture | domain-driven-hexagon | |
---|---|---|
8 | 68 | |
113 | 11,401 | |
- | - | |
3.5 | 5.2 | |
6 months ago | about 1 month ago | |
TypeScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-typescript-architecture
-
Best file structure for node js project
It's opinionated, and it's self promotion, but this is what I've used for every project of mine since 2020: https://github.com/jbreckmckye/node-typescript-architecture
-
Ask HN: Web frameworks – which less popular framework are you using and why?
Self-plug: I wrote this Node / TypeScript port of "clean architecture" to typed, functional JavaScript two years ago - and it's served me well on every production project ever since
https://github.com/jbreckmckye/node-typescript-architecture
-
Moving to NodeJS
Node TypeScript Architecture repo by Jimmy Breck-McKye (https://github.com/jbreckmckye/node-typescript-architecture) as a fan of TypeScript this will be extremely helpful for me to see how to structure a TS based Node app
-
How do people find time and energy for (large) side projects?
I would also say that certain practices are invaluable for working efficiently, just as they are in a job. I don't unit test my open source work particularly religiously - to be honest, I don't feel it gives me much more confidence. But I do have a personal architecture (based on ports and adapters, if you're interested), that I stick to because it always allows me to keep my pure logic and IO / effects code strictly separated.
-
Reference Design/Architecture document
May I share this? https://github.com/jbreckmckye/node-typescript-architecture
- Domain-Driven Hexagon - DDD, architecture, best practices (Full project using NestJS)
- NTA: An opinionated (work in progress) architecture for writing Node TypeScript apps, with functional DI/IOC and runtime type validation
- Show HN: An opinionated architecture for Node/TypeScript apps
domain-driven-hexagon
-
From Frontend to Backend
That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/
-
How to Become a Node.js Backend Developer? Share Helpful Resources!
Domain-Driven Hexagon - architecture (NodeJS code examples)
-
Best file structure for node js project
Can't use any frameworks or libraries? Seems like a terrible idea tbh. I can suggest this repo https://github.com/Sairyss/domain-driven-hexagon - read "modules" and "folder and file structure" sections for some suggestions on how to structure files using patterns like Modular Architecture, Vertical Slicing, etc. Make sure to read the attached links and check code examples.
-
i just made an equation solver using constraint propogation in style of sicp
This is a reasonable intro, furthermore it points out more resources if you would he interested: https://github.com/Sairyss/domain-driven-hexagon
-
Anyone using CQRS in production? Does it really have any benefits?
I’ve recently refactored one of my key domains using nestjs/cqrs and was heavily inspired by this repository.
-
Clean architecture in real world app?
Not a big one, but explains how to combine architectures like clean architecture, domain-driven design, hexagonal, etc. https://github.com/Sairyss/domain-driven-hexagon
-
Recommended practices for better Angular large application architecture, project structure
I strongly recommand this: https://github.com/Sairyss/domain-driven-hexagon
- Examples of APIs that follows the best practices and are production ready on Github?
-
[AskJS] How to architect a JavaScript (backend) app that can scale?
Here is an example codebase with architectural patterns described more in details: https://github.com/Sairyss/domain-driven-hexagon
- Complex business logic in Node
What are some alternatives?
io-ts-promise - io-ts for developers who like Promises
typescript-clean-architecture - It is my attempt to create Clean Architecture based application in TypeScript.
fastapi-fullstack-boilerplate - A full stack boilerplate for FastAPI [Moved to: https://github.com/tmkontra/fastapi-fullstack-boilerplate]
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
fullstack-starter-template - Template for full stack applications based on TypeScript, React, Vite, ChakraUI, tRPC, Fastify, Prisma, zod, etc.
nestjs-config - Config module for nestjs using dotenv :key:
nodebestpractices - :white_check_mark: The Node.js best practices list (February 2024)
nestjs-starter-rest-api - NestJS Starter Kit. Monolithic Backend. REST API.
clog - CLOG - The Common Lisp Omnificent GUI
bulletproof-nodejs - Implementation of a bulletproof node.js API 🛡️
remix - Build Better Websites. Create modern, resilient user experiences with web fundamentals.
express-typescript-skeleton - 🔰🦸 Template to start developing a REST API with Node.js (Express), TypeScript, Ts.ED, ESLint, Prettier, Husky, Prisma, etc.