�ݺ�ߣ

Editor's Notes

• #5: Note: Growth refers to year-to-date revenue based on our fiscal years for 2011 and 2012, i.e., it compares Feb-Oct 2011 (calendar year) to Feb-Oct 2012 (calendar). These figures are unaudited and subject to change.
• #32: A highlight of some key features in 2.4. . . . We ’ll add more details and more items each month as we work towards a winter release. Security: SASL is a framework for authentication that helps decouple specific authentication mechanisms from client/server implementation. This framework will permit working with a variety of authentication mechanisms, initially we ’ll build in kerberos. We may add others over time, but SASL implementation will make it much easier for you to add your own without having to implement a new client. Kerberos is quite common, so we ’ll build that one in first. With additional authentication, we want to take a few steps to separate out activities authorized to various users. Separate read, read/write, security administration, database-specific (compact, validate, etc.), and server/cluster administration (fsync, log rotate, shutdown, create database, etc.). This is just an initial step in our authorization work. Hash-based sharding Apply a hash function to a selected key as the shard key. Evenly spread documents in a sharded cluster. Evenly spread the work associated with queries in a sharded cluster. Will minimize migrations (should only happen when growing a cluster). Note: this is something you can do now, but not automatic. Geospatial index resolution: Talk about challenge of specifying some polygon and finding overlap with another polygon in a document, this becomes interesting for location-aware applications, intelligence community. Replica set flapping: avoid electing a new primary due to a falsely detecting that the current primary went down. Adding mechanisms to reduce false detections. This is good for heavy load and network issues/blips in a data center.
• #34: Ok, so here are the presenters notes. Your first job is to add you name and other useful stuff so that your students can contact you afterwards. This is a good time to - introduce yourself - create a seating chart, get each student to say their name, company and what they want to learn... and write it on your seating chart
• #36: A highlight of some key features in 2.4. . . . We ’ll add more details and more items each month as we work towards a winter release. Security: SASL is a framework for authentication that helps decouple specific authentication mechanisms from client/server implementation. This framework will permit working with a variety of authentication mechanisms, initially we ’ll build in kerberos. We may add others over time, but SASL implementation will make it much easier for you to add your own without having to implement a new client. Kerberos is quite common, so we ’ll build that one in first. With additional authentication, we want to take a few steps to separate out activities authorized to various users. Separate read, read/write, security administration, database-specific (compact, validate, etc.), and server/cluster administration (fsync, log rotate, shutdown, create database, etc.). This is just an initial step in our authorization work. Hash-based sharding Apply a hash function to a selected key as the shard key. Evenly spread documents in a sharded cluster. Evenly spread the work associated with queries in a sharded cluster. Will minimize migrations (should only happen when growing a cluster). Note: this is something you can do now, but not automatic. Geospatial index resolution: Talk about challenge of specifying some polygon and finding overlap with another polygon in a document, this becomes interesting for location-aware applications, intelligence community. Replica set flapping: avoid electing a new primary due to a falsely detecting that the current primary went down. Adding mechanisms to reduce false detections. This is good for heavy load and network issues/blips in a data center.