Next.js Discord

Discord Forum

Why Vercel is that bad compare to Amplify and others ?

Unanswered
Pacific herring posted this in #help-forum
Open in Discord
Pacific herringOP
After several tests on Vercel, my app faces unbearable issues - extremely slow loading (even infinite loading and have to hard refresh), repeated client-side errors, and no caching whatsoever. The purpose of this thread is not to criticize Vercel for free, but as a student, I'd like to understand the root of these problems. Is it because of me or my NextJS app?

What's odd is that everything works perfectly on AWS Amplify. While I occasionally encounter client-side errors, they are very rare, and caching works seamlessly. Here's a short video comparing the two.

This is on Vercel :

9 Replies

Pacific herringOP
This is on Amplify :
No infinite loading, previous content is cached, etc...
Pacific herringOP
no idea about that ?
I probably plan to buy Vercel pro plan but if my app just doesnt work its useless
Trigg Hound
Hi - I really recommend the 'learn' tutorial at https://nextjs.org/learn I found it really good at explaining how to optimise apps including explanations around caching and streaming. Have you tried that yet? I don't think it is a Vercel backend issue as they have similar sites running really quickly.
aardani
what caching strategies have you employed?
@aardani what caching strategies have you employed?
Pacific herringOP
Okay the problem only append here on my user route, I have this in my next.config.js :
  async redirects() {
    return [
      {
        source: '/settings',
        destination: '/settings/profile',
        permanent: true,
      },
      {
        source: '/user/:username/:path*',
        destination: '/@:username/:path*',
        permanent: true,
      },
    ];
  },
  async rewrites() {
    return [
      {
        source: '/:lang/@:username/:path*',
        destination: '/:lang/user/:username/:path*',
      },
    ];
  },

Because I wanna user profile are accessible with /@username not with /user/username
Pacific herringOP
So there is a problem with cache, and its working in dev mode (local) and AWS