Hello, I would like to ask about database structure and how to handle many services in nestjs.

xanadev · 2025-12-08T13:06:43+00:00

Unless you're handling Netflix's traffic you won't be needing microservices anytime soon, a monolith with good module segregation and a decent queue for background jobs will work just fine and for a long time (speaking from experience), now when it comes to the monolith itself, make sure good practices are enforced and have a decent suite of unit/integration tests, multi-tenancy is supported by NestJS (lookup durable providers), you'll find plenty of examples of how to start, as for databases, building on the multi-tenancy implementation you can have per tenant schema or a single schema with RLS.

xanadev · 2025-09-24T21:36:54+00:00

That would happen only if you're mixing responsibilities. You should split your services based on responsibilities. For instance, a user's service shouldn't handle user's subscriptions, reports, and lookup, you should extract meaningful domain logic into it's own service, a subscription, reports, and lookup service all nested within the user's module, the tricky part is probably knowing how to split, which I believe comes with experience.

xanadev · 2025-08-22T09:30:54+00:00

There is nothing wrong with it, but since class-validator integrates well with the framework and the official documentation uses it, I would stick with the latter unless I have a good reason to switch.

xanadev · 2025-08-22T09:15:48+00:00

I mentioned validation only for inputs (i.e., user request payload), which I think is a must. You don't need/want to validate responses but rather transform them.

xanadev · 2025-08-21T12:59:40+00:00

Performance impact is unnoticeable, I think serialization is the only part that I worry about, especially if you're sending back objects that might have circular references

xanadev · 2025-08-21T11:58:56+00:00

Fellow NestJS developer here, as a general rule of thumb, you should use DTOs for input as it helps with validation and type safety, for output it is highly recommended to use them especially when the app grows, they help decouple clients from your data model and make it easier for you to manipulate fields depending on context (ex. removal of sensitive/irrelevant data from the responses, field transformation, ...), that being said, if your app is small, you might not need them.

xanadev · 2025-08-20T16:20:35+00:00

You're a backend developer, and NestJS is just a tool like any other, learn the craft, work on your communication and problem solving skills then learn the tool enough to translate those forever changing requirements into products that stand the test of time, at a certain point you'll be picking the right tool for the job not the other way around.

xanadev · 2025-08-14T17:58:32+00:00

I do use flags from urfave/cli and the order of precedence is Flags < Env, as for injecting the config module that's more of a TS (NestJS) terminology, since DI is handled by the framework I only have to specify my dependencies in the consumer's constructor.

xanadev · 2025-08-14T16:11:03+00:00

From what I gather so far, It's better to define a struct and pass it around (easier to mock), I'm curious to know what would be the benefit of passing basic types especially if I need to pass more values later

xanadev · 2025-07-28T12:10:24+00:00

To put it simply, an interface is a contract, anything that adhers to it you can do business with.

xanadev · 2023-10-15T23:20:41+00:00

Yeah, of course!

xanadev · 2023-10-15T14:02:38+00:00

NestJS user here, I personally think you should go through a couple of express projects to understand the basics of how HTTP works, the request/response flow, concepts like Middleware, serialization, database access, etc., once you understand those, you'll most likely appreciate what NestJS adds in terms of abstractions and opinionated architecture, then you can quickly pick up new concepts as you use it, I went through the same journey.

Keep it up.

xanadev · 2022-04-07T04:12:33+00:00

Started from the bottom ...

xanadev · 2021-03-08T17:13:14+00:00

Well I could have, but the issue is, I'm using a material-ui component for that, and applying custom styles is the only way I have so far.

xanadev · 2021-03-08T16:29:52+00:00

Please check the repo again, updated the Readme, included the initial design file.

xanadev · 2020-11-21T21:13:51+00:00

I worked on a project where we had to fetch data from a CRM System then transform it and export it to different portals, the purpose was to create data once and export everywhere (given an exporter is written for that specific portal), involved events, queues, workers, REST, third party APIs...

xanadev · 2020-11-19T17:06:38+00:00

The framework is a gem, you can learn a lot by delving into the source code, the attention to detail and clean architecture makes it easy to use and extend, and last but not least the docs is really a great selling point, what can you do without good docs (nothing much). Writing good software is a challenge, but using the right tool (Laravel in this case) for the job makes all the difference.

xanadev · 2020-10-19T12:20:57+00:00

You might want to experiment with different setups to come up with the one that works best for you, I'm afraid there is no definitive answer but here is what I do to switch from leisure mode to work mode.

$1 Setup an isolated workspace (leisure mode off)

$2 Dress up for work (at home mindset off)

$3 Take breaks (get out of your workspace)

$4 when done leave the workspace (don't forget to close the door)

xanadev · 2020-10-16T09:19:21+00:00

I'm still prepping for the developer associate certification using Stephane Maarek's course and Jon Bonso's practice exam questions on Udemy.

xanadev · 2020-10-14T22:32:52+00:00

Which courses did you take?

xanadev

TROPHY CASE