ContentCentral Learning Content Lifecycle Management

Overview

Content Central is a modern take on learning content management, a headless Content Lifecycle Management system in which the learner-facing learning content delivery and presentation layer (the ‘head’) is decoupled from the process of creating, storing and managing the learning content (the ‘body’).

The focus of LMS is to do a great job of assigning, tracking and delivering the published learning content to learners with the best possible experience. But an LMS does not manage the phases/stages of the learning content lifecycle and the ongoing updates and changes. This is where ContentCentral—a ‘headless’ multi-tenant Content Lifecycle Management system— comes in and delivers!

This decoupled architecture lets you choose the content delivery and presentation layer (the LMS) that best suits an organization, while ContentCentral takes care of exclusively managing your content over its lifecycle. And it does that by seamlessly pairing up and complementing LMS. Any LMS.

It lets an organization take control of its learning content and assets. There is no need to dig through email attachments and folders and track people down for missing documents and lost files. Manage all of your learning content and assets from a single location, organized in the cloud. It is a cloud-based central repository of learning content.
Project Info

Category

Cloud Backend, Web Apps

Client

Content Central

Stack

  • AWS
  • Microservices
  • Multi-tenant
  • React
  • Java

Platform Features

Microservices based back end​
Role Based Access Control​
Back End for Front End (BFF)​
Multi-tenancy​
Asynchronous communication between microservices using AWS SNS/SQS​
Autoscaling using Cluster and Pod Autoscalers​
Spring Security based Authentication using KeyCloak​

Product Features

Maintain Learning programs and their components​
Drill Down Dashboard displaying system data statistics using d3​
Temporal view of Trends and Insights​

Architecture

A Microservices based architecture was defined to allow different business functions of Content Central to evolve independently. It would also help to keep Content Central extensible and maintainable for the long run. This architecture would meet the following business requirements

  • Horizontally scale for critical and highly consumed business functions.
  • High availability of critical business functions.
  • Enabler for faster go-to-market for new capabilities.
  • Low maintenance overhead and ease of extensibility.

ContentCentral is broken down into multiple microservices based on Domain Driven Design. Some of the key services are –

01. Learning Object services (eLearning, Material, Video and ILT Services)
  • Each of these microservices handles a type of Learning object across its life cycle.
  • Responsible to ensure validity of Learning object it maintains.
02. Content Management and Content Processor Service:
  • Business service responsible to store content associated with Learning objects.
  • Validate uploaded content against different business rules based on type of content, validate content uploaded is compliant to eLearning standards like SCORM.
03. Platform Manager service
  • Service supporting all administration functionality.
  • Global configurations.
04. Backend for Front End
  • It is the bridge between the front end and the resources supported by domain specific microservices.
  • It front ends all calls to backend microservices and orchestrates across them to satisfy front end request.
05. ReactJS based Front
  • A user interface service creating a SPA built in ReactJS.

Microservices Architecture Diagram

Repository for storage of content

The most important capability that Content Central has to provide is a repository to store content (published or otherwise) associated with the learning object. The repository is expected to retain content for 10’s of thousands of LOs (Learning Objects) and multiple versions of each LO. A single version of LO has to maintain multiple files of different sizes and types. Over the period of time, more LO’s can be added to Content Central increasing storage requirements of the content repository. 


Considering such requirements, AWS S3 is chosen as the storage backend for Content Central content repository. S3 provides virtually unlimited versioned, HA and secure storage. With its support for multiple storage classes, S3 also provides the ability to optimize the overall storage consumption cost based on content access patterns. Hence S3 was chosen over building an on-premise content repository to avoid having to build all the required capabilities from scratch.

Product Deployment Architecture

Frontend web application is deployed as an independent service along with all the backend microservices in an AWS managed kubernetes environment called EKS.

Continuous Integration, Testing and Development Flow

Leading open source tools like Jenkins, Terraform, Ansible, Helm and Docker were used to achieve commit based continuous delivery straight from Bitbucket version control system to the cloud platform deployments in high availability mode with auto scale based on load. Sonar Quality Gate was used for enforcing code quality checks. The pipeline ran the automated tests written using REST-Assured and TestNG frameworks.

Agile based delivery

The Product Team, in collaboration and agreement with business stakeholders, planned for a 6 month MVP release using Agile Methodology. Each sprint was of 2 weeks duration. On completion of a sprint, the client validated the UX and business use cases implemented in the product.

Summary

Numino’s solution provided the client with a cutting-edge investment optimization tool in the form of a secure, cloud-based reactive Single Page Application (SPA) with appropriate architecture which can automatically scale, is highly available and has a completely automated one click delivery pipeline, finally meeting the requirements of the end customers to

Stay abreast with new/updated policies, standards and laws

Stay abreast with evolving learning paradigms and modern learner preferences

Make learning investments more data driven

Drive continuous improvement by bridging content gaps emerging from business evolution and changes in strategy and markets.

Content Central - Features

With Content Central, you can take charge of your organization’s learning content through efficient, automated and centralized operations through its entire life cycle.
Find The Right Content
With extensive metadata (most automatically extracted), intelligent keywords and a deep search function, locate the right content, right owner, right version, right files and right supplier with only a click.
Access Every Important File
With a cloud-based central library that smartly stores every file that matters, free up your time through easy, specific searches and focus on what matters.
Maintain Ownership And Accountability
With speedy development and update functions, define and maintain content ownership, avoid ‘orphan’ content and achieve enhanced governance and accountability.
Manage changing content and versions
With speedy development and update functions, define and maintain content ownership, avoid ‘orphan’ content and achieve enhanced governance and accountability. Discover outdated, ineffective and ‘broken’ content for review and update and make the right spends for targeted improvement. and everything in its place.

Product Screenshots

Read More

Pixm Anti Phishing v2.0
Cloud Backend,Web Apps,
Pixm Anti Phishing v2.0

Pixm is an AI tool that stops phishing attacks instantly when clicked, using serverless technology for scalable, cloud-based threat detection and comprehensive enterprise security management.
StrategicIT ePMOLite Project Management
Cloud Backend,Web Apps,
StrategicIT ePMOLite Project Management

ePMOLite transforms IT PMO for small to mid-sized organizations with a cloud-based, serverless solution that tracks progress and financials, facilitating informed decision-making.
PromptMule Prompt Cache LLMs
AI,Cloud Backend,
PromptMule Prompt Cache LLMs

PromptMule, a managed caching service, leverages semantic caching and vector embeddings to deliver lightning-fast responses, reducing costs by 70% while improving application responsiveness by 5x.