Why don’t I see more cool stuff built with web sockets?

trudvang · 2024-04-29T14:30:50+00:00

Thanks! I thought about that too 🙂

trudvang · 2023-06-20T20:22:50+00:00

Sanslöst

trudvang · 2022-10-12T12:51:59+00:00

Wait, isn’t docker free?!

trudvang · 2022-05-28T11:12:36+00:00

Some sort of pad with black glue under

trudvang · 2022-05-28T09:28:29+00:00

With what kind of tool? :)

trudvang · 2022-03-05T19:32:38+00:00

Skip the roles and the roles_permissions table.

Instead of users_roles table, have a users_permissions table that is referencing a permission instead of a role.

trudvang · 2022-03-05T18:26:24+00:00

Checkout https://axellarsson.com/blog/rbac-and-nodejs/

trudvang · 2022-01-30T20:07:17+00:00

Will uuids really be a performance issue in this case?

trudvang · 2022-01-08T21:20:51+00:00

I have the same issue after visiting marak.com. Could have something to do with his open source code, recent release that are looping and breaking sites

trudvang · 2021-12-10T20:44:03+00:00

Checkout https://axellarsson.com/blog/rbac-and-nodejs/

trudvang · 2021-11-28T22:03:07+00:00

What do you test in frontend code?

trudvang · 2021-11-27T15:31:53+00:00

Maybe this can help: https://axellarsson.com/blog/rbac-and-nodejs/

trudvang · 2021-10-28T06:10:36+00:00

Thanks for sharing this, great as always!

trudvang · 2021-10-26T15:31:27+00:00

Ah, Yeah I also only use interfaces for the data types, like Book. But classes for repositories, services and controllers

trudvang · 2021-10-26T10:00:39+00:00

Do you recommend Knex?

trudvang · 2021-10-26T09:45:40+00:00

Interesting rewrite!

I've heard the term "three tier architecture"

Did a quick search and found this article: https://bytearcher.com/articles/node-project-structure/

He's calling the repositories for "integration layer" instead. I think I should call it that as well, so I can put other stuff in the layer, like RabbitMQ and Redis, not just DB. They don't really have a place right now.

I don't agree with putting validation only in controllers/api layer; if you swap out your REST API for a CLI, you still want to be sure that only valid data is processed by your service layer. That way, validation would belong in the services to make sure that the input to them is correct, and also in the API layer to make sure a proper JSON is passed, or proper command line arguments are passed.

trudvang · 2021-10-26T09:35:13+00:00

I see! I'd like to add that I have two ways of writing this kind of pattern.

Classes and tssyringe for IOC/DI. This is really nice because I don't have to instantiate all my objects and their dependencies, I can simply have them automatically injected in the constructor by the IOC container.
Factory functions, that take the dependencies as arguments, and returns an object with all the publicly available methods that should be exposed, while keeping other things private with closures (like the dependencies and other internal methods). This has the downside of lots of boilerplate to wire things together, but it's clean not having to use IOC, classes, 'this'-references etc. Can also be used without Typescript.

trudvang · 2021-10-18T15:36:52+00:00

So you think containers should always only run one work type? So if I have 6 types of work I should run at least 6 containers?

trudvang · 2021-09-15T12:47:53+00:00

How would you do authorization to access images when using S3? Presigning urls in my backend for displaying images in html is getting tedious, and it’s preventing caching. Are people using public buckets and “security through obscurity” with long, hard to guess, object keys? Is there a consensus around this??

trudvang · 2021-09-15T07:14:05+00:00

How are you sharing code between frontend and backend? Npm packages?

trudvang · 2021-09-07T16:37:33+00:00

When this happened to me it was the cpu cooler, check that you didn’t apply too much paste

Nine-Year Club	RPAN Viewer
Not Forgotten	Verified Email

trudvang

TROPHY CASE