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…
Blood, Sweat, and Writing Automated Integration Tests for Failure Scenarios
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.
Getting Started With JHipster, Part 1
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…
GrokOla Releases New UML Design Feature
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.We’re happy to announce the release of a UML Modeling design feature onย GrokOla, the tribal knowledge wiki for development teams. GrokOla users have always …
Sanitize: Good for Beer, Good for Data
When it comes to brewing, one of the most critical considerations is sanitization. The same fact can be said for development. In brewing you can introduce unintended flavors, create a lesser end product, or completely ruin your hard work. With development, you can introduce inaccuracies or bad data, errors can be caused or exposed to attack, and security holes can be created.
With best practices in sanitization, we can all enjoy better applications and better beer. In this blog, I discuss the importance of data sanitization in development (with tips for success), with parallels to sanitization in brewing.




