Why Builder Is Often an Antipattern and How to Replace it With Fluent Builder

The Builder Pattern is extremely popular in Java applications. Unfortunately, it’s often misunderstood and incorrectly applied, which results to runtime errors.

Let’s remember the purpose of Builder: set only necessary fields in some object and keep remaining fields set to default values. For example, if we’re preparing a configuration object, then it’s convenient to change only the necessary parameters and keep other parameters set to default values. 

Source de l’article sur DZONE