010a

Dynamo might fill this need for you; you can provision a 1/1 table for less than a dollar per month and just put everything in it. Dynamo will bank some provisioned throughput for you to allow bursting, and the client apis all implement exponential backoff in the event of a throttle, so a 1/1 table isn't nearly as scary as you might initially think.

Of course, then you're using Dynamo.

Yup, last I checked you can create GKE clusters as small as 1 node.

That's a terrible argument considering Hyper gives you no fine-grained control over instance types. You just get a linearly-increasing allocation of CPU cores and RAM.

There are ways to organize your lambdas to get around the 300s timeout. In classic AWS fashion... you just need to give them more money.

Look for ways to divide-and-conquer your lambdas into smaller parts. If you need to run some logic for every record in some table, give N records to a single lambda (where N is some small number which doesn't make the lambda take anywhere close to 300s).

You can orchestrate this workflow with several different AWS tools which exist all over the spectrum of cost and ease-of-use.

Easiest is definitely just having the master lambda directly invoke the other lambdas with InvocationType:Event.

SNS is another easy option. Lambda(master)->SNS(per N records)->Lambda(splinter). Downside is that you'll probably completely blast out your global AWS concurrent function execution limit pretty quickly because you have no control over how quickly SNS will trigger your functions.

Kinesis is a more powerful option. SQS also has potential, but you can't directly trigger a Lambda from SQS. One pattern I've seen used is to have a CWEvents cron trigger a lambda every M seconds to read N records from SQS. Depending on how consistent your workload is, this might make sense because it gives you really fine-grained control over that ratio between "how quickly will my jobs be processed" and "am I approaching my AWS global account limits". But if your jobs are really disparate you'd be invoking lambdas all day to do a whole bunch of nothing 90% of the time.

Lambda is already limited enough when it comes to how you can write the functions. I'm not even sure how you'd write a generic JS/Python/Java function on DPL, unless its got some functionality which I'm not aware of (through a custom shell command bootstrapping your language environment maybe?).

Please fix it and get these products back on the market so I can get my order in.

The Blade Pro is priced at $3700, which puts it in another class incomparable to the MBP.

I was really sad to see the new bars get pulled. Hopefully they get the issues sorted out and get those back on the market; I'll happily be the first to renew my subscription plan.

You could say the same thing for removing serial ports, or floppy drives, or CD drives. People used them when Apple got rid of them. People whined. Apple still did it. We don't miss them anymore.

Its possible Apple could go too far, but I don't think its fair to say Apple did anything wrong _yet_. They're always early on removing this stuff, but they've never been wrong. Literally never.

Curious: Does the usage of CoreOS replace Docker OSX's virtualbox linux VM it uses? And if not, is there any reason why KubeSolo couldn't be designed to run on that VM, just to save resources?

I would take an 8% raise. If I'm working from home, that is one less capital expense the company has to invest in me, in the form of office space and office perks. I would not volunteer to work from home if it had any chance of decreasing my productivity. As such, that is more money in the company's pocket that they should reinvest back into the employees so they have the option of replicating office perks back at home (equipment, coffee, snacks, things like that).

Most of those points are fearmongering, outdated, opinions, or improperly cited. Every database has problems. Mongo has more than most. But I honestly think people dislike it so vehemently primarily because they've monetized so strongly.

Its not an $80 VR headset. The thing that goes around your head is $80, but the expensive part is that phone which you put in the front, which needs a 1440p display (minimum) to avoid the screen-door effect.

iPhone 7+ is a much better comparison considering the size of the first two devices.

On one hand, normal GPU mining is practically never efficient with respect to the cost of electricity. Even in a hyper-efficient datacenter, Bitcoin mining is now dominated by thousands of ASIC miners who are running hardware a hundredth the cost of GPUs at 10x+ performance.

But on the other hand, these machines aren't just sitting there powered off when they aren't provisioned. They have to keep them warm so they provision ultra quick.

So maybe there is some level of mining they could accomplish with their "idle" cycles, given the efficiency of the datacenter, the power of their GPUs, and the price of Bitcoin, which would be profitable. I don't know.

Don't confuse Node with Javascript. Node and the browser are where all the async behavior comes from, not JS. Specifically; if you've ever done any backend coding in Meteor, there is practically no async behavior at all.

But I do agree: Sometimes I see people try to push Node/Express as a good choice for teaching basic APIs. Its not the worst choice, but its startling how easy it is to forget how insanely confusing async callbacks are for new devs.

You should check out kops. It seems to me like its one level of abstraction above kubeadm, and makes creating clusters on AWS _ridiculously_ easy (one command).

Are you aware how much 0.25% of $800 billion dollars is? Now, go ahead and complain about a $60M compensation.

The difference between $60k and $60M, for a fund nearly a trillion dollars large, is worth it if that person worth $60M can eek out even a few extra basis points in returns. Despite what many people believe, there are those out there who have an eye for value, and _can_ pick stocks.

Are you forgetting about dividends?

Best solution is a dedicated secret management tool. K8S has secret capabilities built in, or something like Hashicorp Vault.

Alternatively, I've used something as simple as DynamoDB to distribute config information and secrets to services.

Hosting yourself is still way cheaper. But services like S3 do get cheaper. When S3 was released in 2006, it cost $0.150/gb*month. That price underwent a half-dozen or so cuts every couple years to reach its current price of $0.03.

Its actually been that price for about 2.5 years now. With competition from Google, Microsoft, and Backblaze, its possible we could see a push toward even cheaper prices before too long.

As for security, S3 does support SSE at rest with a user-provided encryption key. So you're good to go there.

Agreed. I keep a server at home, not because I want to but because I have to. The cost of cloud storage and compute, relative to what you can field in your closet, is inordinate. You do pay the premium for not managing it yourself.

Its my hunch that the statement you quote is just simply wrong. If you're keeping a computer at home that is doing something valuable enough to keep it around, it should valuable enough to you that there has to be _some_ price cheap enough, and _some_ capabilities good enough, that the cloud makes sense. The exception to this is, of course, the hobbyists and the tinfoil hatters.

Fundamentally, it is fewer things that I _have_ to trust. The shim which defines an image should be much easier to grok than the entire application.

GKE/Kubernetes does fill that requirement; its not as simple as GAE, but its one step closer to bare metal.

Am I insane, or are you and the commentators below unknowingly describing Terraform?

https://www.terraform.io/

Oh yeah, I think I remember the FDIC doing something similar to this.

And it adds nothing to the conversation, and has spawned an entire subthread of comments like ours which also adds nothing to the conversations. Its exactly the type of comment that should be banned from HN.

I've been heavily using it since what must have been early closed beta, and cannot recall ever having this issue. Might be something that isn't quite so widespread.

Cloud PubSub is also missing, which I've always heard is one of the better parts of Google's cloud offerings.