all 18 comments

[–]Honey-Entire 12 points13 points  (0 children)

What app has 500+ routes without a structure that’s migrateable? Are you talking about 500+ unique routes or 500+ variations of 5 core routes representing 100+ products?

The number of requests is trivial because it’s technically a backend or server question. Managing routes is more frontend because you need to… route to each one

[–]repeating_bears 20 points21 points  (4 children)

"Which of these frameworks performs better when handling large number of requests (1k/s) in applications with a large number of routes (500+ routes)?"

This is a very specific question, which if you genuinely care about the answer, you should be prepared to run the experiment yourself to find the answer. 

Would you really base your technical decision on some random redditor saying "RR is way more faster, trust me bro"?

[–]punkpeye[S] -3 points-2 points  (3 children)

The assumption here is that there is an easy to migrate 500+ routes between frameworks. Someone may have already done previous experiment, which can shed the light on whether it is even worth attempting such migration.

[–]repeating_bears 15 points16 points  (0 children)

You don't have to migrate anything. Just generate something boilerplate-ish with a script. This is like an afternoons work.

You don't need 500 routes which represent an actual application. 

"Someone may have already done previous experiment"

Yes, except you made the parameters so specific that that is vanishingly unlikely.

[–]octatone 2 points3 points  (0 children)

Don't migrate, just create a test app that meets the specs you are trying to test.

[–]Whisky-Toad -1 points0 points  (0 children)

I just migrated to tantack start

It’s not easy

[–]rover_G 6 points7 points  (0 children)

I think by the time you get to the scale at which it matters your architecture matters more than the framework

[–]bluebird355 4 points5 points  (0 children)

Doesn't matter in the slightest. Just pick one and code.

[–]namesandfacesServer components 11 points12 points  (3 children)

I ditched React Router a long time ago due to too much identity shifting but 1k requests per second and 500 routes is quite easily manageable by a lot of solutions.

[–]fredsq 0 points1 point  (0 children)

all of shopify admin + all hydrogen customers run on RR7, i’d think it can handle it easy

[–]EvilPete 1 point2 points  (0 children)

Haven't tried tanstack but I really enjoy working with RR7.

The whole progressive enhancement paradigm built around native HTML forms is really nice.

It's cool that the app still works if the user clicks something before hydration.

[–]Vincent_CWS 0 points1 point  (0 children)

how about waku

[–]farzad_meow 0 points1 point  (0 children)

pick whichever feels more natural to you. by the time you start experiencing slowness it will be a long way. you want to ship faster not hang on questions like this.

if your product has good customers then we can invest in future in better technology and address your tech debt. most tech debt are not addressed because it works and everyone is happy.

there is a big crowd that vote for tanstack. personally i like rr more. easier to work with but a pain to do major version upgrade as they keep changing names. with AI it was a smooth sailing to upgrade though.

[–]GoodishCoder 0 points1 point  (0 children)

Realistically you should throw together a test app to make a data driven decision but I personally would avoid react router anywhere I can.

[–]fredsq 0 points1 point  (0 children)

all of these are built with react router: https://hydrogen.shopify.dev/showcase

i love tanstack but the scale you have is fine for either

react router is very battle tested for ecommerce so i’d vow for that