Background
如果我能将其归结为一个简单的模拟,那么这将是一个集合与较少的客户文档(如Java)之间的区别:
class Customer { private String name; private Address address; // each CreditCard has hundreds of Payment instances private Set<CreditCard> creditCards; }
或者一个有很多很多付款文件的集合,比如:
class Payment { private Customer customer; private CreditCard creditCard; private Date payDate; private float payAmount; }
Question
我环顾了很多地方,但我没有偶然发现任何MongoDB模式最佳实践可以帮助我回答我的问题.