orchid-orm-benchmarks
domain-driven-hexagon
orchid-orm-benchmarks | domain-driven-hexagon | |
---|---|---|
6 | 68 | |
12 | 11,427 | |
- | - | |
6.2 | 5.2 | |
6 months ago | 8 days 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.
orchid-orm-benchmarks
-
How do you create test cases for APIs?
Here are my tests for an example project. The logic is quite straightforward: create db records, make a request, check the response, and if it was a mutating request check how it affected the database.
-
Examples of APIs that follows the best practices and are production ready on Github?
And if you like to see a random example project here is mine, but my point is that a random project won't really help because each project has a unique set of frameworks/libs/practices and it changes almost everything.
-
Announcing a new TypeScript ORM
Or you can clone this examples repo and play with the Blog API code.
-
Is there a good example of a real world NodeJS API project?
I have an example app, and have written documentation based on it, and I'd appreciate it if you could look and give some feedback. Yes, the doc is about ORM, but imagine the ORM is just an implementation detail and instead look at how validations, controllers, repos, and especially tests are done. Source code, and long boring tutorial about it. Really, check the tests here, they are special. It doesn't have "service" because the app is too simple, but I usually have a service layer as a files with exported functions. Error handling is in app.ts.
-
Rate my project made with Express + TS
I keep all routes in a separate file: routes.ts, in case of multiple API versions it could be "routes.v1.ts", "routes.v2.ts" and so on. v1 and v2 can reuse the same controllers.
-
Writing & organizing Node.js API Tests the right way
I wrote some tests for sample app as well, maybe could be interesting for you to check it out: here, criticism is welcome, just as I like to criticize
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?
projecthunt-api - API for projecthunt a project hunting platform
typescript-clean-architecture - It is my attempt to create Clean Architecture based application in TypeScript.
swagger-petstore
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
nodejs-integration-tests-best-practices - ✅ Beyond the basics of Node.js testing. Including a super-comprehensive best practices list and an example app (March 2024)
nestjs-config - Config module for nestjs using dotenv :key:
survey-manager - A survey manager and creator project with node, typescript and react
nestjs-starter-rest-api - NestJS Starter Kit. Monolithic Backend. REST API.
node-rest-starter - A Node.js starter containing common components and services as a reference API.
bulletproof-nodejs - Implementation of a bulletproof node.js API 🛡️
kysely - A type-safe typescript SQL query builder [Moved to: https://github.com/kysely-org/kysely]
express-typescript-skeleton - 🔰🦸 Template to start developing a REST API with Node.js (Express), TypeScript, Ts.ED, ESLint, Prettier, Husky, Prisma, etc.