Clean Architecture & Design Patterns in Practice · Lezione

Singleton e Factory Method

Implementi il pattern Singleton per creare istanze uniche e Factory Method per una creazione flessibile degli oggetti.

Lezione 1 di 411 passaggi

Singleton e Factory Method è una lezione Clean Architecture & Design Patterns in Practice gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Clean Architecture & Design Patterns in Practice, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Clean Architecture & Design Patterns in Practice include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Intro to Creational Patterns

Welcome to our lesson on Creational Design Patterns! These patterns are all about how objects are created.

They help us manage object instantiation in a way that makes our systems more flexible and robust. Instead of directly creating objects everywhere, we use patterns to control this process.

Singleton: One Instance Only

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

It's useful for resources that should be unique, like a configuration manager or a logger.
To achieve this, the class typically has a private constructor and a static method that returns the single instance.

Building a Basic Singleton

Here's a simple example of a Singleton. Notice the private constructor and the static getInstance() method.

The getInstance() method checks if an instance already exists; if not, it creates one. Otherwise, it returns the existing one.

public class SimpleLogger {
  private static SimpleLogger instance;

  // Private constructor to prevent direct instantiation
  private SimpleLogger() {
    System.out.println("SimpleLogger instance created!");
  }

  public static SimpleLogger getInstance() {
    if (instance == null) {
      instance = new SimpleLogger();
    }
    return instance;
  }

  public void log(String message) {
    System.out.println("LOG: " + message);
  }
}

public class Main {
  public static void main(String[] args) {
    SimpleLogger logger1 = SimpleLogger.getInstance();
    logger1.log("Application starting up.");

    SimpleLogger logger2 = SimpleLogger.getInstance();
    logger2.log("Processing user request.");

    if (logger1 == logger2) {
      System.out.println("Both logger references point to the same instance!");
    }
  }
}

Singleton: Thread-Safe Access

The basic Singleton can have issues in multi-threaded environments. If multiple threads call getInstance() at the same time when instance is null, more than one instance could be created.

We can make it thread-safe by using the synchronized keyword on the getInstance() method. This ensures only one thread can execute it at a time.

public class ThreadSafeLogger {
  private static ThreadSafeLogger instance;

  private ThreadSafeLogger() {
    System.out.println("ThreadSafeLogger instance created!");
  }

  public static synchronized ThreadSafeLogger getInstance() {
    if (instance == null) {
      instance = new ThreadSafeLogger();
    }
    return instance;
  }

  public void log(String message) {
    System.out.println("TS_LOG: " + message);
  }
}

public class Main {
  public static void main(String[] args) {
    // In a real app, threads would access this concurrently.
    // Here, we just show it works correctly sequentially.
    ThreadSafeLogger tsLogger1 = ThreadSafeLogger.getInstance();
    tsLogger1.log("Task A completed.");

    ThreadSafeLogger tsLogger2 = ThreadSafeLogger.getInstance();
    tsLogger2.log("Task B started.");

    if (tsLogger1 == tsLogger2) {
      System.out.println("Thread-safe instances are the same!");
    }
  }
}

Singleton Use Cases

When should you consider using the Singleton pattern?

Configuration Manager: To hold application settings, ensuring all parts of the app use the same settings.
Logger: For a single logging service to write application events.
Database Connection Pool: To manage a limited set of database connections efficiently across the application.

The Problem: Hardcoded Creation

Now, let's look at the Factory Method pattern. Imagine you have code that creates objects directly, like new Car() or new Truck().

What happens if you need to add a new vehicle type, or change how a Car is created? You'd have to find and update every place in your code that creates these objects. This makes your code rigid and hard to maintain!

Factory Method: Abstracting Creation

The Factory Method pattern solves this by defining an interface or abstract class for creating an object, but letting subclasses decide which class to instantiate.

It delegates object creation to specialized 'factory' methods.
This promotes loose coupling by allowing client code to work with interfaces instead of concrete classes.

Building with Factory Method

Let's create a system for different types of transport. We define a Transport interface, concrete transport classes, and then a TransportFactory with a factory method.

Each specific factory (e.g., CarFactory) knows how to create its specific product.

// Product Interface
interface Transport {
  void deliver();
}

// Concrete Products
class Truck implements Transport {
  @Override
  public void deliver() {
    System.out.println("Deliver by land in a truck.");
  }
}

class Ship implements Transport {
  @Override
  public void deliver() {
    System.out.println("Deliver by sea in a ship.");
  }
}

// Creator Interface (with Factory Method)
abstract class Logistics {
  public void planDelivery() {
    Transport t = createTransport();
    t.deliver();
  }

  // The Factory Method
  public abstract Transport createTransport();
}

// Concrete Creators
class RoadLogistics extends Logistics {
  @Override
  public Transport createTransport() {
    return new Truck();
  }
}

class SeaLogistics extends Logistics {
  @Override
  public Transport createTransport() {
    return new Ship();
  }
}

public class Main {
  public static void main(String[] args) {
    Logistics roadLogistics = new RoadLogistics();
    roadLogistics.planDelivery(); // Outputs: Deliver by land in a truck.

    Logistics seaLogistics = new SeaLogistics();
    seaLogistics.planDelivery(); // Outputs: Deliver by sea in a ship.
  }
}

Advantages of Factory Method

The Factory Method pattern brings several key benefits to your software design:

Loose Coupling: Your client code interacts only with the Logistics interface, not specific Truck or Ship classes.
Extensibility: You can easily add new transport types (e.g., AirLogistics with Plane) without changing existing Logistics or client code.
Single Responsibility: The responsibility of creating objects is moved to dedicated factory classes/methods.

Check Your Knowledge

Let's test your understanding of the Singleton and Factory Method patterns.

Rispondi nella lezione interattiva

Recap: Singleton & Factory

Great job! In this lesson, we explored two powerful creational design patterns:

Singleton: Ensures a class has only one instance and provides a global access point. Remember to consider thread-safety!
Factory Method: Delegates object creation to subclasses, promoting loose coupling and making your code more extensible.

These patterns are fundamental for building flexible and maintainable software. Next, we'll dive into more creational patterns like Abstract Factory and Builder!

Gratis per iniziare

Impara Clean Architecture & Design Patterns in Practice con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi: 12
Lezioni: 48

Inizia a imparare gratis Visualizza il corso completo

Domande Frequenti

La lezione «Singleton e Factory Method» è gratuita?

Sì — il testo completo di «Singleton e Factory Method» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Clean Architecture & Design Patterns in Practice, passa a CoddyKit PRO. Il corso Clean Architecture & Design Patterns in Practice include 4 lezioni in totale.

Cosa imparerò in «Singleton e Factory Method»?

Implementi il pattern Singleton per creare istanze uniche e Factory Method per una creazione flessibile degli oggetti. Eserciti Clean Architecture & Design Patterns in Practice con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Clean Architecture & Design Patterns in Practice?

Non è richiesta alcuna esperienza precedente. Clean Architecture & Design Patterns in Practice su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Singleton e Factory Method»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Clean Architecture & Design Patterns in Practice?

Sì. Ogni lezione Clean Architecture & Design Patterns in Practice include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

Singleton e Factory Method
Abstract Factory e Builder
Prototype e Object Pool
Dependency injection come tecnica creazionale

← Torna a Clean Architecture & Design Patterns in Practice