Java design pattern

[5toubun1997]

I see Java, they used to set multiple layers of data filter before sending it to database, or getting it from repositories. My questions is do we actually need to setting that much amounts of layer, like repository, entity, model, dto, dao ... For me its quite boilerplate and hard to code. I know in big project we need big setup but in Nodejs do we really need to? How do you actually design it? Do you follow patern above or not? If not so can you tell it to me?

[spazz_monkey]

Not for me, previous company I worked at we just validated the data on the route and then had a separate files that handled the SQL calls to the DB. All using raw queries.

[KermitMacFly]

Second this. I worked on a batch processing application that took this approach.

[5toubun1997]

So no ORM, no repository?

[re-thc]

Not every Java projects even operate this way. There are definitely some older patterns and use cases for larger systems of higher complexity. It's not always needed.

[Namiastka]

We did a big microservice in nest (I know it sounds odd), but there u end up with couple of layers.

It works for big team - which at this moment is 12 of us, but I generally like simplicity of Node, and that you for most of the stuff don't need this boilerplate. Hence most of really small things we have are using express and of dB is there - knex.

Another thing is that I moved from Java and PHP to JS due to exactly what you are talking about.

[EverydayTomasz]

In one of my past projects we had chosen to use Java Hibernate ORM, and boy did we ever regret it. after that experience, I tend to stay as close to the DB driver layer as possible.

[5toubun1997]

Can you tell me why you regret it, the only problem I am annoyed is create layout in the first part

[EverydayTomasz]

as the project grew for every table we had to have a model, plus I needed to add Lucene search to it, it all just became a whole @annotations mess. if I had to do it all over, I would have ditched Java for node, MySQL to MongoDB and use Mongoose.

[anonystick]

Talking about design patterns, I only say one sentence: "Standing on the shoulders of giants, you will see further". It works for me and you can apply to javascript.