Does ODC support zero-downtime deployments for large factories?

Since ODC only deploys one application container at a time, what happens when another application is dependent on those changes as well? We have a large factory of applications that are very interconnected for interoperable health purposes such that it's necessary to have separate applications. 

We have dozens of applications released in same lifetime deployment today in OS11, but how is this managed in ODC? 

Hi Sam,

You can deploy multiple applications at the same time, using different browser tabs.

There are a few things that mitigate much (but not all) of the concern of deploying apps independently to the next stage.

  1. Deployments in ODC are much, much faster than in O11, as only the binaries are copied from stage to stage. No recompilation is required.
  2. You can open multiple tabs in your browsers with ODC Portal and publish in each tab an App simultaneously.

Obviously, that does not avoid having a time window in which your applications integrated with each other to be incompatible. 

I already suggested to OutSystems that a deployment plan still makes sense also in ODC. It allows use to have a better user experience (see my bullet 2), but still use the benefit that all apps in the deployment plan can be deployed in parallel (see my bullet 1).

Furthermore, ODC promotes more loosely coupled application architecture (call it microservices, or whatever), that when using the right practices should also mitigate incompatibility between applications (services).

At Product League we already have a few ODC customers, but non can yet be categorized as large factories, for that ODC is not on the market long enough.



Thanks, yes, it makes sense. What we would be trying to avoid is in the example of adding an input to a service action, we wouldn't want to have to create a new service action in a core application, stage core app to production, then update the UI app to include additional input to new service action, stage UI app to production, then delete the original service action in core app and stage to production. That's possible but sounds very tedious. 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.