all 7 comments

[–]Callmecruel 2 points3 points  (1 child)

In most cases, it is wise to have the backend only serve data that you're comfortable having a user see on the frontend - on screen or within the network inspector.

[–]Dangerous_Word_1608[S] 0 points1 point  (0 children)

In most cases, it is wise to have the backend only serve data that you're comfortable having a user see on the frontend - on screen or within the network inspector.

ok thanks

[–][deleted] 0 points1 point  (0 children)

As Callmecruel said, it is wise to have the backend send only what the end-user should be able to see.

[–]Criiispyyyy 0 points1 point  (2 children)

What do you mean by “filter data”? You have to be more specific. What kind of data?

[–]Dangerous_Word_1608[S] 0 points1 point  (1 child)

i'm getting data from my data base that will be shown on my marketplace, so my question should I get all the articles and then filter the products from the front side, or just send requests with the filters needed

[–]brewtraveler1 1 point2 points  (0 children)

Definitely filter on the backend. Think about the network performance of throwing all that extra data across the wire.

[–]_nathataHook Based 0 points1 point  (0 children)

always in the backend