Allianz Technology

Part of the solution architecture team works with various stakeholders to define integration designs/patterns for projects. Some of the key responsibilities are as follows
- Produces or ensures production of all Architectural deliverables under Allianz development methodology to the required level of quality
- Integration of specific aspects of enterprise and solution architecture
- Identify all areas of risk, including Architectural, Technical and Security, and manage with the cooperation of the appropriate Stakeholders, defining appropriate work to address these or escalation as necessary
- Any Divergences and Risks are both clearly communicated and agreed upon by all Stakeholders
- The adoption of different integration solutions based on the use case, with a particular focus on the Mulesoft Anypoint platform
- Architecting and delivering the MuleSoft platform by applying API-led best practices and principles
- Govern and support the integration process across all phases of delivery

Integration Architect

Integration Architecture

Asos Plc

Jitu is working as a digital technology architect with ASOS. The project was established in the year 2017 and has been going through its digital transformation journey since then

Responsibilities
Delivery (50%) executing and managing multiple projects. Day-to-day work includes releasing multiple reference documents, reusable assets (templates, API specs, schemas), custom codes covering policies, and scripts.
Working on some of the integration use cases which involved account migration between Salesforce accounts and syncs use cases between SAP & Hybris.
● Innovation (10%) developing new designs to streamline developers’ experiences at the org level. Includes development of Mule 4 starter kits (Maven archetype) projects, automation using scripts and CI/CID pipelines to deploy Mule applications on Anypoint and hybrid, and improving turnaround times using cloud services.
● Architecture (30%) developing standards, governance process, evaluating open source codes and cloud services (Azure) and outlining security patterns supporting various use cases
● Coaching (10%) onboarding new projects, enabling developers and consultants with overall infrastructure and API development lifecycle

Solution Architect

BP has opted for API first approach as their digitization tool. Worked as a core member of their central team which comprises 6 members including a Solution Architect.
https://www.mulesoft.com/case-studies/api/british-petroleum


Senior Integration Consultant

Few of the Azure log analytics database tables i.e. Perf & KubeInventory table generate CPU usage logs which are required to measure one of the key performance indexes i.e. core used across an organisation. Unfortunately due to heavy logging and costs maintaining this log for a long duration was a challenge. This project was packed with an analysis of Azure services supporting data export, data ingestion & data visualisation use cases. As a solution following pattern was used 
Data export: A scheduled logic app flow was written to query and stage results in a blob container
Data ingestion: Azure event hub was configured on the storage account to sync data in one of the Azure data explorer custom database table
Data visualisation: ADX UI dashboard was implemented on custom table data to showcase real-time compute usage data
This solution is being used to ensure customer is complaint against current compute subscription.

 Compute log retention solution using Azure data explorer

A dynamic object-store implementation using Azure Redis SDK and Spring. The project enables customers to stage data over distributed Redis cache and achieve high availability, resiliency, durability, performance & low latency. The implementation also offers an invalidation service where a key or whole cache can be invalidated which is one of the key USP of this product.

Distributed Redis cache module

A one-stop solution for API developer's to start their development, this tool was developed using the Maven archetype and ties all the engineering best practices together i.e. naming pattern, project structure, test framework, maven dependencies, logging, exception handling and a sample API contract and it's implementation. Saved 30% of the development effort and brought uniformity across all the APIs developed post it's release.

 Starterkit for developer

An alternative to enterprise batch processing product, this product was written on Java & Spring batch modules. Consumes any collection stream and process chunks in parallel backed by a monitoring dashboard. Developed as an eclipse update site project, which can be imported and used as a plugin.

Expert, freelance SOA engineers