I am planning on setting up a service / web application for clients and I’m just wondering which backend platform will be best for my needs.

The client would register for the service; I would need to store some client data in a database. it would be roughly 2000 records per client.

I would need to give the client access to these records (to edit remove or add new records) what would be the best way to store these records? Maybe a table per client?



At a later stage I might want to be able to allow clients to create multiple logins, these new users will have access view specific records, but no edit access.

Do you think Mysql on a Linux server would be a good option?

Yes, I think MySQL on a Linux will be a good option.
I strongly recommend against using a table per client. That would be unpractical and inefficient. For one, you'd have to create a new table for each client.

You should create a table for holding clients info (username, password, etc). Table holding records for them should be referencing the client table.

You can use PHP as an interface the database.

Yes, I think MySQL on a Linux will be a good option.
I strongly recommend against using a table per client. That would be unpractical and inefficient. For one, you'd have to create a new table for each client.

You should create a table for holding clients info (username, password, etc). Table holding records for them should be referencing the client table.

You can use PHP as an interface the database.

I back him :agree:

I agree with Akkai, too.

MySQL can handle a large number of data and scale without problem. And PHP is very easy to learn. And since both PHP/MySQL run on different operating systems, you are not locked in one platform (like windows for example if you follow mssql, asp route).

You can invest some time to learn a framework (like zend), and build the service with a framework that will do the common things for you or even create a module for a popular cms like drupal etc. - you seem not to have basic knowledge of programming and software design, so building this from scratch would be very hard.

Good luck!

I would recommend MySQL or PostreSQL.

When dealing with multiple ownership, you could use a foreign key to indicate ownership/relation to a row. You can also use that to enforce updates/deletions only happen to rows owned by that specific person.

Any platform will support what you need and offer a lot of ways to do it. Using different languages, interfaces and databases. The options you have are extremely broad. Yes, Linux with MySQL would be a great choice, and you could use PHP, Perl, Ruby, Python, C, C++, whatever the server had installed and that you feel most comfortable with. However, the fact you are asking would compel me to recommend you simply contact a qualified developer and get quotes, and tell them of any platform you prefer they offer a quote for, if it matters to you.