Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
flounder3
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
flounder3
4y ago
I can truly empathize. I’ve never wasted so much of my time on a vendor. It’s infuriating and certainly not worth the personal stress and agony. It shouldn’t be this hard!
32.
▲
by
flounder3
4y ago
I was part of Orchard and miss it dearly. It had a lot of potential but it was launched as a proof of concept built on pooled resources freed up from optimizing legacy workloads (namely, moving Siri from VMware to Mesos). It never got the l
33.
▲
by
flounder3
4y ago
Splunk worked with us to optimize our configs but we always managed it ourselves.
34.
▲
by
flounder3
4y ago
I totally understand that ripple effect and am very familiar with Most Favored X when it comes to unit pricing of a tangible good (e.g. xx,xxx physical servers with a particular SKU), but in this case we were talking about a SaaS product wh
35.
▲
by
flounder3
4y ago
Lol, this is exactly what I was referring to! We were negotiating a massive renewal (50x budget IN EARNEST!) and out of nowhere they threatened to cut us off with less than 24 hours notice because we were a week behind their schedule, despi
36.
▲
by
flounder3
4y ago
Absolutely agree. It’s tragic. Shoving SignalFx down our mouths and trying to get us to create “metric” indices was the straw that broke my back.
37.
▲
by
flounder3
4y ago
I personally brought Splunk to Apple in 2010 alongside a small handful of people (Hi, Sean and Ariel!). There is a massive difference between real-time searches where latency beyond a few seconds is unacceptable, and historical searches whi
38.
▲
by
flounder3
4y ago
Sounds crazy, but Datadog. I’ve been hammering their product teams for years with specific use cases for the sole purpose of replacing Splunk. They recently migrated search technologies and are rapidly closing the gap. Plus, their exclusion
39.
▲
by
flounder3
4y ago
It has always been the Cadillac of search, and moreso with unstructured indexing (e.g. key collisions with different data structures. Foo = string vs foo = integer vs foo = array). Your queries or infrastructure were not optimized. It’s ver
40.
▲
by
flounder3
4y ago
Splunk, as a company, is a shell of its former self. All they care about is pimping themselves out to maximize profits to an extreme that only Dilbert can relate to, even at the expense of destroying a long term professional relationship ov
41.
▲
by
flounder3
5y ago
San Francisco. Los Angeles. Seattle. San Jose (albeit theft has never received attention in San Jose)
42.
▲
by
flounder3
7y ago
Did you read the article? It begins with "Electronic health record giant Epic Systems..."
43.
▲
by
flounder3
7y ago
There is no mention of the type of fuel the cargo ship burned while outside of port (bunker fuel, anyone?). The three citations at the end of the article simply reference generic sites, not specific information.
44.
▲
by
flounder3
7y ago
I appreciate the gesture, but what's to keep them from moving their scraper to a third-party cloud provider, or sales folks using a VPN?
45.
▲
by
flounder3
7y ago
We implemented it for Siri in iOS 7. Exposed APIs for third party developers in iOS 11.
46.
▲
by
flounder3
7y ago
The secondary market for whiskey is quite real. The article is remarkably accurate on that accord, so it is very easy to believe the meat market is similar. With regard to booze: there is no way to truly verify or authenticate until you dri
47.
▲
by
flounder3
9y ago
Regarding [1], the move to Mesos was not a rewrite. Some core components had to be improved, but [2] was primarily an infrastructure upgrade that happened to make Siri considerably faster by ditching hypervisors. It was a massive feat that