Support the ongoing development of Laravel.io →
Architecture Database Eloquent

Hi all, I’ve recently been playing around with Larvel and building a sample project to try and wrap my head around the basics which I think I’m coming to grips with now.

Quick question, let say I decided I want to build a SASS App. A booking system or client manager for example.

I know how to do all the Auth with subscriptions and taking payment etc what I’m unsure on, is the correct way to store each users data.

Let’s use the client manager for example. Even if it’s just a simple project that has client name, number, email & phone.

Where does each users client details go?

Do I have a table of clients, create many to many relationsships and set up and pivot table to match clients to users?

Let’s say my idea takes off and I end up with 10,000 users of the worlds worst client manager 😂

Each user has 100 clients that’s 1,000000 records. I know that’s not really a lot in the grand scheme of things but seems a lot of records to get through just to pull 100 back for my current user.

Hope this make sense and hopefully someone can explain if this would be the right route or not.

Last updated 3 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

Craig cib88 Joined 20 Feb 2021

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2025 Laravel.io - All rights reserved.