Ashish Mishra

Ashish Mishra Senior Architect, Coforge, Bangalore Profile Summary Ashish Mishra has 17 years’ experience in Middleware Technologies (Java/JEE),Enterprise Integration, DevOps and Cloud. He has interacted with Enterprise Architects, Business Architects, Product Owners and other key stakeholders to finalize requirements and analyse technology and product landscape. He has demonstrated good Technical Leadership, Product fitment assessment capabilities and Solutions requirement fit approach. He has demonstrated good technical leadership and participated in all phases of software development lifecycle – comprising of Design, Development, Testing and Operations and Maintenance, He is well versed in various software architectural styles such as N-Tier, SOA and Microservices. SKILLS Technology Java, JEE,Spring, SpringBoot, Hibernate, Microservices Modelling/ Requirement Management UML, JIRA BPM Pega 8, BPMN DevOps Tools AWS, GIT, Subversion (SVN), AWS Cloud, Maven 3.x/4.x, Jenkins 2.x, Nexus, Terraform, Ansible, Jenkins, Docker, Nagios, Kubernetes Testing Selenium, SOAPUI, JMeter Domain Government Services, Insurance, Travel & Transport CERTIFICATIONS March 2011 s Oracle Certified Master Enterprise Architect – Part 1 Project Experience Name of the Project:Case Management Migration Project, HMRC, UK Duration March 2020 to March 2021 Role Middleware and DevOps Architect Project Type Migration, Integration& Upgrade Technology Pega 8, Oracle 19c, AWS Cloud, Java, JEE, Microservices, Ansible, Terraform, EKS, Docker Project Overview Overview My Responsibilities HMRC is migrating its Case Management Systems to AWS cloud environment. In addition, these set of applications will be re-architected/ re-platformed to the latest versions of supported underlying software, The existing Case Management Systems are hosted on-premises and based on Pega 6 and Oracle 11g and getting re-platformed to Pega 8 and Oracle 19c. Alongside, there is integration with legacy applications (NPS, CISR-CMS, CISR-WM, COTAX, rd CESA, Corporate DataWarehouse) and 3 party systems such as SAP (ERP), SAML and Active Directory(Security and Documentum.          Participated in rearchitecting Case Management Systems (on-premises systems) to AWS Cloud environment using cloud agnostic architecture strategy. Involved in development with agile methodology. Coordinated with client regarding Non-functional requirement Worked on System Integrationarchitecture. Worked on DevOps – Git, Maven, Nexus, Ansible,Ansible Towers andJenkinsfor CI/CD pipelines Worked on Terraform, EKS and Helm for Clustered GitLab Installation in AWS cloud environment Automation of batch processes using Ansible Automation of scheduled start and stop processes of EC2 instances, databases etc. End to End Cloud Solutioning in AWS Cloud. Name of the Project: GAPP, IAG, Sydney, Australia Duration Project Type Sept.2019 – Feb.2020 (Sydney AUS) Development Role Technical Architect Technology JIRA, Java 8, JEE 8, Pega 7, Microservices, Spring Boot2 , Spring Cloud Netflix [Service Discovery (Eureka), Circuit Breaker (Hystrix), Intelligent Routing (Zuul) and Client Side Load Balancing (Ribbon) ], AWS, Kafka, Zookeeper, HTML5, CSS3, Bootstrap, JSON, SAML, OAuth with JWT, MongoDB, Postman, JUnit, GIT, Maven, Bamboo, Docker, Confluence GAPP, IAG, Sydney, Australia (Architect) IAG is the largest provider of General Insurance in Australia and New Zealand with more than AUD 12 billion premium every year and selling insurance under many leading brands such as NRMA Insurance, CGU and SGIO. Project Overview Overview At present each brand uses payment gateway of their choice directly and there is a scope to centralize, manage and optimize payment operations within IAG. GAPP was conceived based on these lines where the brand/consumer applications of IAG will use the generic APIs developed by GAPP which, in turn, wrap the Payment APIs of these Payment Providers and then route to appropriate payment Provider as requested by the Brand/Consumer. GAPP is also responsible for the boarding and un boarding of brands with the Payment Providers Project Experience and carries out some other functions such as keeping customers’ default Payment methods and notifications to the Consumer applications from the Payment Providers. GAPP is part of IAG’s wider microservices architecture such as CMS (their Customer Management System) and Order Management System. Application is deployed in Cloud Native environment in AWS. My Responsibilities        Authored Payment Gateway Market Research and Solution document with detail analysis, comparison and evaluation on features of Payment Gateways offeredby different vendors. The selection was based on features, security, compliance, performance and cost as well as existing usage by different brands. Continuous Integration/ Delivery using GIT, Maven, Ansible, Jenkins, Docker, etc. Low-level design documents for Manage Payment and Notification module. Hands-on development of Manage Payment RESTful web services for Adyen and Stripe using Spring Boot and deployed as micro-services. Hands-on development of Notification module and passing event payloads to distributed topics using Kafka. Test Driven Development (TDD) of RestFul services using rest assured maven plugin. Incorporating advanced security mechanisms for Payment System Name of the Project: GMIL, Office Depot, USA (E-Commerce) Duration Jan.2017 – Sep.2019 Application Enhancement and Project Type Migration Role Technical Lead Technology Java 11, JEE 8, Microservices, Spring Boot , Spring Cloud Netflix [Service Discovery (Eureka), Circuit Breaker (Hystrix), Intelligent Routing (Zuul) and Client Side Load Balancing (Ribbon) ], Java Messaging System (JMS) using Active MQ, Redis, NewGen’sOmniFlow Intelligent Business Process Suite (iBPS), HTML5, CSS3, Bootstrap, JSON, JSTL, JSP, SONAR, SAML, OAuth , JWT, MongoDB, Postman, JUnit, Jmeter, JProfiler, GIT, Maven, Jenkins, Docker, Kubernetes, Ansible, ELK . Office Depot is a leading office supply retail organization based out in the United States. It operates retail stores, e-commerce sites and a business-to-business sales organization. Project Overview Overview Gimillenia (GMIL) is used by Office Depot’s Customer Service Department to manage customer data and place and modify orders on behalf of the customers. The users of the system are InStore Representatives and Call center executives. Office depot is migrating its present N-Tier on-premises architecture to microservices Cloud native architecture. GMil is one of the micro services where customer data and their orders are managed are managed. It interacts with other applications such as Order Management, Vantiv (Credit Card Authorization), CDAP (Warehouse application) and ODEN (Email Notification Engine). Project Experience The configuration is centralized and Coforge is engaged in providing Application Development (Enhancement to cloud native and micro services architecture and migration to AWS), Enhancement and L2 and L3 support for Gimillenia. My Responsibilities            Leading a small team of resources to accomplish application development, enhancements and support Active participation in agile ceremonies. Decompose epics into user stories. Groom user stories and make accurate estimates through story points Design and Code reviews. Code artifact quality control using SONAR and crucible Implementing RESTful web services using Spring Boot and deployed as micro-services with embedded Tomcat Implementation of micro services using Spring Cloud/Netflix OSS (Zuul proxy, Eureka, Hysterix (Circuit Breaker) etc.) and ELK for Log Aggregation. Test Driven Development (TDD) of RestFul services using rest assured maven plugin. Incorporated security frameworks with OAuth2, SAML, JWT. Worked on AWS IAAS/ PAAS services like EC2, S3, ElasticBeanStack and integration with AWS services (SNS, SQS, ElastiCache, CloudFront, Route53, CloudSearch (Solr), DynamoDB) Participation in Load Testing and Profiling. Incorporate performance tuning. Analysis and resolution of production issues and issues raised by end users. Continuous Integration/ Delivery using GIT, Maven, Ansible, Junit, Docker, etc Name of the Project: SITA Voyager, UK Duration September 2014 – Dec.2016 Role Technical Architect Technology JIRA, Java 8, JEE, Oracle Weblogic Application Server, Websphere MQ [Java Messaging System (JMS)], OSB, SONAR, HTML5, CSS3, Bootstrap, Angular, Coherence 3.x, MongoDB, JSON, SoapUI, Postman, JUnit, SVN, Maven, Jenkins, Ansible,Elasticsearch, Logistics, Kibana. Project Type Development Project Overview Overview SITA Voyager is an Enterprise Application that aims at replacing its Mainframe based legacy system, Passenger Service System (PSS) with a combination of N-Tier architecture style which includes an integration tier. The new application is based on Java/JEE, Oracle Service Bus (OSB), Websphere MQ and Oracle database. Voyager is composed of airlines business domains such as reservations, inventory and departure control systems and access to that functionality is provided through well-defined interfaces (“Service Contracts”). It is intended to provide multi-tenant service to its clients (airline subscribers) hosted at SITA’s data center. The new system aims to be robust, scalable and extendable system. Agile methodology (Scrum) is followed for development. My Responsibilities      Part of core team and played role of a Technical Architect. Led teams in various phases of software development Design and Code reviews. Code artifact quality control using SONAR and through code walkthrough Project automation using Maven, Jenkins, Ansible, Shell Scripts, DTO generation, Linux scripts etc. Continuous Integration/ Delivery using Jenkins, Maven, Ansible, Junit, Cobertura, SVN etc Project Experience       Design and implement solutions and Technical resolutions of issues. Creation of technical documents such as Design documents, Standards & guidelines, installation guides, Release document, web services contracts etc. Guided team in extensive testing using JUnit, Soap UI, and Postman Etc. Conducting technical prototyping and proof of concept development to demonstrate business concepts and technology capabilities Incorporated performance tuning, clustering, Load balancing etc. Incorporated NFR testing such as security, performance testing, Log aggregation using ELK etc. and resilience testing Name of the Project: Machine to Machine (M2M) Device Platform (IOT platform)–Verizon, USA Duration Project Type November.2013 – August 2014 Development Role Offshore Developer Technology StarUML, Java, JEE, MQTT, AWS Lambda, Java JEE, WebServices (RestFul), Rabbit MQ, Apache Kafka, AMQP, XMPP, MQTT, XML, JSON, HTML5, CSS3, OAuth2, SSL/ TLS, Bootstrap, Amazon AWS, Oracle, JBoss (Wildfly) M2M Device Platform is a middleware product that connects end user sensors to Vertical Applications (such as mHealth and Building Energy Management). It comprises of Gateway applications and Sensor2Cloud (S2C). Project Overview Overview My Responsibilities S2C is a platform agnostic middleware hosted in the cloud that facilitates communication of sensor data with the vertical applications. It communicates with gateways in the user plane to retrieve data/responses from the sensor and send command to actuator. Besides, S2C provides control functions such as policy download, application management, access control and device management through its portals. It hosts the S2C Bus which is a message broker using MQTT and XMPP that integrates Gateway and 3rd party sensors on one hand and Verical Applications on the other.       Leading a small team of key java resources. Creation of Technical Architecture document. Requirement analysis, HLD, LLD and client sign off. Led a small team in accomplishing design and development of prototype in IOT and cloud computing. Development of prototype using alternate cloud providers Amazon AWS and Jelastic, Interacted with client for requirement clarification and design acceptance. Name of the Project: Medicaid Management Information System- Xerox, USA Duration March 2008 – Sept 2010 and August 2012 – June 2013 Role Technical Architect/ Technical Manager Microsoft Project Plan (MPP), UML, SOA, Migration/Support and Project Type Maintenance WebServices (SOAP), WildFly (formerly Technology JBoss), Hudson 2.x, SVN, Maven, JUnit, MuleSoft, Spring, Oracle, , FICO Blaze Advisor & Drools, BPEL, HTML5, ExtJS. Project Overview The Medicaid Management Information System (MMIS) is a healthcare enterprise application for claims processing and information retrieval system used by the states of the USA. Project Experience Overview MMIS can be customized to the need of a particular state. Important modules are Member, Provider Inquiry and Services and primary purpose of MMIS is to retrieve, adjudicate and pay claims to medical service providers. It also has a analytics and reporting module. MMIS is HIPPA compliant and works towards reducing cost for the state while protecting patients and providing better medical care. My Responsibilities      Led teams and authored Architecture Description Document along with client architects in the US. Project Automation and Continuous Integration/ Delivery using Hudson 2.x, Cruise Control, Maven, Junit, Cobertura, SVN etc. Setting technical guidelines and standards, review of core artifacts and providing technical direction to team, design and system integration. Implemented the Integrations module that involved interaction with external systems using Mule ESB. Ensuring that team performs within set technical guidelines, accomplished design and code reviews etc. EDUCATION R.V. College of Engineering and technology Ss B.E. (Computer Science) Professional Experience: Infosys, Bangalore - (Softwaree quality analyst ) Cisco, Bangalore (Senior Software Engineer) - IBM Internation Pvt. Ltd (Senior software Engineer) -