Custom Deadline and Schedule System for LMS

Custom Deadline and Schedule System for LMS

Students miss deadlines, instructors waste hours on manual reminders, and course completion rates suffer. That's the exact problem we solve with a custom-built deadline and schedule engine for any LMS. Over the past 5 years we've delivered 20+ such projects for online schools and universities. Our system boosts assignment submission rates by 40% (validated by client data) and saves instructors up to 10 hours per week.

Why a dedicated deadline and schedule system is critical

Without automation, students lose track of due dates and live sessions. Instructors manually send reminders—time that could be spent teaching. Our system fully automates the process: from generating a course schedule to sending push notifications 15 minutes before a class. It uses a task queue (Bull/BullMQ) that is 3× more reliable than basic cron jobs.

Two course modes

Self-paced — students progress at their own speed. Deadlines are relative: "Submit within 7 days of starting the lesson." No schedule.

Cohort-based — a group with fixed dates. Absolute deadlines and a class schedule (webinars, seminars). Students enroll in a specific cohort.

How we set up notifications without spamming

We use a task queue (Bull/BullMQ) and configure rules: a notification is sent only if the assignment hasn't been submitted. Intervals: 7 days, 24 hours, 3 hours before the deadline. For classes: one day and 15 minutes before. Everything is managed from a single dashboard.

Data model (PostgreSQL example)

-- Cohorts
CREATE TABLE course_cohorts (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  course_id       UUID REFERENCES courses(id),
  name            VARCHAR(200),           -- 'Cohort #5, March 2026'
  starts_at       DATE NOT NULL,
  ends_at         DATE,
  max_students    INT,
  enrollment_open BOOLEAN DEFAULT TRUE
);

-- Assignment deadlines
CREATE TABLE assignment_deadlines (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  assignment_id   UUID REFERENCES assignments(id),
  cohort_id       UUID REFERENCES course_cohorts(id),
  deadline_at     TIMESTAMPTZ,
  relative_days   INT,
  late_allowed    BOOLEAN DEFAULT FALSE,
  late_penalty_pct INT DEFAULT 0
);

-- Schedule events
CREATE TABLE schedule_events (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  cohort_id       UUID REFERENCES course_cohorts(id),
  lesson_id       UUID REFERENCES lessons(id),
  title           VARCHAR(500),
  event_type      VARCHAR(50), -- 'webinar', 'seminar', 'qa_session'
  starts_at       TIMESTAMPTZ NOT NULL,
  ends_at         TIMESTAMPTZ NOT NULL,
  location_url    VARCHAR(2000),  -- Zoom/Meet link
  recording_url   VARCHAR(2000),  -- After the event
  is_mandatory    BOOLEAN DEFAULT FALSE,
  timezone        VARCHAR(100) DEFAULT 'Europe/Moscow'
);

Calculating personal deadlines for self-paced

When a student enrolls, all relative deadlines are converted to absolute ones and stored per student:

async function assignDeadlines(studentId, courseId) {
  const enrollment = await db.enrollments.findOne({ studentId, courseId });
  const assignments = await db.assignments.findAll({ courseId });

  const deadlineRecords = assignments
    .filter(a => a.relativeDays !== null)
    .map(a => ({
      studentId,
      assignmentId: a.id,
      deadlineAt: addDays(enrollment.enrolledAt, a.relativeDays),
    }));

  await db.studentDeadlines.bulkCreate(deadlineRecords, {
    onConflict: 'ignore', // Don't overwrite on repeat calls
  });
}

Display in the interface

For students:

• Calendar with deadlines and events
• "What to submit this week" list on the dashboard
• Countdown timer for the nearest deadline
• Segmentation: overdue / due today / this week / later

For instructors:

• Cohort overview: how many students submitted on time vs. late
• Bulk deadline extension for the entire cohort

Deadline notifications

Notifications are dispatched via the task queue on a schedule:

// Cron job runs every hour
async function sendDeadlineReminders() {
  const upcoming = await db.studentDeadlines.findAll({
    deadlineAt: {
      gte: new Date(),
      lte: addHours(new Date(), 25), // Next 25 hours
    },
    submittedAt: null, // Not yet submitted
    reminderSent24h: false,
  });

  for (const deadline of upcoming) {
    const hoursLeft = (deadline.deadlineAt - new Date()) / (1000 * 60 * 60);
    if (hoursLeft <= 24) {
      await sendReminderEmail(deadline.studentId, deadline.assignmentId);
      await db.studentDeadlines.update(deadline.id, { reminderSent24h: true });
    }
  }
}

iCal export

Students want to see the course schedule in Google Calendar or Apple Calendar:

import ical from 'ical-generator';

app.get('/api/courses/:id/schedule.ics', authMiddleware, async (req, res) => {
  const events = await db.scheduleEvents.findAll({ courseId: req.params.id });
  const calendar = ical({ name: course.title });

  events.forEach(event => {
    calendar.createEvent({
      start: event.startsAt,
      end: event.endsAt,
      summary: event.title,
      description: `Type: ${event.eventType}\nLink: ${event.locationUrl}`,
      url: event.locationUrl,
    });
  });

  res.setHeader('Content-Type', 'text/calendar');
  res.send(calendar.toString());
});

What's included in our work

• Analysis of your current system and requirements gathering.
• Data schema design (PostgreSQL).
• API development on Laravel/Node.js.
• Queue integration (Bull, RabbitMQ).
• Custom UI in React/TypeScript.
• Notification setup (Email, Push, Telegram).
• iCal export for calendars.
• Documentation and team training.
• 3 months of post-launch support.

Comparing self-paced and cohort-based

Process

1. Analytics — study your LMS, load, requirements.
2. Design — database schema, notification architecture.
3. Development — write code, test with sample data.
4. Integration — connect to your LMS via API.
5. Testing — load and functional tests.
6. Deployment — to your server or cloud.
7. Training — webinar for administrators.

Timeline and cost

Basic deadline system with notifications — 4 to 5 days. Cohort-based schedule with calendar display and iCal export — additional 4–5 days. Full cycle — 10–12 days. Cost is calculated individually after scope assessment.

Common implementation pitfalls

• Time zones not accounted for — deadlines shift.
• Notification queue not scalable — reminders are skipped.
• No fault tolerance — deadlines lost on failure.
• Complex interface — students can't find deadlines.

We address these risks during the design phase.

Our expertise

We've been building LMS systems since 2019. In that time we have delivered over 20 projects for online schools and corporate universities. We use a modern stack: Laravel, PostgreSQL, Redis, Vue.js. We guarantee 3 months of free support after launch.

Have questions? Contact us and we'll evaluate your project within one day.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.