Swift summary manufacturing facility design sample

Summary manufacturing facility in Swift

The summary manufacturing facility sample offers a option to encapsulate a bunch of particular person factories which have a typical theme with out specifying their concrete lessons.

So summary manufacturing facility is there so that you can create households of associated objects. The implementation normally combines easy manufacturing facility & manufacturing facility methodology ideas. Particular person objects are created by manufacturing facility strategies, whereas the entire thing is wrapped in an “summary” easy manufacturing facility. Now verify the code! 😅

// service protocols
protocol ServiceFactory {
    func create() -> Service
}

protocol Service {
    var url: URL { get }
}

// staging
class StagingService: Service {
    var url: URL { return URL(string: "https://dev.localhost/")! }
}

class StagingServiceFactory: ServiceFactory {
    func create() -> Service {
        return StagingService()
    }
}

// manufacturing
class ProductionService: Service {
    var url: URL { return URL(string: "https://dwell.localhost/")! }
}

class ProductionServiceFactory: ServiceFactory {
    func create() -> Service {
        return ProductionService()
    }
}

// summary manufacturing facility
class AppServiceFactory: ServiceFactory {

    enum Setting {
        case manufacturing
        case staging
    }

    var env: Setting

    init(env: Setting) {
        self.env = env
    }

    func create() -> Service {
        change self.env {
        case .manufacturing:
            return ProductionServiceFactory().create()
        case .staging:
            return StagingServiceFactory().create()
        }
    }
}

let manufacturing facility = AppServiceFactory(env: .manufacturing)
let service = manufacturing facility.create()
print(service.url)

As you possibly can see utilizing an summary manufacturing facility will affect the entire utility logic, whereas manufacturing facility strategies have results solely on native components. Implementation can fluctuate for instance you may additionally create a standalone protocol for the summary manufacturing facility, however on this instance I wished to maintain issues so simple as I may.

Summary factories are sometimes used to realize object independence. For instance when you’ve got a number of completely different SQL database connectors (PostgreSQL, MySQL, and many others.) written in Swift with a typical interface, you may simply change between them anytime utilizing this sample. Identical logic might be utilized for something with an identical state of affairs. 🤔