Add search features to your application, try Elasticsearch part 2 : start small

Hi, This article is part of a whole which aims to describe how one could integrate Elasticsearch. The previous post discussed the concepts: why using a search engine?. No people learn the same way. I usually need to understand the theory and I need to start small. So I usually start by books. If there… Read More Add search features to your application, try Elasticsearch part 2 : start small

Add search features to your application, try Elasticsearch part 1 : the concepts

Hi all, The ultimate goal of a search engine is to provide fast, reliable, easy to use, scalable search features to a software. But before diving into complex and technical considerations we should ask ourselves why bother with a search engine. 1 – Why should my team bother with a new complex component ? Adding… Read More Add search features to your application, try Elasticsearch part 1 : the concepts

Testing security in RESTful application with jersey and jbehave

Security concerns emerges naturally in applications because softwares have so many capabilities and we sure don’t want these features to be available to anyone. The important words in the above sentence areĀ features and anyone. Securing an application is often a matter of 2 concepts : identifying who should/should not access the system : aka Authentication.… Read More Testing security in RESTful application with jersey and jbehave

Testing error handling in RESTful application with jersey and jbehave

Hi reader, As far as I’m concerned I write tests mostly for one reason : deal with the non-nominal path because in most cases the nominal path is the easier one. They help me dealing with the question “What if the user/client doesn’t provide correct inputs how will my application behave ?“ RESTful applications are… Read More Testing error handling in RESTful application with jersey and jbehave

Testing REST content negotiation with jersey and jbehave

Hi everyone, When building RESTful services one very common concern is content negotiation. This feature allows a client (REST client), to specify its preferred response formats. The idea is “Dear server I’m sending you an application/x-www-form-urlencoded content but I’d rather get application/json results.” It also allows a server to specify its preferred request formats. Client… Read More Testing REST content negotiation with jersey and jbehave