4 ms·
> No, because we didn’t change the team composition after our cloud exit. This has been my experience with my major enterprise company’s cloud transition as we
by addicted 3y ago
> No, because we didn’t change the team composition after our cloud exit.
This has been my experience with my major enterprise company’s cloud transition as well. The ops payroll has only grown since the transition. And our company had 4 major platforms before transitioning to the cloud and now only has 3.
I won’t deny the cloud doesn’t have any benefits. Distributing services and DBs geographically is much easier than with Colo for example. But really yhwts where the cloud benefits really lie. Since everyone is spending all their money building services for the cloud, that’s where innovation in tech lies right now (although whether we need more innovation is indeed arguable, and whether one benefits from being at the vanguard of innovation is also an open question).
- leroman 3y agoThis is where I see K8s fit in, future proofing and un-vendoe-locking (mostly). My own experience running on DO and moving to AWS (free credit ) while using DO S3 clone, managed pg and K8s, the move was rather straight forward..
- happymellon 3y ago> > No, because we didn’t change the team composition after our cloud exit. > This has been my experience with my major enterprise company’s cloud transition as well. Except in classic double speak they did, because they have hired an extra contracting company to look after all the hardware installation and maintenance.