On Tue, May 8, 2012 at 4:17 PM, Andrew Parker <[email protected]> wrote:
> I'll chime in on this now, I suppose. > > You are right that both read and write operations are good for > abstraction. The problem comes that comes into play is that read and write > operations usually end up with completely different needs for their > abstractions and so combining them together in a single system can be > problematic (this is the basis for the CQRS architectural design). So > although you can combine the write model and the read model in the same > application, they often will have little to do with each other and so you > might as well keep them separate. > > Ah I see what you mean now. It's not that we shouldn't have a write API, it's that it probably shouldn't be all tangled up in the query API. Thanks for the reply Andrew. -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
