function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Jay JanarthananJay Janarthanan 

Multiple developers , single sandbox or individual sandboxes ?

Both approaches have its pros and cons. What do you prefer and why ?
 
Richard Jimenez 9Richard Jimenez 9
Hi Jay,

I would say it really depends on :
  • What you are implementing? - all config, all code, a product, multiple features, bug fixing etc
  • What is your release strategy? - release a feature when ready, or only when the whole development is complete?
  • How many developers you have!
Having more sandboxes can help keep multiple development streams separated and more manageble, but will introduce additional deployment overhead, so source control is key to this working. There are trade offs with both, there will be some developments where you can go either way, and in others where the choice is obviously suited to one.

Individual Sandboxes
  • 3-4 developers
  • Separate dev streams - e.g. bug fixing or features
  • Separate release dates
Single sandboxes
  • Small to medium builds with 1-3 developers
  • Single go-live date for all changes
  • Developers working in the same office - it is much easier to manage shared resources / changes that will impact all developers if they are work in the same office.
Thanks,
Richard.
Jay JanarthananJay Janarthanan
About 20 developers, 95% the code base is APEX. 
Pankaj_KatharPankaj_Kathar
Hi,

Can you please help me clear my few more questions!

Initially, where do we create developer users? 
In developer sandbox or in developer pro or in partial copy or in full copy sandbox?

Also is it considered as separate licence if developer is created and using more than one sandbox?