This is a list of 10 best practices that are more subtle than your average Josh Bloch Effective Java rule. While Josh Bloch's list is very easy to learn and concerns everyday situations, this list here contains less common situations involving API / SPI design that may have a big effect nontheless. I have encountered…
Availability and reliability are paramount for all web applications and APIs. If you’re providing an API, chances are you’ve already experienced sudden increases in traffic that affect the quality of your service, potentially even leading to a service outage for all your users. The first few times this happens, it’s reasonable to just add more capacity to your infrastructure to accommodate user growth. However, when you’re running a production API, not only do you have to make it robust with techniques like idempotency, you also need to build for scale and ensure that one bad actor can’t accidentally or deliberately affect its availability.
List<Predicate> predicates = new ArrayList<Predicate>();
//Adding predicates in case of parameter not being null
if (param1 != null) {
predicates.add(
qb.equal(customer.get("someAttribute"), param1));
}
if (paramNull != null) {
predicates.add(
qb.equal(customer.get("someOtherAttribute"), paramNull));
}
//query itself
cq.select(customer)
.where(predicates.toArray(new Predicate[]{}));
S. Bechhofer, R. Volz, and P. Lord. The Semantic Web -- ISWC 2003: Second International Semantic Web Conference, Sanibel Island, FL, USA, volume 2870 of Lecture Notes in Computer Science, Springer, Berlin, (2003)
J. Broekstra, A. Kampman, and F. van Harmelen. The Semantic Web -- ISWC 2002: First International Semantic Web Conference Sardinia, Italy, volume 2342 of Lecture Notes in Computer Science, Springer, Berlin, (2002)