You kind of need to provide a bit more detail in what you are looking for. Back end of what specifically? Its like..the back end of a car is different from the back end of a truck. Best example coming to mind atm. lol.

Hahaha good point.

It's effectively going to be a site relatively similar to [link] except for clothing and clothing designers only. So you'll have the login system for buyers and sellers, sellers will be able to upload their clothes, buyers will be able to view and buy (I'll be getting a third party shopping cart system and integrating that in - I ain't gonna code that stuff), sellers will be able to create their own 'rofiles' - a single page where they can say who they are and what their insiration for designing clothings is etc etc. Also a 'favourites' system for products and buyers.

That's just a brief overview, and I'm coming up with more things daily.

I also get the feeling I may have bitten off a lot.

--
I am random, not insane.

There's a difference?

...No, not really.

When you stop coming up with more things, then ask us how to do it.

But, as a ballpark, you'll want to be looking at either PHP/.NET/RoR/Python/Perl for the back end work horsing, SSL for financial transactions, and a damn good lawyer to come up with a usage policy that will cover you incase things between buyers and sharers go pear shaped.

--
_{The DataGrid control is intended for viewing data, and not as a layout tool like an HTML table - Adobe}

I need to start learning so I can get onto the creating I'd imagine as I learn more, I'll encounter more new useful things I can do so by the time I'm actually capable of creating something that isn't a pile of mush I'll have more ideas than I started out with.

I've also had PHP/MySQL combo suggested to me for this. Which would you suggest would be a good starting point?

Lawyers are easy, I work at one of the top commercial law firms in New Zealand I've got the legal side of things down set, it's all the rest that's a bit pear shaped.

--
I am random, not insane.

There's a difference?

...No, not really.

I would strongly discourage you from using MySQL and point you instead to PostgreSQL, PHP is ok.

--
_{The DataGrid control is intended for viewing data, and not as a layout tool like an HTML table - Adobe}

Ah, brilliance

I shall start poking around 'beginners guides'

Thank you very much for your good advice!

--
I am random, not insane.

There's a difference?

...No, not really.

Well, lot of sites work fine with MySQL... Not sure how PostgreSQL is better.
Anyway, a potential good start for an e-commerce seems to be Magento, which use more modern code (Zend Framework) than osCommerce and derivatives.
Perhaps somebody has other advices. There are lot of e-commerce engines available, but not much really usable.

--
82% of statistics in signatures are made up. (This is a recursive signature...)
Spreading them is un-original and sheepish. If you agree, copy this in your... wait, no!
No to signature clichés! You are on an art site, be creative!

One big reason why PostgreSQL is better is because it supports both full-text indices and transactions. MySQL does support each one of the individually, but not both of them at the same time; InnoDB supports Transactions, but not full-text indices, while MyISAM supports full-text indices, but not Transactions.

In addition to what `summaro has said you need to sit down and read the PCI DSS regulations extensively if you plan on doing eCommerce.

--
_{Crudelius est quam mori semper timere mortem}