Online Store Precautions

szym9341

I am developing a php/mysql clothing store... Should I use three different databases?? (1- Online Stock 2- Customers 3- Customer Orders)... What are some security issues that I need to consider at this beginning stage? (I have my tables drawn up and normalized in 3NF).

Pig

I'm not trying to be a jerk, just pointing out a serious issue. If you don't know enough that you have to be asking such broad questions, then you have no place handling someone's credit card. There are gobs of scripts out there, many of them free.

szym9341

I realize that my question is quite broad... When I have the databases and pages built, and I am ready to start implementing a shopping cart... then I'll use those scripts... I feel like an idiot asking my question, but I need to start somewhere. I guess a better question would be, "What keywords should I learn about when developing an online sales page?"

ultraslacker

Transactions, for one. SSL too. Normalization, which you know is a keyword. Surely there are plenty of shopping cart tutorials.

I'm with Pig on this - the project is ambitious and you have considerable groundwork in front of you, as your question shows. Do it right and learn the technology thoroughly. I hope you do not have a deadline.

For your question - what would be the pros and cons of one database versus three?

szym9341

I have more time than necessary... well, an undisturbed 35 hours a week for leraning and planning. In, say, 4 months from now I would like to have a prototype...

Thanks for the direction of shopping cart tutorials, SSL, and transactions...

Am I correct with these assumptions? Are they worth considering during my planning stage?:

(One) Database PROS: Speed, Simpler code...
(One) Database CONS: Can't Store Data on Different Servers..

(>One) Database PROS: Possible different server storage, Create modular dB's on the fly if needed for future projects, Separate security for each dB (administrator vs public pages)

(>One) Database CONS: Multiple Connections (slower?)

szym9341

If I develop the whole site as a prototype just for testing the flow of data and visual aesthetics (between administrator page, public, and shopping cart) first...

Will I run into any major changes that need to be made to my code and dB/Tables when I start implementing transactional security for public use?