The project was to create an oAuth2 server which will generate a jwt token with embedded user details and claims and signed by a private key. Its corresponding public key will be shared with the clients and thus the client will be redirected to their registered url with jwt token and refresh token passed in the query params.If token expires, the client will regenerate it using the refresh token and if the refresh token and jwt token both are expired, user will be redirected back to the login screen with redirecturl parameter passed to it

Had to develop a robust API which would be of bursty nature. Hence had to be highly load tolerant. So we decided to go ahead with golang. Had to design they entire API with rabbit, mysql, redis

Technologies used v golang, redis, rabbitmq, mysql

Part of Teno, a product geared towards school and children where we crowd source questions for various standards and pay the authors accordingly

A consumer to interest events and populate in mysql
Expose apis to display weekwise stats
A scheduler to generate invoice of payment

Technologies used: rabbitmq, jpa, mysql, mongo, redis

To process all events like clicks, opens, sent, etc realtime in a multithreaded environment and create the corresponding summary in mongo.This would then be consumed by APIs to be displayed on dashboard.Dashboards included data like Email analytics, Web Analytics, App analytics.

Had to understand existing marketing automation backend architecture and implement new features in the component while maintaining it and keeping it bugfree. It basically is an event processing system and an automation can be created via html.It parses the HTML into corresponding business logic(into clojure).This was built into a jar and was deployed to our storm topology. Thus business logic can be created on UI via building blocks like a flow chart and this will be converted into clojure and eventually a jar. Our storm cluster had 10 topologies which were spread across 2 servers. Kafka was used as a messaging queue and storm spouts and bolts were used to consume and process the data via apis

To process all events like clicks, opens, sent, etc realtime in a multithreaded environment and create the corresponding summary in mongo. This would then be consumed by APIs to be displayed on dashboard.

Had to develop a c milter to filter emails based on any role specified by the client in the UI. These rules could be like delete mails with subject containing abc etc. Had to write a milter in c for this using send mail library and integrate it into postfix for real-time email filtering.

Had to develop a UI to add users with their details and create mailboxes on Gapps servers. This was done through google api libraries and api authentication was done through saml. This was done in order to create users on our server as well as google via a single UI.

Had to install our mailserver (Einteract) along with ECM (Anti Spam) and EMA (Mail Archival). Had to customize all three products according to client requirements and clear the ATP committee headed by Haresh Bhatt (ITSO). Customizations included the option to add additional restrictions to emails being sent/received, additional quota restrictions on quota etc and some UI related changes. Had to also design a C milter on the go to prevent Open relay and some UI Vulnerability Fixes.