Home  >  Article  >  Backend Development  >  Go Design Patterns #Singleton

Go Design Patterns #Singleton

Patricia Arquette
Patricia ArquetteOriginal
2024-10-08 06:08:30423browse

Go Design Patterns #Singleton

Design patterns are tried-and-tested solutions to common problems that arise in software design. They provide a template or guide for solving these problems in a flexible and reusable way.

Each pattern represents a best practice that developers can adapt to their specific context. Design patterns are often classified into three main categories.

To kickstart this series, let's talk about the Singleton pattern.

Singleton

The Singleton pattern ensures that a class has only one instance and provides a global point of access to that instance.

This is useful in cases where you need to manage a shared resource, such as database connections or configuration settings.

Problem Statement

Often there is the need to ensure that only one instance of a class exists, such as when managing configurations or interacting with hardware resources. Without Singleton, creating multiple instances can lead to issues like inconsistent data or resource locks.

This is very common to happen when working with asynchronous code, where multiple goroutines can create new instances of a class or access shared resources.

Real-World Example

Consider a database connection pool: If multiple parts of your application create new connections at the same time, you may end up with redundant or conflicting database interactions. A Singleton ensures only one connection is created and used across the application.

Implementation

package main

import (
    "fmt"
    "sync"
)

type Singleton interface {
    DoSomething() string
}

type singleton struct{}

var lock = &sync.Mutex{}

var instance *singleton

func NewSingletonInstance() *singleton {
    if instance == nil {
        lock.Lock()
        defer lock.Unlock()
        if instance == nil {
            fmt.Println("Creating single instance now.")
            instance = &singleton{}
        } else {
            fmt.Println("Single instance already created.")
        }
    } else {
        fmt.Println("Single instance already created.")
    }

    return instance
}

func (s *singleton) DoSomething() string {
    return "Doing something."
}

func main() {
    instance1 := NewSingletonInstance()
    instance2 := NewSingletonInstance()
    fmt.Printf("%p\n", instance1)
    fmt.Printf("%p\n", instance2)
}

The function NewSingletonInstance ensures that only one instance of singleton is created, even when called multiple times.

  • First, it checks if instance is nil (i.e., no instance has been created yet).
  • If instance is nil, it locks the section of code using lock.Lock() to prevent multiple goroutines from entering this section simultaneously.
  • After locking, a second check is performed to ensure that no other goroutine created the instance between the first check and the time the lock was acquired.
  • If instance is still nil, a new singleton instance is created and assigned to the global variable.
  • The sync.Mutex and double-checked locking ensure that the creation of the singleton instance is thread-safe, preventing multiple goroutines from creating separate instances.

The above is the detailed content of Go Design Patterns #Singleton. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn