Part 3: API Routes in Next.js
Overview
Welcome on board! In this series of articles, you'll learn everything you need to know about Next.js through project-based learning so you can get started with Next.js. If you have no idea what Next.js is, I highly recommend you to check out...
eugenegoh.hashnode.dev4 min read
Recently I've started work on a next.js project (eCommerce with a chat & notifications) which uses a REST backend on an external API server, as well as the build-in API routes of Next.js. My idea is that I will use the backend server for stuff like WebSockets and cron-jobs. I then want the Next.js API routes to handle the authentication of users, fetching of data, and anything else that isn't limited by server less functions. In my mind, this sounds like a good idea, but I'd be glad to hear your opinion on it azar shagle . Any glaring issues etc, anything I might not have thought of with this approach?