I'm in the view of starting a small business and among the requirements there's a... programmable search engine w/ APIs

I previously relied upon Yahoo Boss API while experimenting with YaCy alongside for testing the grounds for a possible transition. Last month Yahoo triplicated its API pricing so it's become more important to properly test YaCy capabilities on suitable hardware and decide for a possible move.

For the sake of the hype, here's the hardware

These are:

Motherboard: dual-CPU 771 Supermicro

RAM: 32GB ECC fully-buffered DDR2 (in picture: 24GB by the right box, 16GB mounted on MB. Final configuration will have 32GB)

All will be assembled in a week when the Xeon's arrive.The existing YaCy virtual machine (currently running on a smaller server) will run under OpenVZ and will be moved to this server soon as it's assembled.

The target documents count is 100M and the main sources for crawling will be Amazon, Newegg and Best Buy. The node publicly shares its indexes and supports the global community network

After several unfulfilled bug reports and two data loss which corrupted a 210 GB index, I'm glad I move away and repurpose my hardware for a custom crawler & indexer.After all, today YaCy seems to be a glory of the past, mostly unmaintained, with bugs and plain missing features keeping it unsuitable for professional use, and probably it's remained nothing more than an exploit to fill up someone's resume to inflate wasted years.

For the smart one, wondering why after 11 years of development YaCy is a failure with less than 1000 users, here might lie some clues; maybe the unsuccess of YaCy was not caused by one user walking away, but by thousands of missed users sharing the same point of view as mine. But you demonstrated to not being able to interpret this. So, good luck, if possible at all.