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.
Attention: The following article was published over 9 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.At Keyhole, we have published several blogs about Microservices. We’ve talked about architectural patterns used in a Microservices environment such as service discovery and circuit breaker. We’ve even posted blogs on platforms …
Attention: The following article was published over 9 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.I had some time before my next project started up, so David Pitt asked me to research and write a blog on Service Fabric. It sounded terrifying. First off, I’m not really what you …
Attention: The following article was published over 9 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.Introduction Update! Whirlpool now uses the “just released” Netty version 4.1.3. The great news about this is the upgrade required zero code changes, just update the pom and rebuild! In my last …
