4 ms·
This is where I usually draw the line at the "everything is a service" world view. It is much better to provide this as a library than as a service, particularl
by mattmcknight 17y ago
This is where I usually draw the line at the "everything is a service" world view. It is much better to provide this as a library than as a service, particularly algorithms that run across large data sets.
However, the exception I see to this is a service that applies the algorithm across a large dataset that is owned by the service. An example of this is geocoding, where you probably don't want to store the addresses of everyone in the world in your database, but it is easy to reach out to a range of providers to get latitude longitude for your address.
- keefe 17y agoI think the other area where AAS makes sense is in distributed algorithms, there is a genuinely large amount of work in writing parallel versions of algorithms and they also require clusters.
- jacabado 17y agoGoogle Wave?
- keefe 17y agodo you have any reference on how distributed algos and wave mix? I'm a little behind the curve in understanding wave but I can't see the link here.
- jacabado 17y agoGoogle Wave as a platform is a huge step in distributed computing abstraction. If you ever try/tried to implement any app on top of distributed algo you will value the wave possibilities!
- akronim 17y agoAt least if it's a library you're not really increasing your chance of failure. Whereas as you add external dependencies, the odds of one of them being down and taking your service with it increases. So you had better thinking about how you handle failure situations gracefully and so on, so the service you call had better be doing something special (e.g. giving you access to some huge dataset) to make it worth that additional complexity.