A Redditor questioned the necessity of using Redis with Next.js's App Router, considering Next.js already offers robust built-in caching mechanisms like data cache, route cache, and RSC caching [73↑].
Several users pointed out the importance of Redis for scenarios like session storage in multi-instance applications behind a load balancer [72↑, 22↑, 13↑]. Redis serves as a single source of truth for sessions with in-memory key/value storage and automatic expiration. Also it is useful for sharing cache across multiple servers.
Beyond caching, Redis offers powerful pub/sub capabilities suitable for push notifications and background task queues. It is also useful for rate limiting endpoints, managing concurrent access to resources, and storing short-lived items like one-time passwords, tokens, and sessions [15↑].
In essence, while Next.js's built-in caching is valuable, Redis addresses edge cases like horizontal scaling and specific backend functionalities, complementing Next.js's caching capabilities.
A Redditor shared their first website built with Next.js, created to facilitate efficient learning [72↑]. The author invited questions and feedback on their work [5↑]. The website is lurnall.com.
One user complimented the site as "Pretty cool!" [3↑], while another inquired about the screen recording tool used in the presentation [2↑]. The creator identified the tool as "Cursorful," a browser plugin [3↑].
A Redditor is facing issues with route management in their Next.js application after form submissions [7↑]. After submitting a form on a page, they use router.push() or router.replace() along with router.refresh() to redirect back to the previous page, but this adds the previous page to the history stack again. This results in the user needing to press the back button twice to navigate to the page before the list view. The user asks what the proper solution to avoid this behavior would be.
One suggestion advised using router.back() for routing, focusing on data updating issues [1↑]. Since the data wasn't updating, the user mentioned that ChatGPT said router.refresh() targets the current page before router.back() finishes navigating [1↑].
Another user suggested that manually refreshing may indicate an underlying problem in the approach to data fetching [2↑]. They requested more details on how the list page works, particularly how the data is fetched.
The user clarified that Page1 fetches data server-side, while Page2 submits data client-side, and another user suggested invalidating the cache or adding a query parameter to trigger a fresh data fetch after form submission to ensure the updated data is displayed [2↑].
A Redditor is seeking advice on hosting a system built with React and Supabase for a small jewelry business [2↑]. The system includes features for bookings, transaction records, and inventory management. The main concern is finding a suitable hosting solution without a domain, as it will only be used by the business's three employees, who expect around 10 customers daily. They are also considering wrapping the system in an .exe file as a last resort, preferring hosting for easier updates.
Several users suggested that Vercel's free tier could be sufficient [2↑],[2↑], although one commenter pointed out that commercial use might violate their terms [3↑],[3↑]. One user suggested that Netlify could be an alternative, also offering a free tier that might accommodate commercial use [3↑].
The original poster clarified that they would consider a paid plan to allow for commercial use [2↑].
In short, the conversation revolved around whether the system's commercial nature restricts the use of free hosting plans and the suitability of Vercel and Netlify.