GanapathyRajan Rajendran

A Node.js-based, full-featured back-end application for the Dimsum VOD service that acts as a payment proxy. This application supports the various payment methods in the range of recurring payments from credit and debit cards and single payments from online banking and e-wallets for both inbound and outbound subscriptions as well as terminations. This application can map promo code (non-paid SVOD) and pseudocode (paid SVOD) with pre-generated unique codes to serve the user accordingly. It provides a selection of product listings for Malaysia, Singapore, and Brunei as the geographical location of the users.

I was the sole developer who designed and developed this application by communicating with external business partners such as Telekom Malaysia, Celcom, uMobile, Huawei, Maxis, Digi, iPay88 and MolPay. The script was designed to be flexible and customizable to support all upcoming partners, as some partners were added later.

A Node.js-based microservice which is a combination of 4-tier security that would be used in the API request of all external parties.

Tier 1 — Signature Algorithm
All requests must be signed using the HMAC-SHA256 algorithm and a secret key. The corresponding secret key wọ̣̣uld be securely shared with the party. The signature would be passed through the header as an x-sign.

Tier 2 — Time-based Validity Verification
The default valid time range is five minutes. This prevents the API from failing due to a time difference of five minutes or more between the requesting party and the requested party. The timestamp value would be passed via the header as x-timestamp.

Tier 3 — API Invocation Permission Control
All requests to the API are checked against the third-party identifier. The partner must request the permissions of the requested party to obtain the identifier. The value would be passed as a query string parameter.

Tier 4 — Authentication Token
All requests must be made with a valid JSON web token (JWT). If the identifier is successfully authenticated, the API would be responded with a JWT with a validity period of one day. The requesting party should trigger the token API to receive the updated token when the token expires.

Node.js-based, grouped microservices serving all and soon to be other business partners by integrating Dimsum's video content into their portal and supporting inbound subscriptions instead of outbound subscriptions. Inbound subscriptions give Dimsum more flexibility compared to business partners.

These microservices cover the following functions:
• Processing video content and metadata based on tagging. This handles SVOD and priority-based rules while internal media content is not affected. For example, the entire episodes of Series A can be offered as SVOD on the Dimsum portal, while the first two episodes of Series A are offered for free on Huawei and the first three episodes are offered for free on MaxisTV 2.0.
• The API checks the eligibility of the renewal request and responds accordingly, depending on the product and business partner.
• Returns the DRM-licensed video URL after verifying the user's eligibility. The video URL is prefixed with the business partner's short name on CDN to track the video request.
• All these requests can only be made through the 4-level security.
• Script designed and developed to support all new business partners added without making any code changes.

A Python-based app running in a Linux environment to process big data ingests and massages the data from various sources like CSV, Excel, API and JSON.

The script would identify the child's recurring orders and map them with the user, order, and content details. Reconciliation of payment gateways like MOLPay and iPay88, telcos like Maxis, Digi, U Mobile, and Unifi, and third-party business partners such as MaxisTV, Huawei, and Digi EasyAdd, and promo code reports. Notifications are sent for each completed operation via AWS SNS, Mandrill to the analytics team, and Telegram to the support team.

The analyzed data is stored in AWS RDS for the analytics team's view and pushed to AWS Personalize weekly to deliver user-based personalized content.

A Python-based microservice that pushes data from AWS RDS to AWS Personalize, which is run by AWS CloudWatch.

The script was written in Python due to some issues with the AWS Personalize SDK of Node.js. AWS SDK for Node.js causes some undefined values when it calls AWS Personalize API.

This API submits the currently playing media and responds with the next playing media as a recommendation.

AWS will update its model every two hours to recommend the updated media content. For the newly registered or free users, the recommendation would be based on the popular content only.

Node.js-based back-end script that processes media content into SVOD and AVOD based on tagging rules and priority rules. All movies, documentaries, and kids' content are processed as SVOD, while short movies are processed as AVOD.

All drama, simulcast, and close release genre content would be processed as SVOD on initial release, followed by conversion to AVOD after two weeks and then to SVOD on final episode. After three months, the entire series-episode will eventually be converted to AVOD. This process differs by grouping and individual files. In grouping, the entire series-episode are converted to SVOD and then to AVOD on the same day, while in individual processing, the content is processed individually and converted to SVOD and then to AVOD after each time set.

This also differs depending on the country of origin of the content. All this is due to the agreement with the providers from each country. For boxset drama genre, it is a one-way conversion from SVOD to AVOD after three months, as boxset means that the entire episodes of the series are uploaded to the portal on the same day. The script has been designed and developed to support all new genres, countries, and rules being added without any changes to the script.

PHP-based OOP and Python-based hybrid backend script that converts the SRT to WebVTT, segments it and appends it to the M3U8 file.

PHP processes the Python script to convert and segment the subtitle file. These segmented files are appended to the manifest M3U8 file as a subtitle group to support multilingual subtitles such as English, Malay, and Simplified Chinese.

The script would notify the subtitle and/or operations team when the error occurs. No similar errors would be reported twice in the same day to give the respective parties time to re-upload the corrected version of the subtitle file. If the error occurs more than five times, the errors would be ignored forever.

Laravel-based full-stack development for the content team and back-end scripts for the Android app.

Developed a fully functional admin portal for the content team to upload and manage media content. Admin could rearrange the content listing and set the active/inactive date for the content. The preview content gives the content team a glimpse of how the content would be displayed through the Xcite app.

A back-end Bash script segments all uploaded full-feature movies into 10-second HLS DRM-encoded files, while segmenting the other video content without DRM encoding. Another back-end Bash script was developed to clear all expired content and cache on each new login to the app.

A back-end script was developed to sync all content to the 1630 Huawei MediaPad tablets and sync the data from the tablets to the local server to be retrieved monthly and visualized on Google Data Studio for the analytics team.

Native Android and iOS app, complemented by an admin web portal for soccer pitch booking and online buying and selling soccer-related merchandise and merchandising products.

Served as the sole back-end developer (Node.js), acting as the CTO for this product. I advised the client on the design of the product UI/UX, feature development and deployment. Communicated with the client and delegated the tasks to the Android and iOS developers and monitored their progress. Collaborated with the front-end developers to integrate the back-end API needed to complete the product.

Developed the full-featured web admin portal on Laravel 5.4, including user management, role management, booking slot management, fielders and team management, and data visualization.

Deployed the product back-end services and admin portal on Digital Ocean and moved the apps to Play Store and App Store.

I constantly monitored the app usage and logs for bugs and continuously made improvements and bug fixes to improve performance. A year later, I assisted the client in moving the code and product to another company.

Developed a native Android and iOS app, complemented by an admin web portal for the podcast app designed exclusively for mosques and preachers to upload their courses in audio format to share the content with a wider audience.

Served as the main back-end developer (Node.js) and acted as the CTO for this product, advising the client on the design of UI/UX, feature development, and deployment. Communicated with the client, delegated tasks to the Android and iOS developers, and monitored their progress. Collaborated with the front-end developers to integrate the back-end API.

Developed the full-featured web admin portal on Laravel 5.4 to manage the entire podcast app. Deployed the back-end services and admin portal on Digital Ocean and moved the apps to Play Store and App Store.

Continuously monitored app usage and logs for errors and made continuous improvements and bug fixes to improve performance.

Last year, in 2020, I helped the client list all the developed features to publish on LaunchGood and raise funds. This year, I assisted the client in transferring code and product to another company.

I was the back-end developer for this Laravel-based system.

The restaurant was able to manage the menu in the restaurant, which was then listed in the Android app used by the waiters. The user can manage the dish ingredients, which audits how many kilos were wasted or used to prepare the dish. The dish menu is based on best-selling items and it generates a report on the profit per dish prepared. The system includes staff management, sales reporting, cost reporting, and business intelligence.

It also has an Android app connected to POS that allows waiters to take the order per table. It even displays the wait time for each dish when the customer places their order.

The POS system includes a payment feature that allows customers to pay online. It includes an order refund and cancellation feature that has been integrated with external delivery providers. It includes staff management functions such as time-tracking and staff clock in and out. POS and Android apps have been integrated with printer hardware to print the invoice receipt at the counter and the dish order list in the kitchen after the order is completed.