In part two of this series, we create a microservice architecture using JHipsterโs available options for doing so. There is quite a bit more work to do with this approach as compared with the monolithic approach. But, in the end, it pays off. You will see the benefits and flexibility in decoupling our different layers of our architecture. Each layer will not be dependent upon another to run. Let’s get started…
I introduce the process I went through to diagnose the bug and determine the correct integration test solution to fix it the right way. In doing so, I had to create a test that accurately reproduced the scenario my service was experiencing in PROD. I had to create a fix that took my test from failing to passing. And finally, I worked to increase confidence in the correctness of code for all future releases, which is only possible through automated testing.
So, you want to stay on the leading edge of technology, but feel overwhelmed by all the moving parts. Youโre in luck! jHipster aims to make setting-up an app fairly painless.
In this jHipster series we are going to take you through, first, creating a monolithic application. Secondly, we will make an app in the microservices style. Last, weโll give you some tips and tricks for jHipster best practices. Let’s first begin with Part One…
Attention: This article was published over 10 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Being a strong advocate of Spring Batch, I’ve always talked about the notion of Spring Batch providing developers with a framework that allows them …
I recently wrapped up attending the SpringOne Platform conference in Las Vegas. If you didn’t attend SpringOne, you’ll definitely want to read this post. We’ll go over four main themes from the conference and how to get started applying them in your endeavors going forward.