Can you explain the principle of the Service Locator pattern and its application in application architecture?

The Service Locator pattern is used for managing dependencies in an application. Its essence is that there is a centralized object — a service locator, which knows how to create and provide the necessary services (objects responsible for specific functions).

Application:

• Instead of each class directly creating or obtaining dependencies, it refers to the Service Locator.
• This simplifies replacing service implementations (for example, for testing).
• It helps avoid tight coupling of components.

Example in Swift:

protocol AnalyticsService {
    func track(event: String)
}

class ServiceLocator {
    static let shared = ServiceLocator()
    private var services = [String: Any]()

    func addService<T>(_ service: T) {
        let key = String(describing: T.self)
        services[key] = service
    }

    func getService<T>() -> T? {
        let key = String(describing: T.self)
        return services[key] as? T
    }
}

// Usage:
let analytics = MyAnalyticsService()
ServiceLocator.shared.addService(analytics)

if let analyticsService: AnalyticsService = ServiceLocator.shared.getService() {
    analyticsService.track(event: "AppStarted")
}

Cons: it can complicate dependency tracking and testing if used without caution.