OutSystems allows delivering enterprise web and mobile applications that run in the cloud, on-premises or in hybrid environments. Since it covers the full application lifecycle, from development to deployment, a typical OutSystems installation is comprised of an infrastructure with four environments:
- Development Environment: In development you create accounts for all developers and development managers of the Development Team.
- Quality Environment: In quality environment is where testers and business users experiment the production candidate applications or the application versions resulting from (agile) sprints. There are usually few scalability and redundancy requirements for this environment.
- Production Environment: In production, full control is given to the Operations team but is advisable to setup read-only access accounts for development/maintenance teams to have access to analytics information on performance and application errors.
- LifeTime Environment: LifeTime is the console for managing the infrastructure, environments, applications, IT users, and security.
Even though this is the typical OutSystems infrastructure, you can always adjust the infrastructure to add and remove environments, since the Platform is made to scale with your own needs.
If you need to retain the control of your servers, simply install OutSystems in your own datacenter.
The scenario depicts an infrastructure where you manage the environments: Development, Quality Assurance, Production and LifeTime. In this case you’ll have to install the Platform Server in each server of your infrastructure (front-ends and deployment controllers), and Service Center for each environment, to monitor them. You’ll also need to install LifeTime, the console to manage your infrastructure. Given its requirements, LifeTime must run in a dedicated environment. Installing LifeTime in an existing environment is not supported from version OutSystems 11 onwards.
Since OutSystems runs on the cloud, it is possible to set-up your infrastructure with a mouse-click. You only have to install Service Studio and Integration Studio development tools to start developing and deploying your applications. Learn more at www.outsystems.com.
If you want to balance the simplicity and cost savings provided by the cloud, while retaining the control of part of your infrastructure, you can have some environments of your infrastructure running on the cloud and install the rest of the environments on your own data center.
The scenario depicts an infrastructure where the Development and Quality Assurance environments are on the cloud, making them easily scalable to the current development needs, while the Production environment remains installed in your own data center.
In this case you’ll not only have to install the development tools to start developing and deploying your applications, but you also need to install OutSystems Platform Server on each server of the Production environment. You’ll have to install as well Service Center, the management console for the environment.