2022-09-27
3445
#node#typescript
Ganesh Mani
33247
Sep 27, 2022 â‹… 12 min read

Understanding design patterns in TypeScript and Node.js

Ganesh Mani I'm a full-stack developer, Android application/game developer, and tech enthusiast who loves to work with current technologies in web, mobile, the IoT, machine learning, and data science.

Recent posts:

Nx Adoption Guide: Overview, Examples, And Alternatives

Nx adoption guide: Overview, examples, and alternatives

Let’s explore Nx features, use cases, alternatives, and more to help you assess whether it’s the right tool for your needs.

Andrew Evans
Mar 28, 2024 â‹… 9 min read
Understanding Security In React Native Applications

Understanding security in React Native applications

Explore the various security threats facing React Native mobile applications and how to mitigate them.

Wisdom Ekpotu
Mar 27, 2024 â‹… 10 min read
Warp Adoption Guide: Overview, Examples, And Alternatives

warp adoption guide: Overview, examples, and alternatives

The warp web framework for Rust offers many enticing features. Let’s see when and why you should consider using warp in your projects.

Ukeje Goodness
Mar 26, 2024 â‹… 8 min read
Integrating Next Js And Signalr For Enhanced Real Time Web App Capabilities

Integrating Next.js and SignalR to build real-time web apps

In this tutorial, you’ll learn how to integrate Next.js and SignalR to build an enhanced real-time web application.

Clara Ekekenta
Mar 25, 2024 â‹… 8 min read
View all posts

6 Replies to "Understanding design patterns in TypeScript and Node.js"

  1. Singleton is antipattern, actually. At least in the described form. Makes testing really hard, creates hidden dependencies…
    If you have a dependency container, it can handle providing single instance of a service. This is a better form of singleton.

  2. The Singleton getInstance() implementation as presented may not work as expected depending on how MongoClient.connect is implemented. If the callback for .connect is invoked some time later when the connection is established (as is typical), then “this.instance” will not be set in time for the “return this.instance” line. If the assumption or behavior here is that getInstance() should return a promise that resolves to the client connection then the MongoClient.connect call should be wrapped in a “new Promise(…)” that resolves to mongo client inside the connect callback or rejects with an error from the callback.

  3. Singleton and Builder design patterns do not go well in javascript.
    Javascript has object literals, which solves the verbosity constructors with long parameter lists, funnily enough you gave an example of this User taking IUser object.
    And singleton is just a convoluted way to do something that is already solved by javascript modules.
    Each module is already a singleton imported via a path.
    It can export a class through the module, but that’s just extra unnecessary code.

    Please keep the Java/C# design patterns out of idiomatic javascript.

    Also Utill classes are not idiomatic javascript which has first cass support for functions.

Leave a Reply