ExpressJS

Hello! For your Node.js/Express.js project, it is recommended to use NYC as the code coverage tool. Make sure you configure NYC in package.json, for example:

"nyc": { "reporter": ["text", "html"], "include": ["backend//*.js"], "exclude": ["test//*.js"], "all": true } Then run the test through the command:

nyc mocha path/to/your/test/*/.js Make sure your test cases cover all API endpoints so that the coverage can be accurately reflected.

In addition, for node.js projects, I have a very useful suggestion, that is, before the project starts, you can use a development environment management tool like servbay to perform environment deployment, environment testing, etc., which greatly improves our efficiency

use SonarCube, that's what i think can help u with code coverage

Your stack (Next.js, Express.js, and PostgreSQL) is solid, but NestJS might be a better choice than Express.js.

NestJS provides better structure, scalability, and built-in features like authentication and dependency injection. Plus, since it uses TypeScript, your frontend and backend can share the same language, making development smoother.

If you want a more maintainable backend, NestJS is highly recommended.

I would use Framework7 React for my frontend and Supabase to store the data. Framework7 is mobile friendly, easy to use, and has tons of prebuilt features and components. Supabase is also easy to setup, has a free tier which allows a decent amount of data storage. And above all; it's API is super easy.

My advice: Next.js, PostgreSQL (supabase). Next.js can handle API routes natively, which eliminates the need for Express.js. You can define your own backend logic, such as handling database interactions (CRUD operations) through these routes. For UI/UX you could make use of Nyxbui + Aceternity (based on shadcn, framer-motion, and some other amazing frameworks/libs/modules). But only combine nyxbui & aceternity if you feel confident with very advanced frontend logic, otherwise just use the basic Shadcn. Do not forget to make good/secure RLS policies and take care how you are handling the caching for your routes when using next.js.

Your tech stack is solid for building a real-time messaging project.

React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

I built a very similar application with real-time chatting, and I used a very similar stack to yours (MySQL instead of Postgre). The stack that you chose is very good for what you want to make (or have already made since I am 2 weeks late).

I've heard so many things that I really don't know. Some people say that creating projects on GitHub helps. I got into my current job because my code from a bootcamp I did was better organized than another candidate's.

That was the criterion in the end... He called both of us for an interview and both did well.

Is that a good tiebreaker? I don't know. But a lot of things in life are about luck. Since luck is a skill that can be learned, I'll give you a tip.

Code, program a lot and make it clear to people who search for you on Linkedin, Github, etc. that you know what you're doing and that you're doing it. Because if they search for you and don't find anything, no projects or anything like that will look really bad.

I would trade Express for Fastify.js. It's MUCH better and is maintained by Matteo Collina. He knows a lot about JavaScript, so much so that he's on the Board of Directors of the Open JS Foundation. He is also a TSC (Technical Steering Committee) voting member for Node.js.

I would follow him to learn more about JavaScript backend. But switch to TypeScript as soon as possible. For that, follow Matt Pocock, he is very good at TypeScript.

By the way, it is good to learn No-SQL with Redis too since Mongo died for the industry after the license change. Look for DynamoDB, but don't forget SQL like MySQL and PostegreSQL.

I wish you the best of luck! And happy coding.

Why would you allow your decision to be driven by the limitations of a hosting account? MySQL is a relational database, and typically you need a solid understanding of relational database design and SQL. MongoDB as a so called "Document database" is not relational. You can associate several MongoDB collections together if you understand the basic concepts behind, it, but in general, MongoDB does not have nor require a fixed schema. It can do many of the things a relational database can do, particularly if your data fits nicely into a hierarchical structure. It also often appeals to people like yourself that are working with a javascript stack, as the interface to MongoDB is json. If you can install a package onto your host, then you should be able to use MongoDB. With that said, you can do all your development locally using Docker containers. I would not suggest that you let important design decisions be dictated by what one shared host allows you to do.

I think you should use MySQL but with php or Python because e-commerce websites needs to be fast and reliable with more admin tools and you’ll find what you need and more in e-commerce when using php or python frameworks with MySQL database.

Example: Using django (python framework) with MySQL gives you administration dashboard that you can use to edit in a lot of things and django also supports a lot of things like generating ready forms linked to the models you generated

I do not recommend Vue for a job, learn React or Angular

Additionally Typescript for React is a wise choice. however, you can start using Javascript.

The open source web framework Express.js for Node.js enables programmers to create online apps and APIs. It offers a number of tools and functionality, including as templates, road handlers, renderers, and debugging tools, to make development simpler. The popular Express.js substitutes Koa.js, Hapi.js, Fastify, and Restify are also available.

8+ Hour Stream - 3 Giveaways - Build a Full Stack Forum with Node/Express/Postgres/Vue.js/Bootstrap https://www.youtube.com/watch?v=aqiJQaPDy7o

Look for tutorials on how to build a website, but don't get too caught up in the stack, it doesn't matter at your level. Just have fun, that's my suggestion. If you need some help, feel free to add me on discord

Sergueiovitch#4089

Hi Kelechi,

It is pretty easy. You will need to create and express.js API with Nodejs and have the Postgreql in it. Then you can create your Vue Apps and connect to the express API. This will help; https://www.youtube.com/playlist?list=PLWKjhJtqVAbnadueQ-C5keMQQiQau_i0D

I used a similar setup but I wouldn't recommend it except if you absolutely must. Use something like NuxtJs.

ML immediately tilts your decision towards Python as the ML ecosystem is in Python. Microservices can be programmed in Python. However, as you said, Python is slower than Node.js. This leads to a combination of both languages as the ideal solution. A problem in terms of skills, especially for a limited size team. It also raises the question of how you are going to connect the different microservices. If it is Kafka or MTMQ should not be a problem to connect services in the different languages. If you are limited in terms of size of team, choose Python. As you cannot go very far with Node.js for ML.

With the info you have shared so far, here's my recommendation: 1. Python ecosystem is very sophisticated for ML, AI. Build models, and perform most of background work via python. You can expose these models and any business logic needed via python Fastapi. 2. Node and js ecosystem is great for building both server rendered and Single page apps - whichever your preference is. You can easily use something like Next.js and build out the marketplace web/mobile application, interact with ML models via an api or directly read the model from node backend. Hope this helps.