MERN-template VS Nest

Anyway, the structure of this website uses microservices, driven by an engine I dubbed the MERN-template. It has it's own auth service, and supports both chat and a news feed. The game-specific elements are closed-source though (the idea is you fork the core repo, and build out from there).

i use mariadb, but yes.

Backstory: Decade Jam, a game jam that lasts for a decade, began Jan 1st, 2020. I started writing a web game called Egg Trainer, but after a year of work realized that my codebase wasn't workable anymore. So at the beginning of 2021, I began working on a game engine that would power the beta version of ET - this is called the MERN-template (clearly, I'm bad at naming things).

My MERN-template actually uses MySQL. There's no requirement that you do it one specific way.

I'd use the MERN-template project that I wrote myself. It's essentially the mern stack, except with MySQL.

I've basically written this thing from the ground up, including an open source engine that uses microservices.

Anyway here's my game engine.

Oh, I've done this with my MERN-template. It was designed to power my game, but I made it available for others to use.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

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/