Jan 2021 – Nov 2021 · 10 mos

• API Mesh is a containerised cross zone platform which uses a distributed gateway architecture to achieve cross zone and enable security zone traversal. The application is deployed as a mesh which enables the provider and consumer to interact with one another regardless of their location whether in ANZ network or outside of it. The infrastructure provisioning is fully automated using codefresh pipeline and leveraging terraform as IaC(Infra as Code). Helm 3 is used as a templating engine which generates the Kubernetes manifest for different environments based on value files passed for each environment. The application code base is same for all the platforms. The platform has been deployed in all the platforms like AWS, GCP and Openshift 4.
• https://www.itnews.com.au/news/anz-banking-group-shows-off-its-api-mesh-572091
• Environment: Kong Gateway, Kubernetes, Helm, NodeJS, CodeFresh, Bamboo, Terraform, Postgres, AWS (EKS, ECR, RDS, EC2, Elasticache, Route53, OIDC, IAM, S3), GCP (GKE, CloudSql, CloudSql Proxy, MemoryStore), Openshift, New Relic, Prometheus, Istio, Splunk.

Mar 2019 – Dec 2020 · 1 yr 9 mos

• I2 initiative’s aim to industrialise IBM i2 network analysis tool, so that technology can service network analysis needs across FIO, FCI. The data is ingested from the EBD platform which includes data from different banking systems into IBM DB2 database and Apache Solr in indexes for faster retrieval of data. The data is firstly ingested in staging database where data is massaged and processed by applying with some business logic and then the ingestion jobs are run by python scripts which would ingest data in Solr servers and IBM Db2 database, so that the data can be analyzed by the investigators. Data from external API’s is also ingested using Rest Webservices data connectors using NodeJS to parse the data and ingest into the database.
• Environment: Java, NodeJS, Rest WebServices, Apache Solr, WebSphere Liberty Server, Control M, IBM I2, IBM DB2, Bamboo, Python

Aug 2018 – Mar 2019 · 7 mos · Melbourne, Australia

• Lead the solution design for one of the Big Data and Microservices initiative for one of the large banks related to Open Banking which was creating a POC for the solution. The project involved the data ingestion in a Data Lake from the RDBMS tables using Sqoop Jobs and the data was processed using the Apache Spark (Batch Processing) and saved in the form of Data Frames in CSV files using Apache Spark. The data from the CSV files was exposed to get data to different Rest Endpoints by microservices developed with Spring Boot.
• Environment: Java, Spring Boot, Rest Web Services, Apache Spark, Sqoop, HBase, HDFS, HBase Rest Server.

Apr 2017 – Aug 2018 · 1 yr 4 mos · Melbourne, Australia

• Online Charging System
• The OCS Platform, for Telstra which includes creating API’s for charging the customers across Australia for the different services that are purchased. Major contributions including developing or onboarding the same platform for client in Middle Eastern telecom provider which had the Jenkins Integration for CI/CD.
• Environment: Java, Spring Core, Apache Kafka, AngularJS, Spring Boot, Soap and Rest Web Services, JavaScript, Hibernate, Matrixx API, Puppet, Jenkins, NPM.
• Messaging Mediation Platform(MMP)
• MMP is a message billing system developed for Telstra. The system parses the data and run some business rules and interacts with different system based on the record type. It basically receives data from different upstream system which pass on the data from the upstream system to parse the message and apply some business rules and report the billing for those records and convert the data to downstream understandable formats. The system interacts with millions of transactions every minute and sends that to downstream system after applying business logic.
• Environment: Java 8, JavaScript, JSON, Rest Web Services, HTML, J2EE, Spring Boot , HTML, JSP, Oracle 10g, SQL, TestNG, JUnit.
• Chameleon(Apple Watch 3 Integration)
• Chameleon is a propertiery platform developed for Telstra, which is Web based platform developed to integrate the Apple IWatch 3 with the iPhone. A Web User Interface is created that receives data from the Apple and then parses that data and uses business logic to pair and unpair and provide other features using the Web UI and send the data to provision the Watch the other downstream Systems of core Telecom. It uses latest web technologies to connect to multiple telecom systems for billing and other operational systems.
• Environment: Java, JavaScript, JSON, Rest Web Services, HTML, J2EE, Spring Boot, HTML, JSP, Oracle 10g, SQL, TestNG, JUnit.

Mar 2016 – Feb 2017 · 11 mos

• WebInsure Exchange Manager 2.0 is an extension of the WEM product that has built in feature to toggle certain set of (HIPAA) business rules that are used in the validating of EDI files. WEM acts as an integrator between the state exchanges and the issuer to provide seamless integration of the Payer with multiple state exchanges, which is basically derived from the Obama's Healthcare reform.
• Environment: Java, JavaScript, Apache ActiveMQ, Apache Camel, JBoss Fuse, JSON, Rest Web Services, J2EE, Tibco Validator, Spring, Hibernate ,Web Service, Adeptia B2B Suite, Jasper Reports, SSO, iReports, Oracle 10g, PL/SQL, TestNG, MongoDB.

Dec 2013 – Mar 2016 · 2 yrs 3 mos

• WebInsure Integration Gateway
• WebInsure Integration Gateway is an extended integration gateway that is designed to integrate multiple state exchanges with Payer system’s. The routing components to complete the JBoss Fuse ESB integration developed with Apache Camel, apart from that messages between different components were sent using Active MQ Queue’s and Topics. The individual components are deployed in the JBoss Fuse environment as OSGI Bundles.
• Environment: Java, J2EE, JBoss Fuse, Apache Active MQ, Apache Camel, MongoDB, Postgres, Tibco Validator, Spring, Hibernate , Web Service, , EDI 834/820, Jasper Reports, SSO, Oracle 10g, PL/SQL.
• WEBINSURE EXCHANGE MANAGER
• WebInsure Exchange Manager allows health payers to integrate with multiple state exchanges, process state residents’ applications, track payments & subsidies and update plan rates online at state marketplaces. WEM acts as an integrator between the state exchanges and the issuer to provide seamless integration of the Payer with multiple state exchanges, which is basically derived from the Obama's Healthcare reform.
• Environment: Java, J2EE, Spring, Hibernate ,Web Service, Adeptia B2B Suite, EDI 834/820, Jasper Reports, SSO, iReports, Oracle 10g, PL/SQL

Dec 2012 – Dec 2013 · 1 yr

Sep 2010 – Dec 2012 · 2 yrs 3 mos · Noida Area, India

• Eflow is an Order Provisioning and Orchestration system as well as a workflow driven
• system. It performs all the steps related to provision a Telecom sales order till the time the service can be started and billing can be triggered. During the provisioning life cycle of the order, EFLOW communicates with various other systems in other core areas of telecomm OSS like Ordering systems and Inventory systems through Webservices in a SOA (Service Oriented Architecture) architecture and other middleware communication technologies like JMS, and TIBCO RV messaging. The workflow engine is based upon the CenturyLink’s proprietary framework MDW (Model Driven Workflow) which runs provisioning processes called JPDs (Java Process Definitions) to complete provisioning of sales orders.
• Environment: Java, JSP, Struts ,WebLogic JMS, EJB,TIBCO RV Messaging, Apache Axis , Apache CXF Webservices using Spring Beans, SOAP, CenturyLink’s proprietary Model Driven Workflow (MDW), Weblogic Integrator 10.3 , Weblogic Server 10.3, Oracle 10g, PL/SQL, Java Process Definitions(JPDs), JBoss Drools Rule Engine.