3 ms·

Came here to dump a similar list, but bravo this covers a lot. As for Coherence: Sounds great. I see a future where this makes so much sense - managing distrib

Came here to dump a similar list, but bravo this covers a lot. As for Coherence: Sounds great. I see a future where this makes so much sense - managing distributed dev teams with a fully managed env like this seems like one of the obvious end-game outcomes. Prospect questions: will it run off-Coherence? i.e. will I have the option to spin up the pieces myself if the startup powering this good idea gets "incredible-journeyed" or otherwise goes away? You mention running "in your own cloud". How open source is this stack? Obviously keeping your core secret sauce secret has a lot of merit, just a shout from the void about a potential (but not insurmountable) objection. (sorry if this is covered elsewhere, I read your announcement and browsed your site but didn't get too deep)

zoomzoom 4y ago
Thanks! As far as business continuity for the end of our journey, that’s one of the main reasons we believe so strongly in running in your own cloud (along with extensibility, cost and compliance). I don’t believe that this means we need to be open source - it’s not on our roadmap to do that. Our vision is to operate your control plane and configuration layer, while your customer-facing apps and data remain 100% in your control. If we are spinning down, our promise would be to give you some client-side tooling to replace the control plane, but even if we don’t keep that promise, you’d be able to figure it out on your own and nothing would affect your running apps/data. In the end we’re just configuring cloud services on your behalf and you could go back to doing that with terraform/pulumi/etc yourself (as you’d have to do today without our service).