I’m trying to use Spinnaker to manage two related services:
- Monolith: complicated SOAP-ish API
- Facade: simplified FORM-POST facade on the Monolith
Currently, implementing a feature usually involves making a business logic change in the Monolith then exposing those parameters in the simpler Facade API (the long-term goal is to make Facade a truly independent micro-service).
What’s the Spinnaker community’s take on using multiple vs single pipelines for this situation?
My gut instict is to use a single pipeline to deploy both services since they are coupled, but I could also see multiple pipelines where the Facade pipeline is triggered when the Monolith pipeline is successful. It seems like the choice would depend on which one provides a more coherent process, e.g.: rolling back only Facade vs rolling back both services.
but it’s unclear from the Codelabs what the best practices on Rollbacks are, e.g.:
- conditional Rollback stages in the pipeline based on an integration test failure
- manual Rollbacks operation from the Server Group panel (independent of Pipelines)