Is there any message ordering guarantee in NATS? With Kafka you can achieve this by using keyed message and messages in the same partition will always be ordered
> messages from a given single publisher will be delivered to all eligible subscribers in the order in which they were originally published. There are no guarantees of message delivery order amongst multiple publishers.
I believe with jetstream, message in stream is ordered as they are written. Jetstream have a concept of consumer, (in the broker itself, not client), which can consume a subset of the stream, filtered by message subject.
I've never really understood the appeal of ordered messages. You end up splitting your data across partitions anyways for parallelism, so who cares? What systems out there require strictly ordered data? It seems like any design that requires something like that is going to be extremely brittle.
Right, but that means you're still "unordered" across those partitions?
> TCP/IP ?
But TCP/IP isn't delivered in order, it rearranges the unordered packages by their ID. I guess ordered delivery would be nice for that, but I just feel like making your protocol not require ordering is far simpler.
Not to mention that both TCP and Kafka have to handle head of line blocking?
I'm not trying to say that ordering is bad or anything, I just feel like it isn't buying me tons.
> Right, but that means you're still "unordered" across those partitions?
Right, so related messages have an ordering guarantee but unrelated messages may be processed out of order relative to each other, which is usually what you want. (Of course you do have to set the record key correctly).
> I'm not trying to say that ordering is bad or anything, I just feel like it isn't buying me tons.
It's a lot more lightweight than full ACID, but if you get your dataflow right it achieves everything that a traditional database does. Without ordering you wouldn't be able to do anything that requires any kind of consistency.
Hm, ok, yeah. So I guess I can see what you mean. I've never had a use case where I felt comfortable relying on any kind of message ordering, and always rely on my application level logic to handle that, or ensure the system is resilient despite ordering (ie: commutative operations only).
To me, it seemed at odds with the parallelism of a partition, but I suppose in this case you'd be partitioning on some sort of semantic key vs, say, a hash.
Thanks for bearing with me on that, this was just an unfamiliar idea for me.
Maybe if you're an e-business, you'll split everything happening on your website by client id, but still want events belonging to a single client to be received in order, for practicality.
That was a company selling Hackintoshes. In the many years since, Hackintoshes have remained a thing and I'm unaware of any individuals that have faced criminal or civil penalties.
Until recently, a Hackintosh was a time-consuming way of producing a somewhat worse Mac. As Apple is starting to drive us away, I bet the phenomenon will grow, and then Apple's interest in squishing it will too. And the fact is, Apple could shut this phenomenon down in a matter of hours if they wanted to.
This level of risk is fun but not for the faint of heart.
> Until recently, a Hackintosh was a time-consuming way of producing a somewhat worse Mac.
Oh? What has changed?
> This level of risk is fun but not for the faint of heart.
Read: as soon as a new patch comes out for macOS you are either running around with known security vulnerabilities (as well as missing reliability fixes), or you're a guinea pig entirely unsure if it breaks anything and if so how much effort it is going to take to get the patch applied. Why? Mainly due to drivers.
Besides, good luck finding a well working laptop with good macOS support.
I gave up and bought a MBP 2015 instead. Very nice machine. Expensive, but nice.
For a workstation or MP replacement it'd make more sense. The MP hasn't been updated for 4 years and with physical access to the quick machine its easier to fix issues. You're also guaranteed not on the go, so you got all the tools you need at your disposal. However there is still a risk for loss of productivity and worst of all you can't plan it. Because you don't know when Apple does release their software updates.
I don't think it'd be wise of them to shut down the Hackintosh community. The vast majority of Hackintosh refugees aren't going to be buying Macs, they're going to be wiping their macOS partitions and jumping ship to Windows or some random Linux distro instead. It'd shrink the number of people invested in the Apple ecosystem (including subscriptions like iCloud and Apple Music) and put a bad taste in the mouths of a lot of people with sway of family/friend and perhaps even corporate purchasing decisions, not to mention strongly casts Apple in a Big Corporate Bully sort of light. There's not a scenario in which they kill off Hackintoshing that's a net benefit for Apple.
Apple is a hardware company. The services you mention are small in terms of revenue compared to their profits in hardware. If the Hackintosh community is large enough that the services revenue or impact on the ecosystem is signigicant, Apple would rather have the revenues associated with the hardware as well.
The fact that Apple hasn't done this already is because it's insignificant, not because of some benelovence on Apple's part. They're not going to encourage unlicensed use of the OS. The OS is there to sell the hardware, not vice versa.
There's the potential to create a pretty powerful machine for the buck, but it's definitely fraught with challenge. Reminds me of building a decent desktop Linux machine in the late 90's/early 2000's.
not really, i was running osx 10.5, so almost 10 years ago out of the box, the only thing that i had to play with was sound.
there was only one rule and i believe the same i truth now, if you plan to run hackintosh u better watch what hardware you get. if you do that u can run hackintosh without problems.
What we do:
Eyeota is the global leader for audience data with over 2 billion unique profiles. Eyeota provides marketers with the data they need to reach the right online audiences and cut campaign waste whilst also enabling publishers to monetize their audiences more widely. In addition, our data delivers deep audience insight to both marketers and online publishers to help them understand their customers in a new way – as human beings. Eyeota supplies third party audience data to all major global and regional ad buying platforms, trading desks, DSPs, DMPs and ad networks. The company was founded in 2010 and has offices in Berlin, London, Melbourne, New York, Singapore, Sydney and Tokyo.
Who we're looking for:
Full stack developer to join our team in Singapore. In this role, you will be working in close collaboration with a team of highly empowered, experienced developers who are building a high-performance, highly scaled global platform.
Some of the technologies that we use: Java, Clojure, Apache Cassandra, ElasticSearch, Kafka, Ember.js, Ansible
Hello there, I think Singapore is hot! (Pun intended)
Location: Guangzhou China and/or Vancouver, Canada (Flying man)
Willing to relocate: Yes
Technologies: Interested in: Clojure, ClojureScript, Core Java, Reagent/OM, Machine Learning.
I personally love functional programming style. But JVM is also awesome. So ... Clojure!
Eyeota is the global leader for audience data with over 2 billion unique profiles. Eyeota provides marketers with the data they need to reach the right online audiences and cut campaign waste whilst also enabling publishers to monetize their audiences more widely. In addition, our data delivers deep audience insight to both marketers and online publishers to help them understand their customers in a new way – as human beings. Eyeota supplies third party audience data to all major global and regional ad buying platforms, trading desks, DSPs, DMPs and ad networks. The company was founded in 2010 and has offices in Berlin, London, Melbourne, New York, Singapore, Sydney and Tokyo.
We are looking for both experienced Backend developer (Java) and Full stack developer to join our team in Singapore and be instrumental in taking our products to the next level. In this role, you will be working in close collaboration with a team of highly empowered, experienced developers who are building a high-performance, highly scaled global platform.
Some of the technologies that we use: Java, Clojure, Apache Cassandra, ElasticSearch, Kafka, Ember.js, Ansible
Disclosure: I work for Confluent