astuyvenberg

It's the exact same play as Yelp - once they grew out of the community review forum stage, they turn to extortion to make it profitable.

Basically anything and everything that I can surmise will complete within 15 minutes.

I do not spend that much on Amazon, but have encountered fraudulent products (shipped & sold by 3rd party). Confirmation bias on both sides aside, I agree with the top comment. Anything I really care about, I buy in store somewhere which matches prices.

I mean not correct in the literal sense. It's not about reliability nor simplicity nor testability - the code is wrong. It has a bug. The code is written without understanding that lambda containers can be re-used, thus, it's exhausting a finite resource unintentionally.

You handle the "timed out right as next request comes in" case by memoizing the connection in a variable and checking if it's null in the handler. If it is, re-establish the connection.

Lambda may not be a magic reliability wand, you definitely still need to manage downstream pressure. That said:

> The code creates a MySQL connection during each invocation.

This is not a correct implementation for Lambda.

You shouldn't recreate a connection on every invocation. Instead, create your connection outside of your handler code. Then each invocation of a warm container will re-use the same handler. (1)

This will help cut down on cold start time, as well as help manage running out of connections.

You should limit your maximum number of concurrent invocations to be equal to the limit of your database threadpool. This is all in their documentation, as well as several blog posts. (2, 3, 4)

[1] https://docs.aws.amazon.com/lambda/latest/dg/services-rds-tu...

[2] https://www.jeremydaly.com/reuse-database-connections-aws-la...

[3] https://medium.com/faun/reusing-connections-lambda-functions...

It would be challenging to do so - the rule states that full time students can only enroll in one full-time online class.

Learning basic *nix commands like sed, awk, and grep has helped me so much. I still frequently google/manpage them, but I often find myself thinking "I can do this with X in just a few seconds!"

This is great! One thing that many HN-ers may not know is that Amazon Prime users get a free subscription to give to anyone on Twitch.

It'd be neat if there was a button here that would allow a user to subscribe with Prime; I'm sure these streamers would love that.

That's not entirely true anymore. Several third party services offer debugging experiences.

Are there issues running java using serverless? I've worked with a number of enterprises using lambda and java. Seems to be fine ¯\_(ツ)_/¯ YMMV

I develop in the cloud!

Serverless Framework deploys are now less than three seconds. It's almost exactly like `run watch` now!

I deploy to a dev AWS account, then a staging AWS account, and then promote to prod out of github.

Check it out: https://github.com/serverless-components/

Those choices were made by AWS, unfortunately: https://aws.amazon.com/blogs/compute/announcing-http-apis-fo...

Oh absolutely! I'm commenting that fuel economy is likely not the deciding factor for people considering purchasing a Tesla vs a Camry.

In fact, I can't imagine many car purchase decisions boil down to "Camry vs Model 3".

¯\_(ツ)_/¯ and?

I don't think fuel economy is the reason people purchase a Tesla. The Model 3 beats the Camry on cool-points alone.

This seems like a perfect solution for a portfolio, blog, or new project. I like that it's open-source, lightweight, and has a self-hosted option!

Elevator pitch from `rational.markdown`

GoatCounter aims to give meaningful privacy-friendly web analytics for business purposes, while still staying usable for non-technical users to use on personal websites. The choices that currently exist are between freely hosted but with problematic privacy (Google Analytics), hosting your own complex software or paying $19/month (Matomo), or extremely simplistic "vanity statistics" (Fathom).

GoatCounter attempts to strike a good balance between various interests. Major features include a free hosted version so people can easily add analytics to their personal website, an easy to run hosted option, an intuitive user interface, and meaningful statistics that go beyond "vanity stats" but still respect your users' privacy.

But the person earning 150% more than _them_ isn't purchasing a Tesla. It's a Lamborghini or a Bugatti. It's not a 3br home in SF - it's a summer home in Napa, or a chalet in Tahoe.

The person earning 150% more than _them_ is coveting the latest Bell Jetranger, or Gulfstream G700.

The obsession for more is the same at all levels.

That's precisely my point regarding the rat race - what is one trying to catch up to? Is there economic or social anxiety at 350k/yr which evaporates at 400k/yr?

This post also resonated with me, especially the quote from /r/cscareerquestions

> Got an awesome internship at an interesting company? Well, it wasn’t FAANG, so who cares? Got a FAANG internship? Well it wasn’t one of the good FAANGs, so if you really think about it, you really didn’t accomplish anything. Got into a “Good FAANG”? Well, the other intern works on his own startup idea when he goes home. Why aren’t you working on your startup idea? Do you even have a startup idea? Are you even trying?

It's absolutely not limited to new engineers. Take a look at the replies to the "Levels.fyi Annual Report" here on HN.

> You can't move to the US/SF/NYC? Good luck eeking out a living. You didn't get an offer from a FAANG? Well, you don't really belong in the bay area then. You got a FAANG offer but you didn't negotiate 400k+ total comp? Good luck ever getting a raise. You made it to the top of your salary band? Well, they'll never move you up, better plan your exit now.

The tech rat race mentality is very real and very pervasive.

I'd strongly disagree with that assessment after building on serverless platforms full time for 9 months. I'll never go back to a server-full backend.

Yes, I believe so. We've just passed the peak of inflated expectations on the technology hype curve, and the comments on HN reflect this.

But in general - Do people manually deploy MySQL, Postgres, or MariaDB on EC2 servers? No, (most) people use RDS. The servers are still there, but the management is less.

Do people manually deploy RabbitMQ? No, (most) people use SQS.

Cloud providers have been working out of the same playbook for years - provide low-level compute, watch what people build, and create managed services which solve common use cases. Developers love these services, because it's less infrastructure to be on call for, and they can build products faster.

Lambda and Serverless represents the inevitable conclusion of the natural evolution of the cloud. Parts of it are still painful, but undoubtably it's getting easier and more capable.

Finally, this has been a long time coming. Connecting to existing RDS instances from lambda functions has been a pain for users looking to adopt serverless tech into their existing applications.

I've been using Brave for several months. It's exactly what I wanted - A faster, chromium-based browser with sensible, privacy-conscious defaults.

I don't personally mind the Chrome Web Store default.