Primary key and foreign key links from different Db in different hosting Laravel

This can be a dangerous path you are following....

What if you want to change something in the student script or the DB architectuur .. Or there is a patch needed for a db. It means you have to go to each school and do an upgrade manually. I would rather expand my servers so you have one single place where your code and Database resides. And let's say 100 schools with 1000 students will give you a table of 100.000 , which is fine in databases. The only thing you should test on , is the amount of requests a minute you will receive. Will all those 100.000 students do the test at the same time ? Then an optimized code and a couple of server nodes should do the trick.... Especially if you host it for example in a cloud that automatically expand the server requirements.

But let's say you still want to continue with your plan. I would create an API on hosting A with the questions I would ask once all the questions and cache it. But there still will be 100.000 requests of each student for the questions...

@hondnl thank you for your response.

Ya i understood. but what my plan, is when each school registers it will became a separate db in separate hosting,. so that when when n number of school adds it takes n number of db and hosting.

why this because, when any server issue occurs or any school left i can easy remove that db. but when all school mixed in same db means remove a single school and separating a single school from the db is difficult i think so.

only the question bank resides in separate db hosting. that question is shared by different hosting and different schools

is this form ok

else suggest please