Front-end and Back-end on Different Domains

[jeet_inging22]

Hi,

I am planing to separate Back-end and Front-end on Different Domains . The main domain for Front-end and other for Back-end . All the product images will be stored on Beck-end side . Also I will use CDN , Caching options in Future.

Will be any issue in Scalability if I use Different Domains for Back-end and Front-end ? It is a Big E-commerce Project.

-
Jeet

[Robert Gonzalez]

Scalability no, but you will probably run into some issues if you plan on using anything ajaxy given the nature of cross domain policies of browsers.

I'm not sure this is the best architecture for what you are doing. Can you give us a little more info as to what you want to accomplish?

--
This group is managed and maintained by the development staff at 360 PSG. An enterprise application development company utilizing open-source technologies for todays small-to-medium size businesses.
 
For information or project assistance please visit :
http://www.360psg.com
 
You received this message because you are subscribed to the Google Groups "Professional PHP Developers" group.
To post to this group, send email to Professi...@googlegroups.com
To unsubscribe from this group, send email to Professional-P...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Professional-PHP

--

Robert Gonzalez

   

[jeet_inging22]

Hello,

Thanks Robert for quick response .
Actually I want 2 or more websites with Common Back-end for All .

www.ecom1.com ( for Clothes )
www.ecom2.com ( For Jewellery )
www.ecom3.com ( For Electronics )

One database for All the website and Backend

One Central Backend for Order management etc. Also here product images for all the websites will be stored here.




-
jeet

[Robert Gonzalez]

You can do this all on one server pretty easily, although if this needs to scale you'd be better off using Amazon Web Services and setting up a couple of Large Instance EC2s behind an ELB. You can set up rsync scripts to keep all of the file systems in sync. 

Then set up an RDS for your database and use S3 for your assets (CSS, images, etc). This is a pretty common architecture for cloud deployments that need to scale and at the same time will still allow you to do exactly what you're trying to do. 

To post to this group, send email to Professional-PHP@googleg

[jeet_inging22]

Thanks a lot, robert