Swift Service Lifecycle provides a basic mechanism to cleanly start up and shut down the application, freeing resources in order before exiting.
It also provides a Signal-based shutdown hook, to shut down on signals like TERM or INT.
Swift Service Lifecycle was designed with the idea that every application has some startup and shutdown workflow-like-logic which is often sensitive to failure and hard to get right. The library codes this common need in a safe and reusable way that is non-framework specific, and designed to be integrated with any server framework or directly in an application. Furthermore, it integrates natively with Structured Concurrency.
This is the beginning of a community-driven open-source project actively seeking contributions, be it code, documentation, or ideas. What Swift Service Lifecycle provides today is covered in the API docs, but it will continue to evolve with community input.
If you have a server-side Swift application or a cross-platform (e.g. Linux, macOS) application, and you would like to manage its startup and shutdown lifecycle, Swift Service Lifecycle is a great idea. Below you will find all you need to know to get started.
To add a dependency on the package, declare it in your Package.swift:
.package(url: "https://github.com/swift-server/swift-service-lifecycle.git", from: "2.0.0"),and to your application target, add ServiceLifecycle to your dependencies:
.product(name: "ServiceLifecycle", package: "swift-service-lifecycle")Example Package.swift file with ServiceLifecycle as a dependency:
// swift-tools-version:5.9
import PackageDescription
let package = Package(
name: "my-application",
dependencies: [
.package(url: "https://github.com/swift-server/swift-service-lifecycle.git", from: "2.3.0"),
],
targets: [
.target(name: "MyApplication", dependencies: [
.product(name: "ServiceLifecycle", package: "swift-service-lifecycle")
]),
.testTarget(name: "MyApplicationTests", dependencies: [
.target(name: "MyApplication"),
]),
]
)Below is a short usage example however you can find detailed documentation on how to use ServiceLifecycle over here.
ServiceLifecycle consists of two main building blocks. First, the Service protocol and secondly
the ServiceGroup. As a library or application developer you should model your long-running work
as services that implement the Service protocol. The protocol only requires a single func run() async throws
method to be implemented.
Afterwards, in your application you can use the ServiceGroup to orchestrate multiple services.
The group will spawn a child task for each service and call the respective run method in the child task.
Furthermore, the group will setup signal listeners for the configured signals and trigger a graceful shutdown
on each service.
actor FooService: Service {
func run() async throws {
print("FooService starting")
try await Task.sleep(for: .seconds(10))
print("FooService done")
}
}
@main
struct Application {
static func main() async throws {
let service1 = FooService()
let service2 = FooService()
let serviceGroup = ServiceGroup(
services: [service1, service2],
configuration: .init(gracefulShutdownSignals: [.sigterm]),
logger: logger
)
try await serviceGroup.run()
}
}Please see SECURITY.md for details on the security process.