flex - Best practices for model driven development using LiveCycle Data Services -


What is your advice on using model-driven development to develop enterprise applications? Adobe's Live Seekal Data Services looks very promising, I have found several tutorials / videos that show how fast one application can be created in one way / automatic applications being generated.

What are the best practices, it's good / bad to use those auto-generated methods, they can actually save a lot of time.

All suggestions are welcome, please tell me if you know some current blogs / discussions.

Make sure your model is very tight, and that your object graph does not bring the whole database Fill a combo box when you are actually trying to be. ;) Our team was sold to our management to use Hibernate as a level of persistence on our heritage relational database on the last Flex project part of our team. The part of the sales pitch was that the model could only be produced by a magician. Well, maybe lazy loading better than LCDs Blazads, but for the first time we tried to load Cambodia, we pulled several MHz figures due to autogenerated relationships, sometimes recursive, which generated by the wizards Was there. Perhaps due to sluggish load it will never come to light during the normal web app, but the serialization will show you the exact meaning of "N + 1 problem" !!

;)


Comments