Jun 2020 – Jun 2022 · 2 yrs · Bengaluru, Karnataka, India

• Designing and Implementing change-aware Metadata pipeline for Program-Guide-Data for TiVo.
• Build and deploy Spring-boot microservice using AWS cloud.
• Enabling near real-time Program-Guide-Data update using Apache-Kafka's streaming and messaging capabilities.

Jun 2017 – Jun 2022 · 5 yrs · Bengaluru, Karnataka, India

Jun 2017 – Jun 2020 · 3 yrs · Bangalore Urban, Karnataka, India

• TiVo provides an on-screen guide of scheduled broadcast programming television programs.
• Service Engineering (Metadata) is responsible for Design, Develop and Deploy many microservices for delivering Program Guide Data to the customers.
• Builds Spring-boot microservices.
• Microservices are built following Tivo-inception framework,( an internal microservices development/deployment architecture )
• AWS as the cloud infrastructure.
• Program Guide Data pipeline is designed to be a Change-Aware System ( Kafka is used extensively for stream processing).
• System Goal : Publish PGD updates to the Client STBs <30 minute
• TiVo’s Next-Gen Platform : IPTV solutions: start-over/catch-up availability in PGD

Dec 2015 – May 2017 · 1 yr 5 mos · Bengaluru, Karnataka, India

• Built java backend systems in Everteam iBPMS and CMS solutions. Everteam (founded in 1990) is the leading provider of Enterprise Content Management (ECM) Solutions based out of France.
• Bootstrapped several microservices using the Spring-boot framework
• Technical stack :
• Netflix-Eureka for Registration and Discovery
• Netflix-Zuul as Gateway and Load-balancing
• Spring-config server for external Configuration-Management
• Spring Oauth2 using JWT for Authentication and Authorization
• Features delivered :
• 1. Developed Content Repository APIs as per CMIS 1.1 specification
• 2. Integrated the License Management Service with Salesforce APIs
• 3. Developed Records Service APIs with CMIS repository as the backend storage.
• 4. Enabled authorization for the microservices using JWT for authorization.
• On Everteam-ibpms. (Rebranding of Intalio-BPMS )
• Features developed :
• 1. Adhoc-Task requirements: Adding new SOAP webservice APIs on Apache Axis2 for Task and Process management; ad-hoc task listing and completion, listing Task-Process relationships.
• 2. High-level and low-level Design and development for Data-Driven Process Requirements:

Mar 2013 – Nov 2015 · 2 yrs 8 mos · Bengaluru Area, India

• Worked as Java backend developer in Intalio-BPMS (an enterprise Busines Process Management Solution based on SOA architecture). Mostly worked in the Process-Execution-Engine based on Apache ODE( an open-source WS-BPEL specification engine)
• Features developed:
• 1. Migration from Axis2 - 1.4 to 1.6.2 : Verifying functionalities of all web service endpoints after migration. Resolved issues during migration related to Apache Axiom incompatibility and others.
• 2. Developed REST-ful service (XML and JSON ) adaptor for all native SOAP web-services. Inherently, BPMS engine was not compatible with JSON. Used custom implementation of axis2 components Messageformatters and MessageBuilders to enable inter-conversion between xml and json.
• Fixed few issues with axis2-json utility during the development process.
• Now, BPMS process can invoke a JSON REST endpoint during its execution. Also, BPMS process can now expose itself as a JSON REST endpoint.
• 2. Dynamic Business Rules. Jboss-Drools is used as Business-Rules-Engine. Previously, Business rules were static. No modification was allowed after deployment of the process.
• Enabled dynamic update of Business Rules. Added backend functionality to support modification of the Business rules, maintain change-log of the modification and facilitate deployment of changed rules and its execution.
• 3. Added backend support for drag-and-droppable activities in the BPMN Process Designer.
• a. PDF-Activity : Services for Report Generation from Process Data in PDF format. Used Apache-Velocity as the template engine to generate the PDF report.
• b. Email-Activity : Services to send email notification as part of process execution. Used Apache-Velocity as the template engine to generate the email content and JavaMail to send emails.

Sep 2011 – Mar 2013 · 1 yr 6 mos · Bengaluru, Karnataka, India

• Worked as Java developer in ISAP Workflow Engine. ISAP Workflow Engine is used as the execution platform for developing workflow-based applications exclusively within Huawei and outside. ISAP Workflow Engine is based on XPDL2 specification.
• Features developed :
• 1. Worked in V5 to V7 engine migration project. These versions had incompatible interfaces. Developed the module to support migration using the adapter pattern.
• 2. Fixed the issues in Workflow Engine while executing 'Subprocess element' in Workflow diagrams.
• 3. Worked following agile practices including Test-Driven-Development, 100% unit-test coverage.
• 4. As part of the Organisation level security-audit of the software components, 3rd party jars used needed to be analysed for security loopholes. Used different static analysis tools like SonarQube, Findbugs, Coverity to scan the 3rd party dependencies to identify potential security threats. Issues were fixed and patched jars were added to the central repository for dependencies