Webinar System Development for LMS (Video Conferencing Integration)

Once we integrated webinars into an LMS with 2000 students: the teacher manually created meetings, forgot to enable recording, and had to cross-check attendance via screenshots. After automation via API, administrative costs dropped by 8 hours per week. This approach not only saves time but also eliminates human errors — students receive links on time, recordings are available right after the webinar, and the attendance log is filled automatically.

How to Choose a Video Platform for LMS?

BigBlueButton — recommended for educational LMS: built-in whiteboard, polls, breakout rooms, participant-split recording. Self-hosted. Zoom — if clients already use it and don't want to change habits. Daily.co — if you need to embed video directly into the LMS interface without navigating to an external site.

How to Automate Webinar Creation?

Integration with Zoom API is one of the most straightforward paths. Below is an example JavaScript class that creates a meeting with auto-recording and waiting room settings.

class ZoomIntegration {
  constructor(accountId, clientId, clientSecret) {
    this.tokenUrl = 'https://zoom.us/oauth/token';
    this.apiUrl = 'https://api.zoom.us/v2';
    this.credentials = { accountId, clientId, clientSecret };
  }

  async getAccessToken() {
    const response = await fetch(this.tokenUrl, {
      method: 'POST',
      headers: {
        'Authorization': `Basic ${Buffer.from(`${this.credentials.clientId}:${this.credentials.clientSecret}`).toString('base64')}`,
        'Content-Type': 'application/x-www-form-urlencoded',
      },
      body: `grant_type=account_credentials&account_id=${this.credentials.accountId}`,
    });
    const data = await response.json();
    return data.access_token;
  }

  async createMeeting({ topic, startTime, durationMin, agenda, hostEmail }) {
    const token = await this.getAccessToken();
    const response = await fetch(`${this.apiUrl}/users/${hostEmail}/meetings`, {
      method: 'POST',
      headers: {
        'Authorization': `Bearer ${token}`,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        topic,
        type: 2,
        start_time: startTime.toISOString(),
        duration: durationMin,
        agenda,
        settings: {
          host_video: true,
          participant_video: false,
          waiting_room: true,
          auto_recording: 'cloud',
          mute_upon_entry: true,
          approval_type: 0,
        },
      }),
    });
    return response.json();
  }
}

For BigBlueButton the approach is different — it uses checksum-signed requests. Example in PHP:

class BigBlueButtonService {
    private string $url;
    private string $secret;

    public function createMeeting(string $meetingId, string $name, array $options = []): array {
        $params = array_merge([
            'meetingID' => $meetingId,
            'name' => $name,
            'record' => 'true',
            'autoStartRecording' => 'false',
            'allowStartStopRecording' => 'true',
            'webcamsOnlyForModerator' => 'false',
            'lockSettingsDisableMic' => 'false',
        ], $options);

        $queryString = http_build_query($params);
        $checksum = sha1('create' . $queryString . $this->secret);
        $params['checksum'] = $checksum;

        $response = Http::get("{$this->url}/api/create", $params);
        return $response->json();
    }

    public function getJoinUrl(string $meetingId, string $fullName, string $role, string $userId): string {
        $password = $role === 'moderator' ? $this->moderatorPw : $this->attendeePw;
        $params = "meetingID={$meetingId}&fullName=" . urlencode($fullName) .
                  "&password={$password}&userID={$userId}";
        $checksum = sha1('join' . $params . $this->secret);
        return "{$this->url}/api/join?{$params}&checksum={$checksum}";
    }
}

What Does Attendance Tracking via Webhooks Provide?

Automatic tracking via webhooks solves the problem of attendance fraud. Zoom Webhooks send meeting.participant_joined and meeting.participant_left events. BigBlueButton provides detailed logs through Recording API. We save each student's entry and exit time, compute presence duration, and generate a report.

app.post('/webhooks/zoom', async (req, res) => {
  const { event, payload } = req.body;

  if (event === 'meeting.participant_joined') {
    await db.webinarAttendance.upsert({
      webinarId: payload.object.id,
      userId: await findUserByEmail(payload.object.participant.email),
      joinedAt: new Date(payload.object.participant.join_time),
    });
  }

  if (event === 'meeting.participant_left') {
    await db.webinarAttendance.update({
      webinarId: payload.object.id,
      userId: await findUserByEmail(payload.object.participant.email),
    }, {
      leftAt: new Date(payload.object.participant.leave_time),
      durationMin: payload.object.participant.duration,
    });
  }

  res.status(200).json({ status: 'ok' });
});

Webinar Recordings

After the webinar ends, Zoom/BBB generates a recording. Process:

1. Webhook recording.completed → receive download link
2. Download and upload to S3 (Zoom stores recordings for a limited time)
3. Create a video lesson in LMS with the recording link
4. Notify students who missed the webinar

async function processWebinarRecording(meetingId, downloadUrl, token) {
  const s3Key = `recordings/${meetingId}.mp4`;
  const response = await fetch(downloadUrl, {
    headers: { Authorization: `Bearer ${token}` }
  });
  await s3.upload({ Bucket: process.env.S3_BUCKET, Key: s3Key, Body: response.body }).promise();
  const videoUrl = `https://${process.env.CDN_DOMAIN}/${s3Key}`;
  await db.webinars.update({ meetingId }, { recordingUrl: videoUrl });
  await notifyAbsentStudents(meetingId, videoUrl);
}

Embedded Video Call via Daily.co

If you need to embed video directly into LMS without navigating to an external page:

import DailyIframe from '@daily-co/daily-js';

function WebinarRoom({ roomUrl, token }) {
  const callFrame = useRef(null);

  useEffect(() => {
    callFrame.current = DailyIframe.createFrame({
      url: roomUrl,
      token,
      iframeStyle: { width: '100%', height: '600px' },
    });

    callFrame.current.on('participant-counts-updated', ({ present }) => {
      trackAttendance(present);
    });

    callFrame.current.join();
    return () => callFrame.current.destroy();
  }, [roomUrl]);

  return <div id="daily-container" />;
}

Use Case Scenarios: Platform Comparison

Common Integration Mistakes

What's Included in the Work

• API integration of the chosen platform (Zoom/BBB/Jitsi).
• Automatic webinar creation based on schedule.
• Sending links to students (email/notifications).
• Webinar recording and upload to S3/CDN.
• Attendance tracking with reports.
• API documentation and admin instructions.
• 1 month technical support.

Work Process

1. Requirements analysis: select platform, configure API, agree on data flow scheme.
2. Design: design webhook handlers, recording and attendance storage schemas.
3. Implementation: integrate via API, code, write tests.
4. Testing: verify meeting creation, webhooks, recording, attendance.
5. Deploy and train: deploy on server, provide admin instructions.

Approximate Timelines

Zoom API integration: create meetings, send links to students, basic attendance — 4–5 days. Webinar recording with upload to S3 and notifications — 2–3 days. Self-hosted BigBlueButton with full integration and embedding into LMS — 7–10 days. Daily.co embedded video — 3–4 days.

Experience and Guarantees

We have completed over 30 integrations with Zoom, BigBlueButton, and Jitsi for LMS on Laravel, Node.js, and Python. Our engineers are certified in Zoom API. We guarantee compatibility with any modern LMS and provide 1 month support after deployment.

For an accurate timeline and cost estimate, contact us — we will select the optimal platform for your tasks.

See official documentation: Zoom REST API, BigBlueButton API.

Development of Real-Time Systems: WebRTC, SSE, WebSocket

We know how painful it is when polling kills the server. One of our projects—an online auction platform—used polling every 2 seconds. Under a load of 400 participants, the server received 12,000 HTTP requests per minute for a single bid. 90% of responses were empty. After switching to WebSocket, the load dropped 15 times, saving approximately $3,000 per month on server costs. Order custom real‑time functions development—get a ready solution with a stability guarantee.

Implementing real‑time in production is not just a library. We design the architecture for load, scenarios, and budget. Below is a breakdown of key solutions with examples.

Choosing the Right Real-Time Transport for Your Project

Three Real-Time Transports: When to Choose Which

Server‑Sent Events work over regular HTTP/1.1 or HTTP/2. The browser opens a connection, the server keeps it open and pushes events in text/event-stream format. Automatic reconnection is built-in—no need for reconnect logic. Limitation: server → client only. Ideal for notifications, progress of long tasks, live feeds.

WebSocket is a full‑duplex channel after an HTTP Upgrade handshake. Browser and server exchange frames in both directions. Suitable for chats, collaborative editing, games, trading terminals. Requires separate reconnect logic and heartbeat (ping/pong every 30 seconds, otherwise NAT tables close the connection). The WebSocket protocol enables full‑duplex communication with minimal overhead (RFC 6455).

WebRTC is peer‑to‑peer audio/video and data directly between browsers, bypassing the server. A server is needed only for signaling (STUN/TURN for NAT traversal). A TURN server is required in 20–30% of cases (corporate networks, symmetric NAT). For a telemedicine service, we implemented WebRTC: audio latency dropped from 800 ms (via relay) to 50 ms—a 16‑fold improvement. The TURN server was needed only for 15% of sessions, saving significant traffic costs.

How to Properly Choose a Transport: Step-by-Step Guide

1. Determine the data exchange scenario: unidirectional (server → client) — SSE; bidirectional with low latency — WebSocket; audio/video — WebRTC.
2. Evaluate latency requirements. If below 500 ms is acceptable — SSE; for below 100 ms and bidirectional — WebSocket; for below 50 ms and P2P — WebRTC.
3. Check the infrastructure budget. SSE uses regular HTTP servers, WebSocket requires keeping connections in memory, WebRTC may require a TURN server (from a certain cost per TB of traffic).
4. Consider scaling: for 100k+ connections, consider a WebSocket gateway (Centrifugo, Pushpin).

What Is CRDT and How Is It Better Than Operational Transformation?

Collaborative editing is not just "whoever writes last wins". Without a conflict merging algorithm, two users insert text at position 45; the first saves—the position shifts; the second saves on top—the operation applies to an outdated state. Text gets duplicated or lost.

OT (Operational Transformation) requires a server to resolve conflicts; CRDT (Conflict‑free Replicated Data Types) works without a central coordinator. Yjs is the most mature CRDT library for the browser. It integrates with ProseMirror, TipTap, CodeMirror, Monaco Editor. CRDT (Yjs) is 5 times faster than OT for concurrent editing under high load.

Library comparison for collaborative editing

Issue: the Yjs document size grows due to operation history. Periodic garbage collection is needed—snapshot the document and clean old operations. Without it, a document worked on for a year may weigh 50 MB.

const ws = new WebSocket('wss://example.com');
let pingInterval;

ws.on('open', () => {
  pingInterval = setInterval(() => {
    ws.ping();
    setTimeout(() => {
      if (ws.readyState === WebSocket.OPEN) ws.terminate();
    }, 5000);
  }, 25000);
});

ws.on('close', () => clearInterval(pingInterval));

Common Mistakes in Real-Time Implementation and How to Avoid Them

Typical Mistakes in Real‑Time Implementation

Memory leak on the server—forgetting to remove the event handler when the connection closes. On Node.js, heap grows ~1 MB/hour. EventEmitter warns about 10+ listeners, but it's not always noticed.

Thundering herd on reconnect. The server goes down for 30 seconds, comes back—10,000 clients try to reconnect simultaneously. Exponential backoff with jitter is mandatory: delay = Math.min(baseDelay * 2^attempt + random(0, 1000), maxDelay).

Lack of connection lost indication. WebSocket doesn't always notify about disconnection (e.g., phone enters a tunnel). Heartbeat solves the problem.

Work Process

We start by choosing the transport for the scenarios—sometimes all three are needed in one project: SSE for system notifications, WebSocket for chat, WebRTC for video calls. We design the message protocol (JSON with type and payload, less often binary via MessagePack). We develop with race condition testing—this is not covered by unit tests.

Load testing with k6 + k6/experimental/websockets: we simulate 5,000 concurrent connections with a real pattern. Our engineers are certified in WebSocket and WebRTC, guaranteeing 99.9% stability.

What's Included in the Delivery

• Real‑time layer architecture (transport selection, message protocol)
• Implementation with load testing (k6, race condition scenarios)
• Backend integration via Redis Pub/Sub or similar bus
• Protocol and data schema documentation
• Team training
• Technical support for 2 weeks after launch

Why Centrifugo May Be More Cost-Effective Than Socket.io?

Socket.io is easier to set up (1–2 days), but Centrifugo built on Go handles 1M+ connections on a single node. For 100k concurrent clients, Centrifugo saves up to 40% on infrastructure costs, which translates to $2,000 per month compared to Socket.io. Get a consultation—we'll help you choose the stack for your load.

Timeline

• Basic WebSocket chat or notifications on top of existing API: 1–3 weeks.
• Collaborative editor with Yjs and persistence: 4–8 weeks.
• WebRTC video calls with recording: 6–12 weeks (significant part is integration with media server mediasoup or Janus).

Contact us to evaluate your project. Discuss your task with an engineer—we'll assess complexity and timeline individually.