• Replies 3 replies
  • Subscribers 13 subscribers
  • Views 4190 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

Appian Cloud Environments for my Client

rmanugarra

Can anyone tell me as to how many number of environments are ideal when we are working on an Appian project?

Currently we have - 

 

DEV  (cloud env)

TEST (cloud env)

PRODUCTION (cloud env)

We use DEV for all the appian development, test for all the testing and then move it to Production. Should we also ideally have a pre-production environment to ensure all code is first deployed on pre-prod before it is pushed to production? In what kind of projects do we have more than 3 environments?

  Discussion posts and replies are publicly visible

Parents
  • Certified Lead Developer

    I'd say that it depends on the size of the project/team/organisation.

    My personal preference is to have 4 environments for the following reasons:

    • A User Acceptance Testing/Staging environment is especially useful if you are currently working on a bigger feature with breaking changes (which would require data migration). UAT/STG allows you to develop a hotfix that you can deploy to production and then retrofit back into your DEV environment. This environment is essentially a mirror of your production environment.
    • It can also be useful for training purposes. i.e. you are actively developing and releasing new features to your Test environment but you want stable environment for training users.
Reply
  • Certified Lead Developer

    I'd say that it depends on the size of the project/team/organisation.

    My personal preference is to have 4 environments for the following reasons:

    • A User Acceptance Testing/Staging environment is especially useful if you are currently working on a bigger feature with breaking changes (which would require data migration). UAT/STG allows you to develop a hotfix that you can deploy to production and then retrofit back into your DEV environment. This environment is essentially a mirror of your production environment.
    • It can also be useful for training purposes. i.e. you are actively developing and releasing new features to your Test environment but you want stable environment for training users.
Children
No Data

© 2024 Appian. All rights reserved.