DDP out of Meteor

Few minutes ago I asked on Reddit why DDP not widely adopted out of Meteor community:

I did not get answer yet, but found problems:

  1. In spec there is mentioned EJSON, but SUPERJSON beat ejson 10 times in popularity, growing faster and is more features rich.

  2. change looks simple when you see it first time

changed (server -> client):
- collection: string (collection name)
- id: string (document ID)
- fields: optional object with EJSON values
- cleared: optional array of strings (field names to delete)

but is incompatible with more mature specs like RFC 6902 (JavaScript Object Notation (JSON) Patch) or simpler RFC 7396 (JSON Merge Patch)


I although of these problems I can’t find better spec for collections sync by websocket than DDP.

So my question is:

  • are these two problems, biggest blockers of adoption of DDP out of meteor
  • do you see other reasons why it is not widely used as layer on websocket that can be easily plugged to frameworks like for example fathers?

I think the first question to ask is: is that the problem at the begining?
DDP designed for Meteor. It’s like asking a question: why GAU-8 Avenger 30mm gatling gun has none adoption out of A10 Warthog?

1 Like