I did something very similar with MySQL since that was the DB we already had setup for data (not my choice). Basically any database that has atomic operations can do this. It definitely is way more convenient and cheaper to do use your existing infra for pub/sub and then only scale out to other services once performance becomes subpar. Although if you already have a messaging service up and running, it’s probably better to use that
My company was using GitHub and then we were purchased by a company using BitBucket and had to switch over. We don't even use the CI/CD features but IMO the BitBucket experience is just horrible overall.
When I was in physical therapy about a year ago they told me to leave reviews in Google rather than Yelp because research showed it was more effective. I found it hard to believe since my peers and I both used Yelp way more, but I find this recent behavior from Yelp abhorrent so it may be time to switch
I thought the same thing when I received it. However, at the end I gave them the benefit of the doubt that perhaps they were migrating from one hashing algorithm to another and decided to just reset everyone's password in the process. Lying about the breach entirely is so shady
Yep, sounds like a bank to me. I worked at one of the big 4 for 6 years (way too long, I know) and the experience was horrible. It once took us a full year (no exaggeration) to get a single server allocated...and my group was actually one of the well funded teams
No way...I don't remember hearing about this. You mean changing the URL from like /data/customer/1 to /data/customer/2 ? And the person who did this was prosecuted? Jeez.
I feel like we hear about potential breakthrough cancer cures daily, but then never hear about them again. Do they not make it past animal testing or is our healthcare system so slow that it just takes forever for trials to move along?
I agree it's more akin to malware, but without knowing the implementation details of how the removal was actually done, to me it just feels like a bandaid monkeypatch. For example, it seems like the removal of the Zoom local server was hardcoded into the first silent patch. How can Apple tell between the Zoom local server and a local server I am using for development? I just get the feeling that if any other vendor was silently disrupting applications I (knowingly) installed, there would be outrage
While I appreciate Apple's care to make sure Macs are as secure as possible, I feel like silently disabling or interfering with applications on users' machines is almost going to far. I hate to use such a cliche term, but isn't this a slippery slope?
Hmm..but I'm not getting a confirmation prompt on Firefox or Chrome? Visiting a zoom link in either of those browsers takes me directly into the meeting
I could be wrong, but it looks like they are doing a server-side redirect to their custom zoommtg:// URI protocol now instead of making a call to the localhost server. Couldn't anyone still drop this on their website and force you to join through a redirect just as zoom is? I don't see how that particular concern of the disclosure could be avoided unless browsers force confirmation, as Safari has done.
We had Redshift for our 23TB+ dataset and it worked great. The downside is it can get pricy, so do a cost analysis before you commit. Also know that views in redshift are not materialized so it’s more efficient to create physical tables of the views - which then adds maintenance overhead. The last thing I’ll add is that you’ll need to experiment with compression settings for your data. For us, a combination of ZSTD and bytedict was all we needed
Would they be able to start offering discounts for those who make purchases with an Apple Card vs other credit card? Would be interesting to see if we are having a “credit card neutrality” discussion here in the not too distant future.
Ah, I see what you’re saying now. #2 was always a pain to deal with, but I think other systems have similar problems. Other messaging systems deal with this with things like dead letter queues etc, but no matter what you use for message processing you will need some specialized logic to handle records which can’t be processed normally. In Kafka, you can raise an exception for the offset and then move on. When dealing with the exception, you can seek directly to the record offset and take it from there.
For #1, any application which has an in-order requirement would suffer from this problem. I worked with event processing systems so we never really had to worry about this, since each event was independent. However, there were instances where we would need to track state for certain objects getting processed to make sure all of their child objects were also processed. For this we would use an external store with a short TTL since the lifetime of the object during processing would only be a few minutes.
All-in-all it just comes down to what your app’s requirements are. I don’t think Kafka is meant to replace every pub sub service out there, but definitely has some great use cases.
This is a fair thing to point out. For us the “at-most-once” guarantee was based on committing. Luckily our processing was idempotent so in the rare case of the above scenario it wouldn’t cause any duplication
I’m not sure what you mean by “only accepts offsets which are meant for batches” but with Kafka the offsets are per-partition and you have to flexibility to control exactly when that offset is marked as processed. In our systems we always used manual offset committing and would only commit an offset once processing of the message has completed successfully to ensure both at-most-once and seamless failover.
Well when you work with distributed messaging systems it can be difficult (if not impossible) to guarantee messages arrive or are processed in the same order in which they were generated. So I think the author is just saying generally speaking it’s better to track as little state as possible if you don’t need to.
I was really hoping Apple would yank the certs instead of just the usual “that’s not allowed, please stop and don’t do again” leniency they usually give larger companies. This is the only way to make companies listen
I’m surprised it took them so long to do this. I forget which app it was (maybe Spotify) but I remember them offloading the tax to the consumer by having a 15% higher subscription fee from within iOS. From a consumer standpoint I find the iOS subscription doesn’t add any value. Have you tried finding where to cancel subscriptions from within iOS? It’s buried under so many menu clicks it’s impossible to find without searching the web for help
I go on YouTube like once a month, at most. So yea I’m with you. I’ve actually _tried_ to get “addicted” to it by forcing myself to search for interesting videos just to see what all the fuss about, but I just never end up going back to the site for more
To be frank, Apple blocking 3rd party cookies really doesn't make that big of an impact. The Safari market share is small enough where it really doesn't matter, and there are already cookie-less tracking solutions in place that are more reliable than cookies anyways
Same thing happened when I dislocated my shoulder last year. No NSAID could have done what that morphine did. They tried for about 10min to do it without the morphine but it was just simply not happening. After the morphine they actually had to put my shoulder back in twice since it popped right back out after the first attempt.
I casually switched to Atom for a week or two and although i think it looks a lot prettier out of the box, it just feels HEAVY. Launching can take awhile and it freezes up a decent amount. I've also seen it suck up quite a bit of memory at times. Atom has made some strides in the past couple releases but I'll be sticking to Sublime for the time being.