is ServiceLauncher a good name?
weissi opened this issue · 9 comments
I'm wondering whether ServiceLauncher is a good name for this. See #14 , I'm planning to use this for systems that start/stop sub-systems too. But I wouldn't really call my systems a "service" so I'm unsure if ServiceLauncher is a good name.
this was originally named lifecycle but that name was rejected by marketing folks, which suggested the current name. do you have alternative names?
I'm not a fan of just "Lifecycle" because there are many things which have lifecycles but do not necessarily fit this library or are intended to anyway. But perhaps we can find some middle ground?
Service to me sounded pretty good, since it's like the service command we know from linux envs, which kind of does similar things (even more tho)
What are other names... TaskLifecycle sounds also a bit off... SubSystemLifecycle a bit verbose... 🤔
We can think of these subsystems as "components", but this doesn't yield nice names either: ComponentLauncher, ComponentLifecycle...
ComponentLifecycle could be fine.
If we want a hip name then I just remembered we did something back in the Spray (before Akka HTTP) days and we used to call this: Boot() .
So could be an option here as well. (Short for Bootstrap, I guess then though we're back to "ComponentBootstrap"?). Feels like Boot could be it's own thing here -- since not a word used yet in other libs and not overlapping with "lifecycle" on the grand scale of things.
I'm usually leery of common names like "boot", as web search results will bring lots of non related results.
Spring Boot? 🤪 Yeah that is a risk... just flying by the idea.
If we like ServiceLifecycle + ComponentLifecycle that could mean swift-service-lifecycle as module would be nice...
ComponentLifecycle sounds the best to me.