gatesvp1

6 ms·

1. 1.▲
   by gatesvp1 14y ago

   This is a long-outstanding bug, over 2 years old now: https://jira.mongodb.org/browse/SERVER-863 Obviously you can vote for them to fix the bug. But it's been two years, so I'm not sure it's really high on the priority list.
2. 2.▲
   by gatesvp1 14y ago

   Not a personal attack as Catch is a neat product, but these numbers are basically irrelevant. This type of load can easily be handled by a simple SQL box. We did these types of #s with a single SQL Server box 4 years ago, except that your "
3. 3.▲
   by gatesvp1 14y ago

   The big thing here is cost. > If you put the above rules together, you can see that the minimum MySQL deployment is four servers: two in each of two colos... The ideal scenario is to have 4 "fully equipped" nodes, 2 in each data center.
4. 4.▲
   by gatesvp1 14y ago

   > A more "Mongo" approach is to migrate data as you need to; e.g. you pull in an older document and at that time add any missing fields. I think this works when you're talking about adding fields. But it really breaks down if you need t
5. 5.▲
   by gatesvp1 14y ago

   So that's not actually "safe". If you issue an insert in the default "fire and forget" mode and that insert causes an error (say a duplicate key violation), no exception will be thrown. Even with journaling on your code does not get an exce