Trends and insights from our IT experts

In this article, we will fully configure service-to-service communication, making our service/application always behave as expected, even in cases when the services it is trying to reach are behaving unpredictably - they may be fully down, or currently unavailable, or randomly failing to respond.

The ultimate management sin. It sounds like this should be an easy sin to avoid, but it isn’t. You have some needs of your own as a manager, and these needs may run squarely against your intention to preserve and use wisely the time of the people working under you.

This article is part of the JPA Pitfalls series. JPA makes it really easy to do things the wrong way, and makes it really unintuitive to do things right. In this blog post series I will go over some common JPA pitfalls, and introduce generating IDs.

In this article, we are going to discuss different JPA fetching types, their pros and cons, and see which one you should prefer. This article is part of the JPA Pitfalls series.

Separating product features into "Must-haves", "Should-haves", "Could-haves" and "Would-haves" (commonly known as MoSCoW) can provide a great deal of information about how to prioritize work for a new product release.