Venkata C

Responsibilities: • Developed a POC to prove that a reactive system such as Vert.x would be an efficient solution than traditional blocking apis written in Spring MVC for this particular use case. • Lead the team to build a reactive micro system using Vert.x and java 8. • Upgrading Appian 7.9 to 17.1 along with JBoss up gradation and database backup and restoration • Worked on Appian Integration with external systems such as using Web Services, Connectors, Web APIs R.ich experience in designing Appian BPM complex processes. • Creating Appian artifacts by following best practices • Developed skeletons for vert.x reactive non blocking apis, so that the team can work on the implementations. • Developed reactive non-blocking rest apis to flawlessly serve millions of events during the peak time. • Used non-blocking vertx-pg client to communicate with postgres db. • Built the front end using React JS. • Developed react components using classes and hooks in react. • Used Redux as a state container to reduce the complexity of updating state through multiple tiers. • Used material-ui for react to style the components. Customized the material-ui themes and palette to match our needs • Developed a data dense and responsive front end using react components. • Used Postgres as it supports both SQL and no SQL (json and jsonb) features. • Wrote Queries to query jsonb Objects and perform aggregations. • Moved most of the business logic to postgres queries to optimize the response times of the rest apis. • Used Vert.x shared data for quicker access to static resources • Used Vert.x event bus to pass messages and replies within the system. • Configures Jenkins pipeline for continuous deployment to openshift PAAS. • Configured auto scaling and the resource values in openshift. • Worked with UI team to build intuitiveand low latency we application to display the events • Lead the peer review sessions and moderated the Git commits and merge requests.

Responsibilities: • Involved in business meetings with partners to gather information of their public apis. • Gave my inputs while architecting the application flows • Developed high throughput rest apis. • Used adaptor and factory pattern to onboard new partners with minimal redo of the existing code • Used Java 8 lambda expressions and filters. • Worked on POC’s to make use of java 8’sstream api’s functions like collectors and filters. • Used java 8’s Completable future to run asynchronous tasks. • Used json path library to parse the json response from partner, which helps in reducing the cpu utilization. • Used spring dependency injection. • Worked on POC’s to show the usage of hazelcast cache with Jcache • Responsible for developing the hazelcast cache layer to speed up the response times • Used swagger to generate the api spec • Integrated our apis with UI pages which are developed using Angular js • Used Log4j and slf4j to generate splunk logs and developer logs • Worked with linux/shell commands to do manual deployments of the jars • Used JIRA as the project management tool Environment: Java 1.8, Spring Dependency Injection, linux, curl, Hazelcast In Memory Cache, IBM DB2, Maven, Jenkins, Github, Jcache, log 4j,JIRA, splunk, Angular JS

Responsibilities: • Involved in requirements gathering, planning, developing and production support of this project • Used Jira and agile methodology to assign stories and track the progress of the project • Implemented the project using Spring MVC • Produced RestFul webservices for HCSC legacy services so the front end client can communicate using HTTP and json data • Consumed SOAP webservices from the legacy services to get the subscriber data and then give it to the Appian front end application • Implemented Spring Dependency Injection DI along with Spring MVC • Implemented Spring AOP to add an interceptor which adds a saml token to the request for authentication at the SOAP services provider • Used Log4J to generate debug and info messages • Used LDAP and JAAS to maintain Web Services Security in the application. • Used MAVEN as build tool and used Maven Assembley plugin to package the project • Used soapui to generate stubs and pojo classes from wsdl • Used soapuito test rest and soap webservices • Used curl scripts to test the restfull webservices provided by the application in the Test Environment • Used TomEE as the application server • Used GitHub as repository and Jenkins for continues integration • Done a POC to show that the existing project can be built on springboot framework. Environment: Java, J2EE, Spring MVC, Spring AOP, REST,SOAP,TomEE, Curl script, Eclipse, JUNIT, MAVEN, Log4j,JUNIT