4 ms·

I get where you are coming from, but Lucene is a building block, a library and cannot be immediately used as a valuable service. ES can be used by quite high le

I get where you are coming from, but Lucene is a building block, a library and cannot be immediately used as a valuable service. ES can be used by quite high level developers to implement scalable solutions. Building blocks and libraries offering convenience are not as valuable on its own than solutions that offer some quite immediate value at a reasonably high level. Even if from an abstract view both still require developers as users the applicability is quite different. Amazon cannot 'host' lucene as a service per se. Services vs Libraries

geezerjay 7y ago
> I get where you are coming from, but Lucene is a building block, a library and cannot be immediately used as a valuable service. ES can be used by quite high level developers to implement scalable solutions. Your argument makes no sense. Even if we accept the thesis that building block components are up for grabs because they cannot be immediately used as valuable services... Well, neither can services. You need to design a system architecture, figure out how and if a component plays a role, pick a component, config the component, setup a deployment ans scaling strategy, config and integrate metrics and health checks, ingest data, monitor the service, etc etc etc. And if we actually want to make an objective comparison between libraries and services... Well, in the end they are all components of a larger system. So, obviously there is no objective distinction. There's only intellectual property and companies being hypocrite wanting to have their cake and eating it too. They can't get it both ways.