Still super disappointing though, and yet another reason why trying to build a better search engine on top of someone else's tech is a non-starter.
Still super disappointing though, and yet another reason why trying to build a better search engine on top of someone else's tech is a non-starter.
If there's a market for alternative search engines out there, AWS is already serving so much of the web that Amazon should really provide crawling and basic indexing (for a fee, of course) so it's done once for everyone, with Amazon Lambda processing to allow search engines to customize their indexing. I'm not sure if it would make them much money, but it makes more sense to start up a search engine on AWS using Amazon's crawl and basic indexing vs. using a search engine competitor's crawl and indexing.
Awful for competition and whatnot.
As it stands, if you want to bootstrap your own search engine, you need to base your search engine on either Google or Bing's index, or perform the herculean task of making your own crawler+indexer+search engine. If Amazon can commoditize the back end, and let AWS-hosted search engines provide differentiators late in the indexing pipeline and on the search/serving side, I think we'd see more niche search engines spring up.
Amazon is a weirdly plausible competitor to Google. They have a surprisingly robust ad business, and obviously AWS.
https://www.cnbc.com/2022/02/03/amazon-has-a-31-billion-a-ye...
The crawling and initial indexing stages need a lot of scaling and performance tuning work, which is a core competency for the AWS engineers. Furthermore, essentially zero people say "I want to build a startup around my new crawl scheduling idea, but it's too time consuming and expensive to write the rest of the search engine." Many more people say "I have a new idea for ranking" or "I have a new idea for content extraction, but it's too expensive and time-consuming to write the rest of a search engine".
Google and Bing already expose "custom search engines" which are basically just filters on top of their search engines. I'm talking about something similar, but much deeper customization.
Also, I was at Goldman when Google Search Appliance was EoL'd. GS had plenty of internal content that needed to be indexed, absolutely needed to be kept private, and wasn't well indexed by any of the replacements GS evaluated. For companies that keep lots of documents in AWS storage, it would be good to open up the space for Google Search Appliance replacements. Amazon could write their own, but given that Google abandoned the space, the profit margins aren't great for a huge company. However, creating a search ecosystem within the AWS ecosystem makes the AWS ecosystem more attractive. Maybe forgoing the search profits and inviting in search providers would be a net win in selling more AWS compute and storage.
Maybe that's the real problem. There have been some recent articles on HN about how "search is broken" and maybe this article falls under that. Because what really gets me is that there is plenty of legit content on "pirate sites" and blocking them completely cuts off that content.