H, Thanks Dusting and Stefan for your replies, i have seen Symfony presentations by Yahoo and there i caught some good ideas too and ysfAPIClientPlugin is great contribution to Symfony. I decided to use it in my project already. Actually i am focusing on C++, JAVA and Perl as a backend platforms for persistent db & storage, logging ... Recently i read about some open source tools by facebook guys, especially the most interesting one is Thrift - Framework for scalable cross-language services. I found it very handy.
About symfony1.2 I agree with u Stefan, with that promised features symfony definitely can be used in some specific backend nodes. Looking forward to see released Symfony1.2 :) On Oct 25, 4:25 am, "Stefan Koopmanschap" <[EMAIL PROTECTED] project.com> wrote: > Hi, > > Symfony for the frontend is an excellent choice. I recently did a > project scoping for a project with a similar setup. > > For the project I scoped for, I went with a symfony frontend and a > Zend Framework backend. Why? Well, simply because for this project, > that simply was the best fit. > > symfony could be just as good for the backend though. Especially with > the new REST support in 1.2, symfony could well become an excellent > choice. > > However, with the amount of users you might be running into, there are > some optimizations you may want to look at. This group and the > symfony-devs group are interesting for that. You might also want to > talk to Dustin Whittle or check out of some of his Yahoo! > presentations on slideshare. > > However, the choice for backend really depends on what you need this > backend to do. There are situations where a J2EE backend is more > fitting, or C#/.NET. These situations are getting less and less often > though, as in a lot of situations, PHP will do just fine and even > symfony will help you fine in this. So without knowing too much of the > specifics, I can't go into this too much. But I hope this helps > nonetheless. > > Stefan > > On Fri, Oct 24, 2008 at 6:44 PM, shuxer <[EMAIL PROTECTED]> wrote: > > > Hi All > > > Recently i faced an issue of separating ORM from frontend and move it > > down the stack, that is SOA. > > Although I have read the previous discussions on this topic and i > > would like know the community opinion more on implementation side of > > it. > > > I am planning symfony as frontend(only view). All hard works(sharding, > > massaging, task queue ..) in bachend nodes. > > What platform would be used in backend ? Java EE , C++ or Perl ? maybe > > PHP :) ? Any good practice you would share ? And how frontend should > > talk to backend API, http or down layers ? > > > Expected usage of this application is up to 1 Million users. If get > > success more than 5 Million users. > > > Any suggestions would be appreciated. > > > Shuxer. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
