The Full CRUD Workflow in Laravel

Complete CRUD Flow

// routes/web.php
Route::resource('posts', PostController::class);

// PostController.php
class PostController extends Controller
{
    public function index() {
        $posts = Post::with('user')->latest()->paginate(10);
        return view('posts.index', compact('posts'));
    }

    public function create() {
        return view('posts.create');
    }

    public function store(Request $request) {
        $validated = $request->validate([
            'title' => 'required|max:255',
            'body' => 'required|min:10',
        ]);
        $post = auth()->user()->posts()->create($validated);
        return redirect()->route('posts.show', $post)
            ->with('success', 'Post created!');
    }

    public function show(Post $post) {
        return view('posts.show', compact('post'));
    }

    public function edit(Post $post) {
        return view('posts.edit', compact('post'));
    }

    public function update(Request $request, Post $post) {
        $validated = $request->validate([
            'title' => 'required|max:255',
            'body' => 'required|min:10',
        ]);
        $post->update($validated);
        return redirect()->route('posts.show', $post)
            ->with('success', 'Post updated!');
    }

    public function destroy(Post $post) {
        $post->delete();
        return redirect()->route('posts.index')
            ->with('success', 'Post deleted!');
    }
}

CRUD Best Practices

• Always use Route Model Binding (Post $post) instead of Post::findOrFail($id) — Laravel handles 404 automatically and controllers stay clean
• Use $request->validated() instead of $request->all() — only pass fields that passed validation rules, preventing mass-assignment vulnerabilities
• Apply $this->authorize('update', $post) in edit/update/destroy to ensure only the owner or admin can modify records
• Use eager loading (Post::with('user', 'tags')) on index to prevent N+1 query problems — one query instead of one per post
• Chain ->with('success', 'Created!') on redirects so users get confirmation feedback without extra code in views

Industry Best Practices

• Always write tests for this functionality - it's the most reliable way to catch regressions when you refactor or update packages
• Follow the single responsibility principle: each class does one thing. If a method grows beyond 20 lines, consider extracting helper methods or moving logic to a service class
• Profile performance with Laravel Debugbar (composer require barryvdh/laravel-debugbar) during development - it shows query counts, memory usage, and request timeline
• Keep dependencies up to date: run composer audit regularly to check for security vulnerabilities in your package dependencies
• Document validation rules with comments explaining why - e.g., // max:5 because users complained about spam when unlimited

Tip

Practice Task

Quick Quiz

Common Mistake