I've chosen to develop my server-side code with Ruby on Rails. It's the most productive technology I've encountered. I access its XML output via HTTPService.
If you're designing your application and database from scratch, I don't think anything can beat it, from a productivity standpoint (most of the code is generated automatically). If you're starting from an existing database, like I am, you'll nead to tweak the code a bit, but not much. Chris. --- In [email protected], "mmthm" <[EMAIL PROTECTED]> wrote: > > I'm new to flex and i'm struggling with what to use for the backend > architecture? > > I have seen some discussions on the merits of Livecycle/Flex > Dataservices, vs AMF/RemoteObject, vs HTTPService, vs WebServices, > vs??? > > My main criteria is speed of development. Simplicity and the ability > to pump out solid implementation quickly is my primary concern. I > understand that AMF is a very efficient protocol, but my app is not > massively scaled, so performance is not a significant factor. > > I have traditionally used XML over HTTP. It is very simple, and very > productive from my experience, but i have no experience with the > other options. > > On paper i like what LCDS offers. The ability to synchronize a > domain model across views not only in one app, but across distributed > users, is very cool. Not to mention the ability to help resolve > update conflicts. I could also see using the pub/sub and the ability > to publish live data, especially for charts. > > But how simple and quick is it to learn/use/develop? How well does > it work in practice? Does it work well for simple cases, but get > painful for realworld scenarios? Does it feel like you are working > with a scary black-box, or a simple transparent library? Is the > quality of documentation high, and the support available to resolve > questions? > > XML is can be designed relatively stateless and lightweight on the > server. Are the memory/resource requirements of LCDS significant in > order to maintain the consistency of all the domain objects for > clients? > > What about Cairngorm? My app is of medium size and complexity. It > worth using Cairngorm? Will it increase my productivity, or it more > useful as an architectural framework for very large/complex apps? > Does the framework equally support all the serverside options? > > Maybe some hybrid approach is best? > > Bottom-line, what option do you think is the most productive route to > quickly crank out code? > > Thank you. >
