News for hackers. Stuff that matters.
Re:Traits of Serverless Architecture by closeparen on Monday August 19, 2019 @10:21AM (#20737968)
> The same issues and solutions with any micro-service implementation. The solution usually being a common logging infrastructure.

A mature service mesh will let privileged users get inside containers to attach profilers and debuggers, manually as needed or systematically through performance monitoring tools, in situ or with temporary exclusion from the load balancer pool. It's also sometimes necessary to correlate issues with host-level metrics to understand weirder bottlenecks and tail latency issues.

> it rarely happens

The credible threat of it happening keeps prices low enough to make it unnecessary.

Re:Traits of Serverless Architecture by scarface74 on Monday August 19, 2019 @10:45AM (#20738181)
The credible threat of it happening keeps prices low enough to make it unnecessary.

As far as vendor lock in, in general not just with respect to the cloud, there are so many path dependencies and the risk of disruption versus the reward is so rarely worth it, it hardly ever happens.

How much would Oracle or Microsoft have to raise their prices on their database products for instance to make it worthwhile for a large enterprise company to move away from them to an open source alternative?

Re:Traits of Serverless Architecture by wstrange on Monday August 19, 2019 @01:22PM (#20739686)
A lot of CIOs would dearly love to move away from Oracle. The cost of rewriting software that was not designed to be portable is immense. Oracle knows this, and keeps the pain just below the threshold where porting to postgres or mysql is cost effective.

I agree with the general sentiment that optimizing for extreme portability does not make sense- but there is a balance that needs to be struck. Designing your apps to be relatively SQL agnostic, or at least isolating those dependencies, makes a lot of sense.

Re:Traits of Serverless Architecture by scarface74 on Monday August 19, 2019 @02:45PM (#20740526)
And even if you do have a policy of “designing your apps to be SQL agnostic” and you have had that policy for 5 years over dozens of apps. Would you trust your policy enough that you would change your connection string from pointing to Oracle to pointing to MySQL and hope everything would work?

What about all of the programs that you used that depended on Oracle specific drivers. Even in a perfect world where everything was using standard SQL, would the regression testing and migrations be something you would want to tackle as a CTO? Would you be willing to take the reputational risks of something going wrong?