How to deploy related microservices?

R

raiboon2022-01-26 22:04:33

Software Deployment

raiboon, 2022-01-26 22:04:33

It periodically pops up that they made changes for some feature in several microservices.
Happy, we roll them out to the prod and something falls off, because some service was forgotten.
How to avoid this?
Technically? Administratively?
Project in fat, deploy through concourse, turnips in bitbucket.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

D

Dmitry Roo, 2022-01-26
@xez

Reduce the delivery time of the code to the prod - then you won't forget anything

V

Vitaly Karasik, 2022-01-27
@vitaly_il1

1) As nApoBo3 already hinted , it shouldn't be a problem to update one microservice - as this should not break compatibility with the rest, at least for several versions.
2)

Happy we roll them out

- as already said, there should be a test (staging, pre-production, your-name-it) environment to deploy and test there - at least manually, better automatically
3) deployment should be automatic, with all dependencies, so that nothing is forgotten

A

Alexander Prokhorovich, 2022-01-26
@alexgp13

"in prod and something falls off"
And the test circuit? It's a good practice when rolling out updates to test all the main functionality first, just to check that nothing has fallen off. Even if the changes do not seem to affect these areas. And only then in prod.
You can also, for example, have dependency tables in order to know what to check for this or that change.