But the problem is one of specialization. Surely there are other APIs out there that specialize in particular aspects of what the supermarket is providing. For example, it this AAS business is providing distance algos as well as image algos, there must be Geo Businesses and Image Businesses that can provide higher quality given their specialization.
Algorithms as a Service
11–20 of 30 posts
Re: Algorithms as a Service
#12The database of localities and all associated information is not only huge, it's changing literally every day and thus should be constantly kept up to date. Definitely a good candidate for the hosted service scheme.
Re: Algorithms as a Service
#13I once tried to build a web site with content tied to locations down to the smallest towns in all countries, and I found it hard to get everything right. So I think it would be interesting to have maps, all kinds of geographical information along with some related algorithms "for lease": e.g. find the nearest city to a given location, IP-to-location, address format for a given country for building proper entry forms,…
Re: Algorithms as a Service
#14Author is under impression that implementing algorithms is hard. Real problem is analysing and understanding the problem, implementation of the standard algorithms is the easiest part. If your problem is common enough to have its implementation as service, it's very likely there is free library anyway.
Seriously, ask Dijkstra's shortest path at IOI (high school informatics olympiad), I'd bet half of students would get it 100% correct under an hour.
Re: Algorithms as a Service
#15 This will cause a total nerdgasm, and nobody will buy it.
There is an inverse correlation for how much abstraction is between our product and our customers' bottom-lines and how quickly they're willing to open their wallets. The proposed notion here is taking a couple steps further away from providing an end-to-end solution to a problem. Geeks love that kind of stuff. It's hard to get people to pay for it.Re: Algorithms as a Service
#16A big problem for this would be the transfer of data to and from the API. Imagine an algo to analyze gigabytes or terabytes of data. Also, protection of the data as it is being transfered, stored, and analyzed is an issue. This is both data integrity and also protection for privacy or confidentiality reasons.
Re: Algorithms as a Service
#17Earlier quoted context omitted.
I was thinking that as I was typing my comment. Another solution, which S3 uses, is to ship hard disks by courrier. I guess the real metric here is cost per GB transfered in a unit time, say $/GB-hr.
At what point does it become ridiculous to move the data, which may be measured in TB or PB, when the algorithm itself would be measured in KB or MB?
Re: Algorithms as a Service
#18Re: Algorithms as a Service
#19It's worked pretty decently, but we keep it internal because we just don't have the compute resources to offer things like SAT-solving or logic programming or planning as a service to the general public.