I have already answered in my previous comments with details. I have already shared three examples where one endpoint per route isn't the best solution.
If these drawbacks doesn't applied to you, it's a good news and the pattern you have followed is the best solution for you.
But, it doesn't mean we all need to follow the same pattern. There isn't only one way to do it.
Ok I didnβt catch your resources limit argument ! Sorry. :-)
And I think what Rob said, he is agree with you but we should not use this pattern when the latency is important for the UX, meaning we need to keep a low coldstart, to be able to respond as quickly as possible :-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have already answered in my previous comments with details. I have already shared three examples where one endpoint per route isn't the best solution.
If these drawbacks doesn't applied to you, it's a good news and the pattern you have followed is the best solution for you.
But, it doesn't mean we all need to follow the same pattern. There isn't only one way to do it.
I really don't know what I can add more.
Ok I didnβt catch your resources limit argument ! Sorry. :-)
And I think what Rob said, he is agree with you but we should not use this pattern when the latency is important for the UX, meaning we need to keep a low coldstart, to be able to respond as quickly as possible :-)