alyson-cabral

Will you sign up for the beta at https://www.cloudflare.com/workers-unbound-beta/ linking to this post? Me or my team will follow-up directly to understand your use case and see if it's a good fit.

In 4.0, transactions will just be across replica-sets. The following release will have transactions across the entire sharded cluster (across multiple primaries).

I'm the Product Manager on the Core Server responsible for the multi-document transactions project. For those of you interested in learning more about how we're building transactions in MongoDB, I suggest checking out this video that discusses creating WiredTiger timestamps to enforce correctness in operation ordering across the storage layer. The description is presented by Dr. Michael Cahill, the co-founder of the WiredTiger storage engine aquired by MongoDB. https://www.mongodb.com/presentations/wiredtiger-timestamps-...

I'm one of the Product Managers at MongoDB and I was a part of making this decision. It seems like there are two main areas where people are asking for more information: 1) exactly what are the numbers of Solaris downloads and 2) what about security patches of existing versions? I'm happy to clarify those points here and we will be posting an update to the blog to include this information.

Based on the data we have, about 0.06% (and decreasing) of MongoDB users are running on Solaris. In addition, as Andrew mentioned in the blog, all of our customers have either deprecated Solaris or have told us they plan to deprecate it.

In regards to security patches on Solaris, we will continue to fix critical flaws for the community, regardless of where found or how reported. Anyone can report a security vulnerability by using our Security project (https://jira.mongodb.org/browse/SECURITY) to create an account then a ticket describing the vulnerability.