Hi, I definitely recommend this approach... You symfony as a frontend presentation platform (gluing the pieces together and displaying to the user). All the heavy lifting can be done via services underneath.
I would recommend using curl_multi to execute web requests in parallel and reduce latency (see ysfAPIClientPlugin). You can use c++/java/erlang to create the underlying services and transport with xml/json.. Also, you can create a lightweight php client/object model to make a simple api. This allows you to decouple your components, which makes it easier to scale the backend. - Dustin On 10/24/08 9:44 AM, "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 -~----------~----~----~----~------~----~------~--~---
