Balint Gyori

9 years Java developer experience. I worked on Spring Java applications, which used JSP, and later, an in-house UI framework (based on Google Soy Template technology). We used BDD specification for integration tests and Cucumber framework to implement them. We used well configured Maven plugins to automate as much as we could: code style checking, unit test coverage, integration tests, code complexity etc. Having spent much times with UI framework switching and with application splitting into micro-services, I have extensive experience in code refactoring. In the past I worked on a heavy weight swing based Java client application with Oracle DB. It was a very big and robust application developed for the government. Thus I have experience with old Java technologies, and I have seen their benefits and disadvantages.

My last project was developing Spring Boot based micro services with REST API. These micro services were part of a distributed system. I also created integration tests for these applications using WireMock, Spring Integration test and JSON mocking files. The CI pipeline was managed by Bamboo, and the application was wrapped into Docker containers. The full application was documented on the developers' side.

In the micro-service architecture world, monitoring is a very important part of the application development. Application monitoring should be part of the developers' task, since they know what is the most important information, what should be measured. The developers also have to configure alerts for themselves, which guarantees the shortest reaction time, and the quickest fix for the given problem.