What are the main limits that strapi users can face when scaling their project?

I’m a python dev used to work with flask and django. I’ve never used strapi. I want to move faster with my prototype but I want to be able to expand it easily afterwards.
My project is a job hiring website where you have these three main tables :

Companies with media files (photos and videos of the companies)

Jobs : each company has a list of open job announcements it publishes

Blog articles : about best practices for job search

At first, the website doesn’t include accounts but in V2 it will have two types of accounts :

Company account : will handle their descriptions, media files and job announcements

Applicants : people who apply for jobs. They can upload their CV and see a list of applications they did and what version of CV they attached to them.

People should be able to connect social accounts like gmail and facebook.
In this V2 applicants will be able to use AI to get advice about their CV. Companies will be able to use AI to get an automatic classification of each applicant based on their relevance.
I’ll develop some AI APIs in django for that that I’d integrate to my project.

What do you think about using strapi for this project and having a second service written in python for the AI part?
What problems could I face in the future when the project scales to tens of thousands to users?

PS: I’ll be using Nuxt for front end.

This topic has been created from a Discord post (1289120570838876214) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

You’ll run into the classic nodejs scaling issues. Nothing related directly to Strapi.
Be sure to run a database that will scale with this like pg.
Cache a lot of stuff :smile: (http, objects, etc.)

I haven’t dug into user management on Strapi but nothing you describe seems to be an issue even if it would be easier with a framework.

Why were you looking at Strapi for this?

And as always, build something that works. You will have plenty of resources to refactor some components if that does not scale in the future :wink: