News for hackers. Stuff that matters.
Re:Algorithms as Microservices by sixdimensional on Wednesday March 30, 2016 @09:16PM (#11394337)
Disregarding the article, I sort of disagree with your comment too, maybe you are oversimplifying it too much. Or maybe because it's kind of a chicken and the egg kind of problem - which came first, the algorithm or the data.

Sure, generic sort algorithms come "off-the-shelf", but that is not true for all algorithms. Not all algorithms are public knowledge if they are patented, proprietary, or restricted in use/distribution.

You really need both - algorithms and data, right? And systems of execution for algorithms... and networks to interconnect the systems... and potentially humans to review the algorithm's output... and..... and... and..

I think the key is, algorithms can also represent embedded capabilities (information? knowledge? insight? not sure what to call it) generated from data. I mean, look at a RNN - the values/weights/etc. calculated inside the model are calculated from observations/training on the data. Once you disconnect the algorithm from the data itself, the algorithm alone now has embedded value without the data, potentially enormous.

Or, expert/rule-based systems which contain algorithms explicitly designed to embed human knowledge - those algorithms may not even be trained on actual data, they are simply a simplified expression of codified human knowledge.

If you go one step further and try to make some assumption that the way our brains work is by codifying inputs we receive into algorithmic models... and then using those algorithms to calculate based on new inputs from the environment... we can't keep all the data in our heads, but we can probably keep more algorithms than data.

Maybe I'm being too philosophical, but in my opinion, it's not just about the data.

Re:Algorithms as Microservices by cgio on Thursday March 31, 2016 @03:55AM (#11395641)
Very interesting viewpoint. Any algorithm can be replaced by data and a lookup (e.g. Rainbow or multiplication tables.) On the opposite direction, the claim that any data can be replaced by an algorithm is indeed deeply philosophical (c.f. Materialism and free will)
Re:Algorithms as Microservices by TeMPOraL on Thursday March 31, 2016 @07:11AM (#11396280)
If we want to go deeply philosophical, then fundamentally data and algorithms are the same thing anyway. Whether you interpret something as data or as code depends only on the angle you're approaching a problem at.
Re:Algorithms as Microservices by Natanael_L on Thursday March 31, 2016 @07:41AM (#11396396)
From the perspective of a Turing machine, they're the exact same thing. We just created abstractions to separate them. And from the perspective of physics, you've just got yourself yet another isomorphic transformation of the above mentioned Turing machine, so still the same.
Re:Algorithms as Microservices by collyw on Thursday March 31, 2016 @09:00AM (#11396789)
Have you got an algorithm to produce my production database?

Philosophically you can reduce them to the same thing, but practically speaking you wouldn't really want to.