{"id":1,"date":"2025-05-13T21:24:30","date_gmt":"2025-05-13T21:24:30","guid":{"rendered":"http:\/\/instalatorwp671.dkonto.pl\/?p=1"},"modified":"2026-06-29T20:54:39","modified_gmt":"2026-06-29T20:54:39","slug":"patterns-builder","status":"publish","type":"post","link":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/2025\/05\/13\/patterns-builder\/","title":{"rendered":"Builder \u2013 When a Constructor Is Not Enough"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Imagine you need to create an object with a dozen fields \u2014 some required, some optional, some dependent on each other, and some that must be set in a specific order.

Sounds like a nightmare for a constructor and Programmer that has to re-apply everything in appropriate order?

That\u2019s exactly where the Builder pattern<\/strong> comes in. It turns parameter chaos into a clear, controlled process of building objects step by step.
<\/p>\n\n\n\n

The Problem: Constructor Hell<\/h4>\n\n\n\n

Let\u2019s take a simple example \u2014 an order configuration:<\/p>\n\n\n

<\/pre>\n
public class Order {<\/div>\n
\u00a0<\/pre>\n
\u00a0\u00a0\u00a0 private final String customer;<\/div>\n
\u00a0\u00a0\u00a0 private final String address;<\/div>\n
\u00a0\u00a0\u00a0 private final boolean isExpress;<\/div>\n
\u00a0\u00a0\u00a0 private final boolean giftWrap;<\/div>\n
\u00a0\u00a0\u00a0 private final String couponCode;<\/div>\n
\u00a0<\/pre>\n
\u00a0\u00a0\u00a0 public Order(String customer,<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 String address,<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 boolean isExpress,<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 boolean giftWrap,<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 String couponCode) {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.customer = customer;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.address = address;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.isExpress = isExpress;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.giftWrap = giftWrap;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.couponCode = couponCode;<\/div>\n
\u00a0\u00a0\u00a0 }<\/div>\n
\u00a0<\/pre>\n
}<\/div>\n\n\n
Usage:<\/p>\n\n\n
Order order = new Order(“John Doe”, “Gdynia”, true, false, null);<\/p>\n\n\n
The problem here is it’s pretty hard to read. Additionally – every extension requires too much effort, not mentioning vulnerability for errors<\/p>\n\n\n\n
The Solution: Builder<\/h4>\n\n\n\n
Instead of passing everything at once, we build the object step by step:<\/p>\n\n\n
<\/p>\n
public class Order {<\/div>\n
\n
\u00a0\u00a0\u00a0 private final String customer;<\/div>\n
\u00a0\u00a0\u00a0 private final String address;<\/div>\n
\u00a0\u00a0\u00a0 private final boolean isExpress;<\/div>\n
\u00a0\u00a0\u00a0 private final boolean giftWrap;<\/div>\n
\u00a0\u00a0\u00a0 private final String couponCode;<\/div>\n
\n
\u00a0\u00a0\u00a0 private Order(Builder builder) {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.customer = builder.customer;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.address = builder.address;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.isExpress = builder.isExpress;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.giftWrap = builder.giftWrap;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.couponCode = builder.couponCode;<\/div>\n
\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0 public static class Builder {<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 private String customer;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 private String address;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 private boolean isExpress;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 private boolean giftWrap;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 private String couponCode;<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Builder forCustomer(String customer) {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.customer = customer;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return this;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Builder shipTo(String address) {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.address = address;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return this;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Builder withExpressDelivery() {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.isExpress = true;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return this;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Builder withGiftWrap() {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.giftWrap = true;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return this;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Builder withCoupon(String code) {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 this.couponCode = code;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return this;<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 public Order build() {<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return new Order(this);<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/div>\n
\u00a0\u00a0\u00a0 }<\/div>\n
\n
}<\/div>\n\n\n
Yes – it is much more in the class definition – hovewer it pays off. Usage looks as follow:<\/p>\n\n\n
Order order = new Order.Builder()
.forCustomer(“John Doe”)
.shipTo(“Gdynia”)
.withExpressDelivery()
.build();<\/p>\n\n\n
Benefits are most of all – readability. For Usage we only have to get this information we want and in whatever order we want. Extension is also easy – we only have to extend the class and the extension is ready to use. No need to go through the entire code to make changes – not anymore!<\/p>\n\n\n\n
When do you want to use Builder?<\/h4>\n\n\n\n
There is number of cases when that pattern is suitable. First of all – if you have plenty of optional parameters – the Builder is there for you. With constructors you have to pay attention to every possible detail – and with Builder only the ones you want in particular situation.
It also benefits with complex objects, when extending them through constructor sounds terrible. With Builder you do just what you want to.
API readability is mentioned as advantages as well. A simple Query below proves that:<\/p>\n\n\n
Query query = new Query.Builder()
.select(“name”, “price”)
.from(“products”)
.where(“price > 100”)
.orderBy(“price DESC”)
.build();<\/p>\n\n\n
When avoiding Builders?<\/h4>\n\n\n\n
Builders are overkill for simple cases – if your class has like 4-5 fields and no extensions are coming in future – I would say you don’t need such a sophisticated solution in it. So Generally the Builder will be worse choice especially when the class you are concidering is something minor in your project – not too often used or just basically small.

The same goes for cases when you don’t need step-by-step configuration. Remember – always try to keep it as simple as situation allows to!<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Imagine you need to create an object with a dozen fields \u2014 some required, some optional, some dependent on each other, and some that must be set in a specific order. Sounds like a nightmare for a constructor and Programmer that has to re-apply everything in appropriate order? That\u2019s exactly where the Builder pattern comes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"saved_in_kubio":false,"footnotes":""},"categories":[11],"tags":[],"class_list":["post-1","post","type-post","status-publish","format-standard","hentry","category-pp"],"_links":{"self":[{"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/posts\/1","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/comments?post=1"}],"version-history":[{"count":13,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/posts\/1\/revisions"}],"predecessor-version":[{"id":397,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/posts\/1\/revisions\/397"}],"wp:attachment":[{"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/media?parent=1"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/categories?post=1"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/patryk-sobilo.profesjonalnyprogramista.pl\/index.php\/wp-json\/wp\/v2\/tags?post=1"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}