Database Connectivity - Using a different server

[ecomuser2010]

Hi there,

I currently have 2 stores running:

Store A - a store that users can purchase products from
Store B - another zen cart set up with the exact same products as Store A.


My question is, is there any way for Store A to pull it's product info and store it's sales in Store B?
I want all users to use Store A but have all database connectivity go to Store B. Store's A's DB should be disregarded completely.


They are on seperate domains & servers. If you have any questions, please let me know. Otherwise, I appreciate any input given!

[ecomuser2010]

Just to illustrate a bit better, the flow of the transaction would go like this:

ADD TO CART IN STORE A

\/

CHECKOUT PROCESS AND PAYMENT IN STORE A

\/

WRITE ALL DATA TO DATABASE IN STORE B



Orders would be then processed from the back end of Store B

[DrByte]

Um ... why?
There's a whole lot of information missing from your post, and thus a proper answer is impossible without understanding the much bigger picture of what you're trying to do and why.

Why have 2 stores at all?
Why force your customers into delays while one store is trying to read data over a slow connection to another server to find data that can/should already be in its own database anyway?
Why cripple half of two stores just to name them "A" and "B" when there's no functional difference between them in the end?

[ecomuser2010]

It's been requested by a client. I've tried to deter them from it but this is what they really want. They plan on having multiple stores on different servers write to one single database.

[DrByte]

If those stores are on different servers, then they have no idea what they're really getting into. Seriously.

(Databases housed on separate servers introduce significant delays in getting responses back when reading and writing the data. That's not a prudent thing to do in real-time customer-interaction websites.)

I suggest that if they really want something akin to what you've described in your posts, that a different approach be used, whereby each store stands on its own but simply sends the appropriate data back and forth to the other databases on a scheduled basis. Otherwise you'll have serious performance problems which will cause customers to give up waiting for the data to show up.
Having each store stand on its own also gives redundancy in case one of the other servers may go down or be unreachable for some reason outside your control.

I suggest hiring someone who understands servers and databases very well when you consider designing the architecture of the solution for your client, regardless what solution you ultimately select.

[ecomuser2010]

Thank you very much for your input. I do actually have someone who actually owns a small hosting company setting it up. The more info I have the better as he's never done anything like this himself either.

I did think of the timed intervals to send the info to the other DB but the client is absolutely requires that the transactions run through the "Other Cart". Sending every 6 hours, for example, would still mean that the transactions are running through the current store.

[ecomuser2010]

If both carts were moved on the same server, would we have the sam performance issues ?

[DrByte]

If they're physically on the same server, the performance issues to which I was referring are unlikely to be a problem.

[DrByte]

It's been requested by a client. I've tried to deter them from it but this is what they really want. They plan on having multiple stores on different servers write to one single database.

So, they *say* they want "different stores writing to one database".

But does that really mean they actually need different *stores*?
Or just different visual presentations of the stores? ie: maybe just "looks like" different sites?

Why *exactly* do they think they want different "stores"? What *exactly* do they mean by that?

(You already said that all the products are the same ... so really it's not different stores as far as I can tell from what I've read thus far.)

[ecomuser2010]

They want one master store. Say for example they have 5 other stores with 5 products in each (all different), they want 1 master store with 25 different products in it that they run all the transactions through and write to that 1 database.

I know, it's strange. They're way more successful than I though, so who am I to question.