One main contributor to slow start is when there is a Micro Storage, and it has to start up in Docker.
The fix here is to make sure the user knows why it is taking longer instead of it just looking like it is stalled for no reason.
One, from a SAM perspective, if you run the service (that has a dep on a storage), and docker isn't running, then you get a sad opaque error message. We should make that more obvious.
Two, from Unity, the play-button for a service that has a dep on storage should be disabled if Docker isn't running. (prevent mistakes instead of treating mistakes)
The project ps -w command should emit more states for "starting", "starting deps", "booting microservice", etc, or as many intermediate states as make sense to inform Unity a nice loading experience.
Linked to https://github.com/beamable/BeamableProduct/issues/3175
One main contributor to slow start is when there is a Micro Storage, and it has to start up in Docker.
The fix here is to make sure the user knows why it is taking longer instead of it just looking like it is stalled for no reason.
One, from a SAM perspective, if you run the service (that has a dep on a storage), and docker isn't running, then you get a sad opaque error message. We should make that more obvious.
Two, from Unity, the play-button for a service that has a dep on storage should be disabled if Docker isn't running. (prevent mistakes instead of treating mistakes)
The
project ps -wcommand should emit more states for "starting", "starting deps", "booting microservice", etc, or as many intermediate states as make sense to inform Unity a nice loading experience. Linked to https://github.com/beamable/BeamableProduct/issues/3175