1 person found this helpful
DCD is currently in its infancy and suffers from a lack of features you might find in more mature tools of this nature. In its current form I think its a great tool for rapid prototyping and as it matures may also be a great tool for enterprise development. I am sure as Adobe work with feedback they get from the community these wizards etc.. will get much better.
So that leaves you with the choice of staying with what you are familiar with or putting the effort into become familiar with DCD and using it to its maximum abilities then pushing it a bit further. Its now a part of the environment and its not going to disappear so its wise to at least become familiar with its useability so you don't get left behind as it does improve.
At the moment it does a lot of the minding numbing work of setting up connections preparing client side and server side scripting for basic crud operations and in many simple cases this will be enough.
You can update services with you own code and DCD will generate the client side code for you (VO's etc) you just need to guide DCD as to send and return types. In a lot of cases you can reuse the value objects generated for your extended services (for instance you have a client table that you create a filter for you just tell dcd its the same type as a select from client and when it generates your client code it knows how to type results etc.)
Experts will never be happy with wizards, the code is not as optimal as hand written code and sometimes confusing to maintain. For those getting into development of backend communication the DCD will help them immensely, and hopefully guide them to best practises when it comes to how you should structure everything.
Is it ready for large scale application ?, thats not my call to make(but it's not ready yet ), I will use DCD if I think it can do the job without to much from me otherwise the old tried and true methods will be applied. My expectation is that the DCD will become more powerful and as it does I will be ready to use it on a more frequent basis. For now I still concentrate most my efforts on the 'old way' but won't ignore and the value it can bring to the development cycle.
Thanks a lot for the instructive response.
The main problem is that there's no much info on the insights of DCM. Yes every site shows how with 2 clicks you can see your table in a grid, but this is not a real use case.
I miss a bit of information about how to add new operations, some advices about what can be broken if added, etc... For example I need to retrieve data form a table but resolving some foreign keys and I don't really know how to do it using the generated code. I have checked the files and have seen where operations are defined, etc... but don't know if adding/updating/delteing some of the code will break everything. I'm pretty new to fiber package too.
Anyway, thanks for the comment, it has confirmed some suspects I had . If anyone could expose some tutorial, insights, etc... about my doubts I will be really happy.
Thanks in advance,
1 person found this helpful
Aron, I think David F57’s answer above is right on.
I had issues similar to yours a couple of months ago. and also came to the conclusion that DCD is not yet ready for serious work, but eventually will be. Right now, it’s fine for prototyping and trying fun little projects. You may want to look at this thread, http://forums.adobe.com/message/2834411 and see how and why I reached my conclusion.
Frankly, I think that, at this point, this DCD thing is a more a marketing tool for Adobe than a way to serious development. A lot of people new to this will be dazzled when they see they can just drag a service to a component and end up with an application that displays and manipulates data in minutes – but I am not sure about how many will really understand what is going on.
Thanks for clarification,