Hybrid Assignment Evaluation in LMS: Automation and Expert Review

With the growing number of students, grading homework becomes a bottleneck in any LMS. An instructor physically cannot review 500 submissions in 24 hours, and quality suffers. We solve this with a hybrid approach: automatic grading for quizzes and code, and an optimized interface for manual grading of essays and complex assignments. Our experience shows that up to 70% of typical assignments can be auto-graded, reducing instructor time by 3–5x. For example, in a university project, we implemented automatic code grading in Python — the instructor now grades 200 submissions in 1 hour instead of 5. Budget savings on grading reach 40% compared to manual labor, translating to an average of $8,000 saved per semester for mid-sized institutions. Development cost starts at $5,000, with typical ROI achieved in 2–4 months. We ensure scalability up to 1000 concurrent checks and provide feedback on every submission. Average development time is 2–3 weeks. In this article, we'll share how we design a grading system, what components are included, and how you can order such a turnkey development.

What Problems Does Hybrid Grading Solve?

Instructor overload. Manual grading of 50+ submissions per day leads to burnout and errors. Automation removes the routine: the instructor only reviews complex assignments, while quizzes and code are graded automatically.

Diverse assignments. A single course may include quizzes, essays, code, and files. A universal system must support all formats. We integrate grading rubrics, inline PDF annotations, and a Docker sandbox for code.

Plagiarism. Text borrowing and code copying are common. Integration with Unicheck and MOSS (or a custom engine on TF-IDF) flags suspicious submissions before the instructor even sees them.

How We Implement Manual Grading

The grading interface must minimize context switching. On one screen: the student's work on the left, evaluation form on the right. Key components we implement:

• List of ungraded submissions with filters by assignment, group, date
• View student answer (text, inline file, or link)
• Grading rubric with checkboxes (if criteria are defined)
• Score field and text comment with Markdown support
• Buttons: "Accept", "Return for revision", "Next submission"
• Inline annotations on PDF (if the work is in PDF format)

For quiz-type assignments with correct answers, we implement batch grading: the instructor sees a table of all submissions with answers and can assign scores in bulk.

How Automatic Grading Works

Quiz / closed-ended tests:

async function autoGradeQuizSubmission(submissionId) {
  const submission = await db.submissions.findOne(submissionId, {
    include: ['assignment.questions']
  });

  let totalPoints = 0;
  let earnedPoints = 0;
  const results = [];

  for (const question of submission.assignment.questions) {
    totalPoints += question.points;
    const studentAnswer = submission.answers[question.id];
    const isCorrect = checkAnswer(question, studentAnswer);

    if (isCorrect) earnedPoints += question.points;

    results.push({
      questionId: question.id,
      correct: isCorrect,
      studentAnswer,
      correctAnswer: question.correctAnswer,
    });
  }

  const score = Math.round((earnedPoints / totalPoints) * submission.assignment.maxScore);

  await db.submissions.update(submissionId, {
    status: 'graded',
    score,
    autoGradeResults: results,
    gradedAt: new Date(),
  });

  await notifyStudent(submission.studentId, submissionId, score);
}

Code grading via tests: For programming courses, we run student code in isolated Docker containers against a test suite. This guarantees security and reproducibility.

async function runCodeTests(submissionId, code, language, testCases) {
  const result = await dockerRunner.run({
    image: `lms-runner-${language}:latest`,  // python:3.11, node:20, etc.
    code,
    tests: testCases,
    timeout: 10000,  // 10 seconds
    memoryLimit: '256m',
    networkDisabled: true,  // No network in sandbox
  });

  return {
    passed: result.passedTests,
    total: testCases.length,
    output: result.stdout,
    errors: result.stderr,
    executionTime: result.durationMs,
  };
}

FROM python:3.11-slim
RUN pip install pytest
COPY tests/ /tests/
ENTRYPOINT ["pytest", "/tests/"]

Plagiarism detection: For text — integration with Unicheck or MOSS (for code). We can also implement a custom system using TF-IDF vectorization and cosine similarity if full data control is required. Plagiarism detection can save up to 40% of the grading budget.

Why Automated Code Grading Is Faster Than Manual

Automated code grading completes in seconds, while an instructor spends 5–10 minutes per submission. Compare: 200 students × 7 minutes = 23 hours of manual work versus 40 minutes of automated. Time savings of 30x. Grading quality does not suffer: tests cover all edge cases, and the sandbox ensures security.

What Is Included in the Work?

• Analysis and design. We define assignment types, rubric requirements, integrations with Unicheck/MOSS. Create use cases and interface prototype.
• Manual grading module. Interface with filters, rubrics, annotations, and batch grading.
• Automatic test and code grading. Implement quiz engine and Docker runner with configurable tests.
• Anti-plagiarism. Integration with Unicheck/MOSS or custom TF-IDF system.
• Notifications and workflow. Configure events, email/in-app notifications, status chain submitted→reviewing→graded→returned.
• Documentation and training. Technical API docs, user guide for instructors, and a live training session.
• Post-deployment support. 2-week warranty period, then optional maintenance contract.

Implementation Process

1. Analysis. Determine assignment types, rubric requirements, integrations. Compose use cases.
2. Design. Design API for grading, instructor interface, status workflow. Choose stack: React + TypeScript frontend, Laravel or Node.js backend, Docker for sandbox.
3. Development. Implement manual and automatic modules, connect Docker runner, configure notifications.
4. Testing. Load testing up to 1000 concurrent checks. Unit test coverage for key scenarios.
5. Deployment. Deploy on server (Docker-compose or Kubernetes). Train instructors.

Status Workflow

submitted
  ↓ (auto-grade or manual)
reviewing
  ↓ instructor opens work
graded → notify student
returned → student receives notification, can revise
  ↓ resubmitted
resubmitted → back to reviewing

Notifications

Timeline Estimates

We have over 8 years on the market and have delivered over 100 projects for LMS. The cost of developing a hybrid grading system varies based on complexity, but on average it pays for itself within 2–4 months. Contact us for a preliminary assessment of your project — we'll prepare a tailored proposal. Request a consultation now — we'll evaluate your project for free.

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.