2 ms·
I have taken projects of significance to me from MySQL to Postgres. It was certainly a short-term cost but the upside justified it. (first class IPv6 objects, J
by ggm 4y ago
I have taken projects of significance to me from MySQL to Postgres. It was certainly a short-term cost but the upside justified it. (first class IPv6 objects, JSON)
I have tried to do the language port thing Several times. I never succeeded in bringing others with me (Perl to python) but that said, others I work with have done Perl -> Java and C -> Perl -> C and Perl -> Java -> Rust so I think language may be one of the "tractable" problems in many cases.
We tried AWS for low-end k8s and it was too complex. GCP/GKE was just better presented. It has the same complexity but gcloud/kubectl seemed to work "better" for us, which led directly to helm outcomes we liked. I think the AWS experience we had could be called at best "toe in the water" maybe try before you buy works?
The one which has proved the most sticky is VM/Cloud provider, for routing. If you are in a world which cares about BGP, the one you pick that works, you probably stay with. We partnered with CloudFlare for some stuff, and Linode for other stuff. I do wish at times we'd gone digitalocean, or fastly, or even Akamai (which is behind Linode apparently) -but the BGP surface we have, is the one we want to maintain because we understand it. Maybe it's not that different to AWS vs Azure vs GCP.
Also DNS provider. You tend to stick to the underlying NS and related registrar inside your chosen namespace registry.
Also Cryptography TA. Well.. once you move to letsencrypt you stop moving I guess.
I do think the DNA baked in early tends to persist. If you do monolithic solutions, you aren't walking to microservices without a huge conversation. If you went XML/SOAP you would be asking the cost/benefit of JSON given JSON and XML can be considered strictly equivalent for data content. If you went apache and mod_<something> then moving to nginx or caddy incurs massive cost for what?
But if you wind up behind dead/legacy platform (apache/mod_python) that can suck.
Even just moving off wordpress costs.
Moving off one CI to another CI costs. I don't know any CI which works all the time, they all seem to incur opex burdens
We moved self-hosted gitlab to k8s gitlab to k8s in GCP gitlab and that went ok. Maybe when the abstraction moves to the package, change in how the package is presented matters less?