We're happy to announce TMS XData v1.0, a Delphi framework for multi-tier REST/JSON HTTP/HTTPS application server development and ORM remoting.: http://www.tmssoftware.com/site/xdata.asp
We're happy to announce TMS XData v1.0, a Delphi framework for multi-tier REST/JSON HTTP/HTTPS application server development and ORM remoting.: http://www.tmssoftware.com/site/xdata.asp
Features:
- Server based on REST/JSON architecture style
- Easily accessible from different client platforms like .NET, Java, JavaScript, since it's REST/JSON based
- Uses standard POST, GET, PUT and DELETE HTTP methods for data request and data modification operations
- Partial update of objects (PATCH)
- Full-featured query mechanism
- Well-defined JSON representation of resources including entities, associations, streams and proxies
- Support for streams (blobs)
- Several databases supported in back end: SQL Server, MySQL, PostgreSQL, Oracle, Firebird, etc.. (through TMS Aurelius)
- Design based on standard OData protocol
http://www.tmssoftware.com/site/xdata.asp
Features:
- Server based on REST/JSON architecture style
- Easily accessible from different client platforms like .NET, Java, JavaScript, since it's REST/JSON based
- Uses standard POST, GET, PUT and DELETE HTTP methods for data request and data modification operations
- Partial update of objects (PATCH)
- Full-featured query mechanism
- Well-defined JSON representation of resources including entities, associations, streams and proxies
- Support for streams (blobs)
- Several databases supported in back end: SQL Server, MySQL, PostgreSQL, Oracle, Firebird, etc.. (through TMS Aurelius)
- Design based on standard OData protocol
http://www.tmssoftware.com/site/xdata.asp
Wagner Landgraf By 'aggregate", I mean the definition used in Domain Driven Design, and, in a more informal way, by NoSQL document-oriented databases like CouchDB or MongoDB. The "Data Sharding" pattern implemented by those "aggregates" is something more specific than inline objects, breaking the whole relational model.
ReplyDeleteI used to work on remote DB access via REST and JSON since years, in both SQL and NoSQL worlds, and investigated about OData from its first official release by Microsoft. I do not have doubts about your work, but about OData itself. Just as I have with the docx format - as a standard.
But you are right about my comments.
I now feel sorry to have sounded negative about your work, which is certainly very valuable.
Please accept my apologies if I have hurt you, in any way. It was not my intent at all.
OData in version 4 is very different from the first versions. Being xml-only, early versions were indeed a nightmare. But note that XData was "inspired" from OData, it's not OData. We just borrowed the concepts we felt it was great and already well-thought, like URL conventions, query syntax, etc.. I believe you didn't have bad intentions and you did not hurt myself specifically. I think you do an awesome job with your product, and I'm also proud of what we deliver. They intersect at some degree, but they are just different. Some people will prefer one, some people will prefer the other. There are plenty of space for both of us (and others) and we can just let people decide what's best for them without needing to depreciate or question other's work or design. Apologies accepted.
ReplyDeletegreat job on both, the important thing is that with their products continue to evolve our beloved Delphi
ReplyDelete