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…
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…
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.
There are very good reasons to use immutable objects in certain languages. In JavaScript, however, I’m still kind of…. meh.
In this blog post, I plan to discuss my reasonings with the hope that I might spark discussion on the use of Immutable Objects in JavaScript…
We are excited to announce the next Keyhole Software educational event: Angular 2 In Action! This is a live-coding learning opportunity open to the public. This free presentation will be held in St. Louis at the Courtyard Marriott in Creve Coeur, Missouri on Sept 1, 2016 from 8-10 a.m. / in Detroit, MI at Detroit Labs on Sept 22 from 6-8 p.m./ in Lincoln, NE at the Lincoln.Code() User Group meeting on Sept 28 from 6-8 p.m. Space is limited, so register for your free ticket today.