Laravel Separate Admin Model and Guard: WHY?

Summary

In this video, the speaker discusses the pitfalls of using separate Eloquent models for regular users and admin users in Laravel applications. He argues that this approach leads to duplicated code and unnecessary complexity, especially for junior developers. Instead, he advocates for a single user model supplemented with roles and permissions via Gates, Policies, and packages like Spatie. He acknowledges exceptions, such as legal compliance scenarios, where separation may be justified. Overall, the speaker emphasizes the importance of thoughtful design choices to avoid confusion in long-term project maintenance.

Takeaways

• 😀 Using separate guards for admin and regular users can lead to confusion, especially for junior developers.
• 👩‍💻 It’s important not to confuse guards with roles and permissions; they serve different purposes.
• 📄 Code duplication occurs when having separate user models for admins and regular users, which complicates maintenance.
• 🔄 Implementing API functionality requires clear decisions on which user model to modify, leading to potential confusion.
• 🔍 Adding shared functionalities, like activity logs, becomes challenging with multiple user models due to code repetition.
• 🏗️ Maintaining two separate Eloquent models for users can lead to increased complexity in project support and development.
• 📊 If separate user tables are needed, consider using a single user model with roles and additional profile tables for specific user types.
• ⚖️ In some cases, legal or compliance requirements may justify separate user models, such as in healthcare applications.
• 🚦 Decisions regarding user models should be made early in the project to avoid confusion and support challenges later on.
• 💬 Engaging with the developer community to discuss experiences with separate models can provide valuable insights and best practices.

Q & A

What is the main topic of the video?

The video discusses the use of Eloquent models in Laravel, specifically the separation of user roles into different models (like admin and regular users) and the potential issues this can cause.

Why does the speaker believe separating users into different models is often wrong?

The speaker argues that separating users into different models can lead to duplicated code and increased complexity, especially for junior developers who might confuse guards with roles and permissions.

What does the speaker suggest is a better approach than having separate models for users and admins?

The speaker suggests having a single user model and adding roles and permissions on top of it using Gates, policies, and packages like Spatie Laravel Permission.

What are the implications of having separate models in terms of database design?

Having separate models may require multiple foreign keys or polymorphic relationships, leading to a more complicated database schema.

What does the speaker mention about Laravel's built-in functionality for API authentication?

When setting up API authentication in Laravel, the speaker highlights the requirement to add 'HasApiTokens' to the user model, which can be confusing if there are multiple user models.

In what scenarios does the speaker think having a separate admin model might make sense?

A separate admin model might be justified in situations where there are legal or compliance requirements to keep user data separate, such as in healthcare settings.

How does the speaker address the issue of code duplication in the context of user models?

The speaker points out that having multiple models with similar functionalities results in duplicated code, which can complicate maintenance and updates.

What should teams consider when deciding to use guards in their Laravel applications?

Teams should consider the long-term implications of maintaining multiple Eloquent models with similar behavior and the potential confusion this may cause in the project.

What are some features or behaviors that need to be implemented in a user model?

The user model typically requires features like authentication, session management, and behavior tracking, such as created by user ID and updated by user ID.

What does the speaker encourage viewers to do at the end of the video?

The speaker encourages viewers to share their experiences and thoughts in the comments, particularly regarding the use of separate Eloquent models for users and admins.