Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Design Pattern : Builder" | Hashnode

Feed/

Discussion

jean joel Ntepp

Software developer

Apr 3, 2024

Design Pattern : Builder

Introduction Design patterns are generic solutions to classic problems encountered in software development and many other fields. As a software developer, knowing them often means having a good grounding in computer science. Of course, it's not enoug...

blog.nameksoft.xyz5 min read

#design-patterns #builder-pattern #clean-code #clean-architecture #java #lombok

Responses1

Markdown supported · ⌘↵ to post

Lionel Owono

Cloud Architect with a passion for data and AI. Skilled in OpenShift, GCP, and AWS. Blend of leadership and technical expertise.

Apr 3, 2024

Hello good article, can you please explain de difference with factory pattern ?

Hi Lionel, thanks for interacting.

Both patterns belong to the family of object construction patterns. The Factory pattern is useful when you want to create different types of objects from a class (a dedicated factory). The Factory class generally relies on conditions to determine which type of object to build.

It's the expression "different types of objects" that marks the difference between the two patterns. In the case of the Builder, built objects are always of the same type.

jean joel Ntepp

Software developer

Apr 3, 2024

Lionel Owono

Cloud Architect with a passion for data and AI. Skilled in OpenShift, GCP, and AWS. Blend of leadership and technical expertise.

Apr 5, 2024

jean joel Ntepp

Thanks for you answer.