3 ms·

Developers waiting on the dev/sandbox environment for their turn, is such a frequent issue within our team specially when the sprint is about to end. This solut

Developers waiting on the dev/sandbox environment for their turn, is such a frequent issue within our team specially when the sprint is about to end. This solution really looks cool and will be trying this out tomorrow.I am sure our cloud team will be very much interested in this.

lucasfcosta 3y ago
Indeed, we've seen that happening very often. I lost count of how many times I've seen developers have a Slack or Discord channel to coordinate who's gonna using staging/dev and when. Please let me know if you need any help setting it up. We'd love to help in any way we can.
- cloverr20 3y ago
  One point i am curious about is the way you described you intend to make money, by providing a managed service. I am just thinking that if this service gets really liked by people, won't aws/gcp/azure create managed services out of this code and then it will be difficult for you to sell your services as most companies like to use the services their existing infrastructure is already on. Something similar to what happened with elasticsearch.
quickthrower2 3y ago
As an aside that is a downside of sprints. It creates pressure points like this. Another is QA testing all needing to be done on the final day.
anirudhrx 3y ago
This is an interesting issue that I've also seen across many companies - often even leading to low usage of these slow-to-bring-up environments. At relatively smaller scale, I can see physical infrastructure-based isolation being effective to solve it - with the stack coming up relatively quickly, but at larger scale (even 30+ microservices), I think an approach that uses logical / request tenancy is also worth considering - similar to https://www.uber.com/blog/simplifying-developer-testing-through-slate/ https://www.uber.com/blog/simplifying-developer-testing-thro....

3 ms·

Developers waiting on the dev/sandbox environment for their turn, is such a frequent issue within our team specially when the sprint is about to end. This solut

by cloverr20 3y ago

lucasfcosta 3y ago
Indeed, we've seen that happening very often. I lost count of how many times I've seen developers have a Slack or Discord channel to coordinate who's gonna using staging/dev and when. Please let me know if you need any help setting it up. We'd love to help in any way we can.
- cloverr20 3y ago
  One point i am curious about is the way you described you intend to make money, by providing a managed service. I am just thinking that if this service gets really liked by people, won't aws/gcp/azure create managed services out of this code and then it will be difficult for you to sell your services as most companies like to use the services their existing infrastructure is already on. Something similar to what happened with elasticsearch.
quickthrower2 3y ago
As an aside that is a downside of sprints. It creates pressure points like this. Another is QA testing all needing to be done on the final day.
anirudhrx 3y ago
This is an interesting issue that I've also seen across many companies - often even leading to low usage of these slow-to-bring-up environments. At relatively smaller scale, I can see physical infrastructure-based isolation being effective to solve it - with the stack coming up relatively quickly, but at larger scale (even 30+ microservices), I think an approach that uses logical / request tenancy is also worth considering - similar to https://www.uber.com/blog/simplifying-developer-testing-through-slate/ https://www.uber.com/blog/simplifying-developer-testing-thro....