I wonder why all the predominant RDBMSes are heavyweight connection based, and why this is presumably so hard to change. There's nothing in SQL that requires this to be the case, at least conceptually.
I had to do similar a month ago, around $20k as well. It was from my account at BofA to an account at a different bank. I did it all online, and it cost $10 and cleared the next day, so within 24 hours. I did this all online without talking to any person, though I did have to 2FA into my account.
I get that some banks might not be as competent yet, but signs look like they'll all get there in the end.
As a sibling comment has mentioned, there are high-skills immigration paths in the US, they just aren't very well known, and have a very high bar to clear. It's not great, but it does exist. I personally know 2 Indians who got their green card in a matter of months.
That said, the Canadian system, while definitely better than the US system, still isn't that great, and not something to model after. Specifically, it gives too much weight to credentialing, which is unfair in its own right, and still very much subject to gaming.
I personally believe in complete free movement of labor (which totally existed before, the current state of things is relatively young), but that seems politically infeasible around the world right now. Brexit is an example of even taking a step back from it. Maybe this will someday happen in my lifetime.
People keep saying that Node is async native, but the GC is global and synchronous, and that property will bite you on availability even at moderate traffic, i.e. sooner than you'd expect.
> I feel that if you make the best choice you can given the information you have, you've nothing to regret.
You did miss something. Trying to be a gymnast wasn't her choice, her mom made that choice for her when she was 3 years old. This is the story of a failure to be elite in the sports world, and coming to terms with a dream that was externally foisted onto her at a formative age that didn't get realized.
I don't think this situation applies to the scenarios most HN readers deal with. Your advice is a lot better for this crowd.
This is an informative and well written article, but seems incomplete in this day and age. In public cloud environments, network attached storage is far more prevalent, so the swap story may be different there (I honestly don't know though). Since the author works at Facebook, he probably lacks experience in this regard.
At small scale just go with Kinesis. The base semantics are pretty much the same between the two, and Kafka is terribly complex to run. The hosted Kafka solutions are too expensive for small scale.
Kinesis has a real auth story too, plus you can trigger Lambda functions off streams.