Sergey Zolotaryov

Rewriting of customer registration portal, rates query/aggregation service, rewards enrolment program. Participated in the frontend and now on the backend side of the process.

Maintaining and migrating message delivery APIs to new internal framework. Developing and releasing to production of a web front end (Polymer/Redux from JSP based legacy) and backend (Springboot from Websphere based) for a template managing system XLetter 2.0, a re-write of a legacy front/backend. Rewrote several other internal web applications using the same tools: Polymer & Springboot. Set-up and wrote automated front-end tests using JUnit & Selenium. Developed integration tests and mock server in Kotlin.

Splitting a legacy recommendations backend into microservices, moving it from private datacenter to the Google Cloud Platform.

Middleware/reporting part of the ING pricing solution. My role was initially an engineer’s one, but then I moved to the tech lead role. We were using Apache Ignite (Gridgain) as the data layer to exchange data between components, also a GRPC API on top of it. The system is based on loosely coupled services / microservices. The technologies were: ActiveMQ, XML/Google Protocol Buffers, Tibco, Apache Ignite, Oracle, Apache Karaf, Spring Boot, Docker. The usual CI/CD stuff applicable.

A lot of internal projects. Mostly developing middleware/integration solution for the legacy backend system to enable customers consume data in various formats. Used Camel, Java SE, Spring, AspectJ, Javassist, Velocity, JAXB/Xmlbeans, CXF, Jetty, Angular, ActiveMQ/Tibco. Most recent project includes scheduling and orchestration system which integrates the different parts of company's product suite into a manageable package. Based on AKKA (using Java).

Rewriting a huge legacy front-end based on Swing connected to EJB backend for Parexel. Used IceFaces (a flavor of JSF) and SpringMVC based backend still connected to the EJB server.

Trade monitoring software for Deutsche Bank. Used a lot of JSF/Velocity/JPA, BEA Weblogic.

Everything depends on the customer you are working for. We worked for a very active and interesting customer, which meant a lot of deadlines, tasks and technologies involved. The main goal was creating a mobile communications and advertising platform based on JavaSE and SMS. Technologies used: Spring, Struts, Eclipse RCP, Resin.

Developing web services. Integrating hotel/ticket/taxi/insurance web service to create a homogeneous solution for the end users. We used SOAP Web services, REST services, Firebird, Tomcat.