News for hackers. Stuff that matters.
Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by jrs95 on Wednesday October 04, 2017 @11:59AM (#15401444)
Agreed. I love Go, but a database is one of the things in the stack that ought to be as optimized as possible in my opinion. C++ still seems preferable in these types of applications. At the same time, if the underlying architecture is enough of an improvement over older systems, it's still an upgrade.
Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by zzzcpan on Wednesday October 04, 2017 @12:11PM (#15401533)
You can't optimize anything with C++ if your database is stuck waiting for consensus with nodes 100 ms away. Close to the metal and low level languages are really poor choices here, even Go is too low level for CP databases.
Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by ddorian43 on Wednesday October 04, 2017 @12:18PM (#15401581)
Yes, but you'll have lower overhead on each query/request and more concurrency ? For each query the bottleneck is the network which you can't fix, but you can fix the 2,3,etc bottlenecks which are inside 1 machine (cpu/ram/disk).
Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by jrs95 on Wednesday October 04, 2017 @03:37PM (#15403795)
Yeah...I'm not really aware of a higher level language that mystically makes networking faster. As far as I'm aware, the most efficient network protocols tend to be implemented at a low level, too.
Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by wiremine on Wednesday October 04, 2017 @12:59PM (#15401922)
> C++ still seems preferable in these types of applications

Agreed, but until there are some published performance metrics, I think it's an assumption more than a truth. Premature optimization...

Re:Avoid Vendor Lock-In Risk with Multi-Cloud Deployments by jrs95 on Wednesday October 04, 2017 @03:34PM (#15403756)
Well we already have metrics on what the languages themselves can do. And given that performance will definitely matter in this domain, it's not a premature optimization at all. A database isn't something that can be written easily enough to simply rewrite it in another language later as an optimization.