Streamlining Appointment Availability: Implementing Express Controllers

Managing a beauty appointment system like beauty-appointment-system requires a clean, predictable way to handle client schedules. Recently, I focused on refactoring how we manage available time slots to ensure the system remains performant and easy to maintain as our user base grows.

The Complexity of Scheduling

In our initial implementation, logic for availability was scattered across multiple layers. Checking if a stylist was free felt like trying to find a book in a library where the catalog system had been replaced by a messy pile of index cards. Every request had to manually calculate slots, leading to redundant code and a higher risk of "double-booking" conflicts.

Moving to Controller-Based Logic

To solve this, I introduced dedicated controllers in our Express application. By decoupling the request handling from the business logic, we created a clear entry point for all scheduling queries.

Consider this simplified version of how we now handle availability checks:

import { Request, Response } from 'express';

export const getAvailableSlots = async (req: Request, res: Response) => {
  const { stylistId, date } = req.query;
  
  const slots = await availabilityService.findSlots(stylistId, date);
  
  return res.status(200).json({ 
    data: slots, 
    count: slots.length 
  });
};

This controller acts as a traffic director. It receives the request, delegates the heavy lifting to a service layer, and formats the response for the frontend. By isolating the logic, we can test the availability calculation independently of the HTTP request cycle.

The Resulting Gains

This refactoring resulted in a much more modular codebase. By moving the logic into specific controllers:

1. Improved Readability: Routes now clearly describe what they do without hiding complex database queries.
2. Easier Debugging: When an issue arises with scheduling, we know exactly which controller layer to inspect.
3. Testability: We can now write unit tests for our slot calculation logic without needing to mock the entire Express request/response chain.

The Takeaway

Think of your controller layer like a high-end receptionist at a salon. You don't want the receptionist cutting hair (business logic) while they're also greeting clients and answering phones (request handling). By separating these roles, the entire system runs smoother, and your developers spend less time untangling spaghetti code.

Generated with Gitvlg.com