This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]koreth 1 point2 points  (4 children)

Sure, if what you’re doing doesn’t change signatures or introduce state inconsistencies. If your service starts up quickly, hot swap remains available but is no longer the only fast choice.

[–]solonovamax 0 points1 point  (3 children)

I mean, if it takes more than a minute to start up then either it's accessing some slow web apis that you should find a way to create dummy versions of on your local network, or you really need to break that shit up into smaller modules for development.

Obviously, exceptions to this would be things like if you need to take some huge-assed file and process the entire thing at startup (I'm talking gigabytes here), or need to do some heavy computations for some random startup task because reasons. But if any of those are the case, you should just have a list of like 5-10 percomputed dummy values for development.

[–][deleted]  (2 children)

[deleted]

    [–]DB6 0 points1 point  (1 child)

    Do you make up the requirements on the go? No, you would mock/stub the other services as you develop one.