Deployment
Deployment generally refers to the process of taking a software application or system from a development environment and installing or making it available for use in another environment. For example, moving code from UAT to Production.
During the deployment process, all the processes involved in getting new software or hardware up and running in its environment are completed, including installation, configuration, running, testing, and making necessary adjustments.
Deployment is done for several reasons depending on the context, but generally, it is done to make an application or system available for use by its intended audience.
It is done to make the application available to end-users or customers. This involves making the application accessible on a server, configuring the required settings, and ensuring the application is secure, reliable, and performant.
You might need deployment in the following cases:
- A new feature release
- Product version Upgrade
- A bug fix
When we say cloud, we mean Signzy preferred vendors: Azure and AWS
- Signzy Shared cloud
- Signzy dedicated cloud instance, operated by Signzy
- Public cloud- Customer-owned, Signzy-operated Cloud instance
On-premises means that the instance is not operated by Signzy, broadly it means Signzy does not have root user access and is both owned and operated by customers.
This can be a cloud vendor, internal cloud, or even a bare metal server's true physical server. Signzy provides Docker instances for this type and would require a Docker-compatible infrastructure on the client's side.
We have two categories here:
- No internet access for outside application server
- Internet access for outside application server
Signzy provides the option to opt for a single tenant DB architecture where every client has their own independent & dedicated database VMs. This enables separation of database and logical + virtualized segregation for data of different customers.
Signzy also provides the multi-tenancy option by default which is an architecture in which the same database cluster serves multiple customers. In a multi-tenant architecture, each customer shares the same database clusters and enjoys virtually infinite scalability and near to zero downtime through a HA setup and is ideal for businesses that want a quick setup and swift go live.
For customers who require (a) separated infrastructure (b) want to keep the data & network segregated & (c) want additional security controls like BYOK we have a dedicated infrastructure option. Signzy procures an Azure subscription, sets up a separate network and VPC, and then procures servers for deployment. Signzy’s automated scripts conduct the deployment in the entire infrastructure (server hardening, application deployment, application hardening, and monitoring setup).
Once completed the newly set up system undergoes sanity testing by the Signzy team. Customers (& their infosec team) are welcome to carry audit of the infrastructure and application post-deployment if required.
Getting Help
If you have any questions, need clarification, or have suggestions to enhance our documentation or services, please don't hesitate to contact us.
Reach out to us at [email protected]