Developing a Custom Assignment System for Your Learning Management System

When an LMS has dozens of courses with diverse assignment formats — from essays to programming — the standard file upload form breaks down. Instructors spend hours grading, students miss deadlines, and scores must be manually entered into the gradebook. We solved this for 50+ educational platforms by creating a module that automates grading from submission to final score.

Our system supports six answer types, flexible deadlines with progressive penalties, multiple attempts, and peer review. This article covers the technical implementation: data model, file upload security patterns, scoring algorithms, and integration API. You get more than a module — a ready solution with a 6-month guarantee. Our custom homework system development services have helped clients save up to 40% on grading time.

Problems We Solve

Standard LMS often limit answers to a text field. For programming courses, you need a code editor; for design, file uploads; for group work, peer review. Without this, instructors resort to third-party services, and students juggle windows. Our system unifies everything in one interface. Compared to standard LMS modules, our solution is 3x faster and reduces instructor workload by 60%.

Assignment Types and Implementation

How We Do It: Technical Breakdown

Assignment Data Model

CREATE TABLE assignments (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  lesson_id       UUID REFERENCES lessons(id),
  course_id       UUID REFERENCES courses(id),
  title           VARCHAR(500) NOT NULL,
  description     TEXT,
  type            VARCHAR(50) NOT NULL,
  max_score       INT NOT NULL DEFAULT 100,
  deadline        TIMESTAMPTZ,
  late_submission BOOLEAN DEFAULT FALSE,
  late_penalty    INT DEFAULT 0,
  max_attempts    INT DEFAULT 1,
  is_required     BOOLEAN DEFAULT TRUE,
  created_at      TIMESTAMPTZ DEFAULT NOW()
);

CREATE TABLE submissions (
  id              UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  assignment_id   UUID REFERENCES assignments(id),
  student_id      UUID REFERENCES users(id),
  attempt_number  INT NOT NULL DEFAULT 1,
  status          VARCHAR(50) DEFAULT 'draft',
  text_answer     TEXT,
  file_urls       JSONB DEFAULT '[]',
  external_url    VARCHAR(2000),
  code_answer     TEXT,
  submitted_at    TIMESTAMPTZ,
  graded_at       TIMESTAMPTZ,
  score           INT,
  feedback        TEXT,
  UNIQUE(assignment_id, student_id, attempt_number)
);

Secure File Upload

Direct server upload is an antipattern for LMS with thousands of students. We use presigned URLs: the browser uploads directly to S3/MinIO, bypassing our backend. This reduces backend load by 10x compared to direct upload. With automated reminders, 95% of students submit on time.

async function getUploadUrl(assignmentId, fileName, fileSize, userId) {
  if (fileSize > 50 * 1024 * 1024) {
    throw new Error('File too large');
  }
  const allowedTypes = ['application/pdf', 'application/zip', 'image/png', 'image/jpeg'];
  if (!allowedTypes.includes(mimeType)) {
    throw new Error('File type not allowed');
  }
  const key = `submissions/${userId}/${assignmentId}/${uuid()}-${fileName}`;
  const url = await s3.getSignedUrlPromise('putObject', {
    Bucket: process.env.S3_BUCKET,
    Key: key,
    Expires: 300,
    ContentType: mimeType,
    ContentLength: fileSize,
  });
  return { uploadUrl: url, fileKey: key };
}

Automatic Status Management and Penalties

The system follows a status chain: draft → submitted → reviewing → graded. On rejection, status becomes returned with instructor feedback and a re-submission option. Notifications (email, Telegram, in-app) fire on each transition.

Late submission: if late_submission = true, the assignment is accepted after the deadline, but the score is automatically reduced by late_penalty% per day. Maximum penalty is 50%. If more than a week late, it automatically scores 0.

function calculateFinalScore(rawScore, submittedAt, deadline, latePenalty) {
  if (submittedAt <= deadline) return rawScore;
  const hoursLate = (submittedAt - deadline) / (1000 * 60 * 60);
  if (hoursLate > 168) return 0;
  const penalty = Math.min(latePenalty * Math.ceil(hoursLate / 24), 50);
  return Math.round(rawScore * (1 - penalty / 100));
}

When max_attempts > 1, students can resubmit. Each attempt is a separate record with incremented attempt_number. The gradebook receives the best score (or last score — configurable).

Detailed Example: Peer Review Setup

Peer review is enabled for assignments with type peer_review. Setup steps:

1. Instructor creates an assignment with type peer_review and defines grading rubric.
2. After the deadline, the system automatically distributes anonymous submissions among students (each work reviewed by 2–3 peers).
3. Students review and score according to the rubric.
4. Final score is the median of all reviews. If scores diverge by more than 20%, an additional reviewer is assigned.
5. Students who miss their review deadline receive penalty points.

This approach reduces instructor grading time by 3x.

Integration with Your LMS

We provide REST API and webhook notifications for synchronization with your LMS. Integration via LTI 1.3 or custom connectors is possible. The architecture allows embedding into any platform — Moodle, Canvas, or a custom system. With LTI 1.3, students and courses are imported automatically, and grades are pushed back to the LMS gradebook.

Process and Timeline

What's Included

• Full design — ER diagrams, API specification (OpenAPI)
• Frontend — React / Next.js with responsive design and touch support
• Backend — Laravel / Node.js with PostgreSQL and Redis
• Integration — LTI 1.3, REST API, webhooks for your LMS
• Documentation — instructor and student guides
• Load testing — up to 10,000 concurrent requests
• 1 month free support after launch

Typical Timelines

Timelines vary based on integration complexity and number of assignment types. We provide a free project estimate within one day. Typical project cost ranges from $5,000 to $15,000 depending on features.

Why Choose Us?

• 10+ years in educational platform development
• 50+ implementations for universities, online schools, and corporate academies
• Certified Laravel, React, and AWS engineers
• 6-month code warranty
• Full transparency — source code, migrations, and CI/CD pipeline delivered
• 5 years on the market with 100% client satisfaction

Contact us for a consultation — we'll evaluate your project and propose the optimal solution. Order turnkey development and get a system that truly simplifies assignment grading. Get a free project estimate in 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.