Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
maslam
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
31.
▲
by
maslam
8y ago
Yes exactly. A rational response to this is to delete your FB account.
32.
▲
by
maslam
8y ago
Or Snowflake
33.
▲
by
maslam
8y ago
Thank you. Kudos for doing the right thing :)
34.
▲
by
maslam
8y ago
Joe's a really nice guy. Have you ever worked with him or been in a meeting with him? Sorry, this type of ad-hominem attack really does not belong here.
35.
▲
by
maslam
9y ago
"Third party vendor". Is this Qubole? If so, would be nice to give him an Internet high-five by naming them :)
36.
▲
by
maslam
9y ago
Someone's trying to be GDPR compliant :D
37.
▲
by
maslam
9y ago
Spelling error in video is a big red flag for me. "Expidited" should be "expedited".
38.
▲
by
maslam
9y ago
It's a thing in Seattle. One of my friends lives in a wonderful neighborhood in South Bellevue. Multi million dollar homes. At least 40% sitting empty.
39.
▲
by
maslam
9y ago
Be oh so careful. We ran into issues with alpine node images that would only show up in minimal images like that. Switched to Debian and never looked back.
40.
▲
by
maslam
9y ago
We use urlbox.io and are really happy with it. Don't recommend building this yourself.
41.
▲
by
maslam
10y ago
(product person at Appuri in Seattle) We work with customer data, so lots of time-series. We use SQL for exploration and feature engineering. Model-building happens inside a Docker container that runs on ECS. Scores and predictions are inse
42.
▲
by
maslam
10y ago
Yes
43.
▲
by
maslam
10y ago
This, SOOO much this! Please don't enter the morass that is Hadoop / Hive / Presto / Spark [esp. Spark] unless you really, really need to. Redshift sounds really good for your needs.
44.
▲
by
maslam
10y ago
George - fan of Fivetran. What, in your opinion, are common cases where customers choose BQ over Redshift? Or is it really a function of which cloud you're on?
45.
▲
by
maslam
10y ago
We use Amazon Redshift a lot. The biggest pain point is its lack of elasticity and strong coupling between compute and storage. You can see this pattern emerging in warehouses from Azure and Snowflake. I fear that Redshift will never get th
46.
▲
by
maslam
10y ago
This was exactly my reaction. The tips around Amazon Redshift were spot-on including a few obscure-but-critical ones e.g. the one about many small tables taking up a ton of disk space!
47.
▲
NPS is bad and you should feel bad
(appuri.com)
5 points
by
maslam
10y ago
|
0 comments
48.
▲
by
maslam
10y ago
@rjurney - we started with ECS right around when DCOS was coming out of alpha (?). Anyway, it looks slick!
49.
▲
by
maslam
10y ago
Yes. This is pretty much what we saw.
50.
▲
by
maslam
10y ago
@SteveWatson - thanks for reporting, should be fixed now.
51.
▲
by
maslam
10y ago
@yeukhon - for the performance you get, Redshift is quite affordable. Keep in mind it's an always-on data warehouse - there's really no way to make it much cheaper than AWS does because they're incurring compute costs. What a
52.
▲
by
maslam
10y ago
That's a great blog post. Thanks for sharing!
53.
▲
by
maslam
10y ago
>Another annoying thing not mentioned in the article is that the default AMI used for ECS is not at all production ready, you really have to bake your own images if you want something usable. I suppose this is maybe because there's
54.
▲
by
maslam
10y ago
Thank you!
55.
▲
by
maslam
10y ago
@madeofpalk, I haven't seen that, actually. I'll look into it.
56.
▲
by
maslam
10y ago
There are lots of cases where AWS builds services that are not revolutionary but purely evolutionary. Consider Amazon Redshift, their data warehouse. You would _think_ Redshift, with its poor elasticity and tight coupling of compute and sto
57.
▲
by
maslam
10y ago
Thanks @advisedwang. We're looking into it.
58.
▲
by
maslam
10y ago
HN, I'm a co-founder at Appuri. Happy to answer questions! PS: We LOVE most AWS services like Amazon Redshift. Just not ECS ;)
59.
▲
Our nightmare on Amazon ECS
(appuri.com)
270 points
by
maslam
10y ago
|
127 comments
60.
▲
by
maslam
10y ago
I have vivid memories of working on Longhorn as an intern. It was an incredibly ambitious project - rewrite of the "filesystem" (really, a relational object store!), driver framework and display stack to name a few. The project fa
More ›