Sree P.

About Sree P.

I am an experienced Java developer with a profound passion for software development and a…

Experience

1. Java Software Engineer

   Amegy Bank

   Jun 2024 — Present · Houston, TX, US

   Involved in Requirements gathering, analysis, design, and documentation as the application was started from scratch.• Implemented modules using Core Java APIs, Java collection, Java 11 (Streams), multi-threading, and object-oriented designs.• Worked with Java 8 features like Lambda Expressions, Filters, Stream API, forEach() method in Iterable interface, new Date API, Predicates, and Functional Interfaces. • Responsible for developing Java components using Spring, Spring JDBC, and Spring Transaction Management. • Implemented MVC design pattern using Spring Framework. • Involved in developing the applications using Spring Framework for Dependency Injection (Inversion of Control), Implemented the business logic using EJB (session and entity beans). • Designed and developed Microservices using REST framework and Spring Boot and used Bootstrap along with Angular.js in creating the Application. • Used Microservice architecture, with Spring Boot-based services interacting through a combination of REST.• Used Annotation based Spring Boot extensively for handling the frontend AJAX requests. • Used Spring Boot-based services to interact through a combination of REST. Designed and Implemented the DAO layer using spring, and hibernate.• Designed, developed, and maintained the data layer using Hibernate and performed configuration of Spring Application Framework.• Implemented modules into node.js to integrate with designs and requirements.• Used Amazon Web Services (AWS) for Java API to upload and retrieve users\' media data.• Created and compiled XML Schema to generate Java Bean classes. • Used EJB Stateless/Stateful session beans to implement business logic, session handling, and transaction and deployed Enterprise Java Beans both Session and Entity on WebSphere Application Server. • Log4J is used for logging purposes and debug levels are defined for controlling what we log.