Recent submissions

Comment · 6 years ago
Thanks for sharing, I enjoyed reading your article! Very actionable advice.
Comment · 7 years ago
Worked for me on Linux, didn't even require a restart (some addons just reappeared immediately). Using Firefox from Ubuntu package management.
Comment · 9 years ago
FYI the underlying resource leak has been fixed permanently.
Comment · 9 years ago
Thanks for reporting this! We had an issue with one of the EC2 instances used behind Portal which led to a 500-response rate within the last 5 hours of around 6% (575 responses were affected in total). The instance has just been replaced.

I'll investigate and hopefully fix the underlying issue within the day.

Comment · 9 years ago
Thanks for reporting this! We had an issue with one of the EC2 instances used behind Portal which led to a 500-response rate within the last 5 hours of around 6% (575 responses were affected in total). The instance has just been replaced.

I'll investigate and hopefully fix the underlying issue within the day.

Comment · 9 years ago
Hey there, thanks for the feedback!

I know the website is not perfect yet (and we're not looking for people to buy yet, maybe that should be clearer?), it would be interesting though what in particular you're missing?

Regarding DNS, I'm a bit unsure what you mean. You point your own domain to our servers via a CNAME. SSL can be enabled as well (via LetsEncrypt), the certificate gets generated automatically via a DNS TXT record or, if you've pointed the domain over to us already, without any effort on your side. Of course you can test your setup before changing any DNS entries by using the *.portal.lambdacult.com subdomain we provide you. Load-balancing is done via ELB, not on the DNS level.

Right now, all Portal is doing is to call your Lambda function and returning its response over HTTP(S) - no rate limiting or any other extra features. Those will come as people (like you) try out the service and request those features, everything is possible :-) It's certainly interesting for us to hear that you consider IP-based rate limiting the #1 missing feature from API Gateway, might be possible soon! ;-)

The AMI idea is certainly interesting, but our goal is to provide a no-brainer service that doesn't need any setup or scaling. I can see this solution work well for small APIs, but don't you want the same flexibility and scalability as you already get with Lambda? Isn't that the great advantage over "traditional" server-based infrastructure? What happens if you get featured on the App Store over night? Also don't underestimate the necessary overhead for monitoring, outages, software updates, EC2 instances being shutdown, etc. - probably easier to manage over a service than over customer-owned EC2 instances.

Regarding screenshots, why don't you just try it out? It's free for now (and hopefully simple), let me know if it takes longer than expected to setup :-)

Comment · 9 years ago
Comment · 9 years ago
Comment · 10 years ago
Comment · 10 years ago
Comment · 10 years ago
Comment · 10 years ago
Comment · 10 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton