Deployment types, effort, and other criteria
Ideally, when deployment in each cycle is more, project teams would need bandwidth of DevOps resources, unless customers are willing to take up the task. We should have higher support in case of On-premise versions for this reason (or if a customer specifically agrees to do deployment themselves on receiving the file)
Type | Deployment effort in initial setup | Deployment effort in each cycle | Other criteria |
|---|---|---|---|
Shared Cloud | 1 | 0 | ο»Ώ |
Dedicated Cloud (Signzy procures) | 5 days | Β½ day
| *Subscription purchase and setup are done by Signzy. *Additional requirements of security, architecture, or design that need to be executed will require extra effort, for example, implementation of BYOK (bring your own key), encryption, and NATing. |
Private Cloud | Same as on-premise | Same as on-premise | Same as on-premise. |
On-premise- Internet access | 25-30 days | 2-5 days | *Inbound access to docker.signzy.tech is a must. ο»Ώ *Signzy shall provide credentials to clients for downloading their specific docker images. |
On-premise-Β No Internet access | 45-70 days | 5-12 days | *Requires dependency resolution done properly by the deployment personnel |
ο»Ώ
- The efforts where ranges are mentioned vary for small to large deployments, simple to complex. Example of simple- a piece of code change or flow change; Example of complex- feature additions that require changes in libraries or OS dependencies.
- The above efforts donβt include additional effort that may be required by the client-specific security settings and they are expected to go into product enhancement.
Getting help
Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.
You can reach out to us at [email protected].
ο»Ώ