I put a real search engine into a Lambda, so you only pay when you search
11–15 of 15 posts
Serverless gets a lot of hate for its name, but I have had so much success with it myself that I have moved on to its successor and have started developing for computerless architectures.
Re: I put a real search engine into a Lambda, so you only pay when you search
#12Earlier quoted context omitted.
https://aws.amazon.com/about-aws/whats-new/2020/12/aws-lambd... Is what you're talking about a new thing? Or respectfully, are you just wrong?
They probably have never requested service limit increase to unlock all of AWS.
If they had, they would know that it involves many weeks of arguing with support, of course
Re: I put a real search engine into a Lambda, so you only pay when you search
#13Great to see more love for using Lucene on Lambda via GraalVM native binaries! Explored that same idea few years back for my personal blog [1]. It worked pretty well, but I moved eventually away from Lambda as I wanted to close down my personal AWS account. One thing I always meant to explore was embedding the (in my case small) Lucene index directly into the binary image using Lucene's RAMDirectory via Quarkus' bytecode recording machinery, but I never got to it.
[1] https://www.morling.dev/blog/how-i-built-a-serverless-search...
Re: I put a real search engine into a Lambda, so you only pay when you search
#14Re: I put a real search engine into a Lambda, so you only pay when you search
#15Serverless gets a lot of hate for its name, but I have had so much success with it myself that I have moved on to its successor and have started developing for computerless architectures.
It is the next level of abstraction for sure. Cloudflare seems to be making the biggest strides in also abstracting regions and the geolocation of the data, but I’m not super familiar with their offerings.