Skip to main content

Design Patterns: Builder

This is also, like a Singleton , one of the creational design patterns. It provides the way of creating complex objects step by step by simple chaining and every particular step is independent of other steps.

Let us dive into the real example of usage. For showing purpose we have created an example in C# which creates simple SQL queries using described pattern. 



using System;
using System.Text;

namespace BuilderPatternExample
{
    public interface ISqlQueryBuilder
    {
        ISqlQueryBuilder Select(string columns);
        ISqlQueryBuilder From(string table);
        ISqlQueryBuilder Where(string condition);
        ISqlQueryBuilder OrderBy(string columns);
        string Build();
    }

    public class SelectQueryBuilder : ISqlQueryBuilder
    {
        private readonly StringBuilder _queryBuilder;

        public SelectQueryBuilder()
        {
            _queryBuilder = new StringBuilder();
        }

        public ISqlQueryBuilder Select(string columns)
        {
            _queryBuilder.Append($"SELECT {columns} ");
            return this;
        }

        public ISqlQueryBuilder From(string table)
        {
            _queryBuilder.Append($"FROM {table} ");
            return this;
        }

        public ISqlQueryBuilder Where(string condition)
        {
            _queryBuilder.Append($"WHERE {condition} ");
            return this;
        }

        public ISqlQueryBuilder OrderBy(string columns)
        {
            _queryBuilder.Append($"ORDER BY {columns} ");
            return this;
        }

        public string Build()
        {
            return _queryBuilder.ToString().Trim();
        }
    }
    

    class Program
    {
        static void Main(string[] args)
        {
            ISqlQueryBuilder queryBuilder = new SelectQueryBuilder();

            string query = queryBuilder
                .Select("id, name, age")
                .From("Users")
                .Where("age > 18")
                .OrderBy("name ASC")
                .Build();

            Console.WriteLine("Generated SQL Query:");
            Console.WriteLine(query);
        }
    }
}
  
In this particular example we can see that we avoid to use hardcoded SQL strings and provide one flexible way of building the queries. Same example can be extended to other SQL commands. In the end, client that uses the builder interface does not need to care about the order of commands, or on spelling of SQL keywords.


When to use it?

  • When constructing a complex object requires many steps.
  • To create object with lot of optional parameters.
  • When constructing objects with immutable states.
  • To improve code readability and reduce the complexity of the object creation logic.

When not to use it?

  • When having simple objects with few properties.
  • High-performance systems with frequent object creation.
  • A singleton or a constant-like object.
  • If the codebase is unlikely to grow or change significantly.

Conclusion

The Builder pattern is ideal for creating complex objects step-by-step, especially when they have many configurable parts or require different variations. It improves code readability, ensures consistency, and simplifies object construction by separating the build logic from the object itself. However, it’s best suited for scenarios where complexity justifies its use—avoid it for simple objects or straightforward creation processes.
Labels:

Comments

Post a Comment

Popular posts from this blog

Design Patterns: Singleton

Tyipically the first design pattern most people learn, often wrongly ☺ To give an introduction, we can say that singleton is one of the creational design patterns which ensures only one class instance with single point of access thru entire application.  Because it is relatively simple to implement, the Singleton pattern is sometimes misapplied in situations where it is not the most suitable choice. When to use it? Here are the few examples of corrent usage of singleton: Configuration Management  Centralized configuration settings for consistent use thru entire application Caching Maintaning  Single istance of cached objects for easy and fast acces Logging  Ensure unified mechanism to avoid duplication of log files, formats, etc Global State Management  Centralized management of the state which is needed to be shared accross the application Resource sharing  Thread pools, database connection, I/O operations When not to use it? On the other hand, here are fe...
Post a Comment
Read more

Why Do Employers Lie In Interviews?

This is a very common subject that many of us have already experienced. But when you realize that half of what has been said at interviews is actually a lie, you are already at least six months in the company, you have already started some project and it wouldn’t be appropriate to leave the company at that moment. Why is this happening? First of all, let us see how the usual interview process looks like in software development companies. First round interview in most of these companies is an interview with HR. This is the first insight about the company. A person who works in HR is usually someone who, in most cases, doesn’t understand what the software is and how the software development process goes. Big respect to those companies where HR knows these things. This phase usually contains some standard questions about your personality, what do you like about the company, how this company is something that you are actually looking for, where you see yourself in five/ten  years etc… ...
Post a Comment
Read more