I've decided in recent months to create a website that aggregates items for sale from eBay, amazon, social media, blogs, and websites to make the life of a niche consumer much easier. I would like to create a dynamic webpage with price & auction updates. I would also like the items to be organized in category whether size or color. I've been trying FileMaker Pro but have ran into some dead ends. Anyone have any suggestions?
Questions on what database I should run for my website?
- Thread starter Ill Cosby
- Start date
Zapdos
Power Member
- Oct 22, 2011
- 597
- 710
MySQL is the standard relational database for running websites. Wordpress uses it, Magento uses it, vBulletin uses it, Kayako uses it... Hell, even parts of major sites like google, yahoo, bing etc use it.
It's also OS agnostic and allows for easy remote management, anything can be integrated into it with ease. It's one of the default databases practically everything supports.
There are others but starting with MySQL is the easiest, fastest and probably the most efficient for you.
It's also OS agnostic and allows for easy remote management, anything can be integrated into it with ease. It's one of the default databases practically everything supports.
There are others but starting with MySQL is the easiest, fastest and probably the most efficient for you.
Well you got a bunch of options here really...
Firstly, there are many alternatives to mysql. What zapdos is saying is spot on, mysql is a tested solution. A lot would actually depend on what programming language you are using for this. For example, PHP and mysql is a pretty standard solution and it works fairly well. Nodejs and mysql, well not so much. It would still work, don't get me wrong, but the community has taken a liking to stuff like mongodb or couchdb (which have their advantages and drawbacks, just like mysql does).
So if you could provide some more information, we'd probably be able to give you a better answer. Just based on the info that you have provided, I'd suggest you start out with mysql and go from there.
Cheers
Firstly, there are many alternatives to mysql. What zapdos is saying is spot on, mysql is a tested solution. A lot would actually depend on what programming language you are using for this. For example, PHP and mysql is a pretty standard solution and it works fairly well. Nodejs and mysql, well not so much. It would still work, don't get me wrong, but the community has taken a liking to stuff like mongodb or couchdb (which have their advantages and drawbacks, just like mysql does).
So if you could provide some more information, we'd probably be able to give you a better answer. Just based on the info that you have provided, I'd suggest you start out with mysql and go from there.
Cheers
lisper, what kind of other info would you need to help me make a better decision?
i want to make it a dynamic database that would include some auctions which would have to include current price and time left in real time. i would also like to include static listings from blogs and other social media. i would want the database to be edited easily so i can add auctions auctions or listings as i find them.
However, i would like all of these to be organized by size and style.
i want to make it a dynamic database that would include some auctions which would have to include current price and time left in real time. i would also like to include static listings from blogs and other social media. i would want the database to be edited easily so i can add auctions auctions or listings as i find them.
However, i would like all of these to be organized by size and style.
jazzc
Elite Member
- Jan 27, 2009
- 2,964
- 14,717
Choosing the right database is not an easy thing at all for a big project. I 'm not saying your project is big, just stressing how important it is to make right choices.
You are confusing technologies here. A db is just a way to store and retrieve information. Nothing more. All the other things you are saying has to do with the business logic of your program - they are the job of your coder.
jazzc is as always right, a db is nothing more than persistent storage of your applications data. Sorting, retrieval, serving and any other logic is handled by your application. In other words, your application will store and retrieve data from the database and most importantly do something (your application logic here) with that data and present it to you or the user.
Which architecture you pick becomes very important when scaling is involved, handling smaller datasets (for example 100k rows is still fairly small) allows a wider margin of error as far as optimization and so on is concerned. So in your case I'd just go with mysql. Unless again I'm mistaken and you are actually building a massive application here.
It all starts with your programming language of choice (as I've mentioned before), as you would want a db solution that can be tightly integrated into your programming language. Once you've picked a couple of candidates you'll have to take a ton of things into consideration before making your final choice.
At the most fundamental level, you got a choice between an sql and a nosql (not-only-sql) database architecture. Mysql, as you might have guessed, is an sql type database. Whereas couchdb for example takes the nosql approach. The following is all IMHO, but basically, the biggest difference between these two is that an sql solution provides a level of automation whereas a nosql solution, well you are basically in charge of many, many thing manually. These results in a number of benefits as well as drawbacks (as with most things...)
For example, mysql is great as an entry database (not to say that it isnt powerful and couldn't be scaled), as it takes care of a lot of things for you. With a nosql system a lot of those "checks and balances" are removed and it is up to you to set them up yourself. This (again this is all IMHO) allows for generally better scaling and better performance however it's a bit of a double sided gun if you don't know what it is that you are doing exactly.
Again the above description is very, very generalized and there are a great deal of differences between different nosql solutions as well (the same applies for sql solutions too of course). So you should most probably do some further research or consult an experienced developer if you must.
Hope this helps and feel free to drop me a PM if you have further questions.
Cheers
Which architecture you pick becomes very important when scaling is involved, handling smaller datasets (for example 100k rows is still fairly small) allows a wider margin of error as far as optimization and so on is concerned. So in your case I'd just go with mysql. Unless again I'm mistaken and you are actually building a massive application here.
It all starts with your programming language of choice (as I've mentioned before), as you would want a db solution that can be tightly integrated into your programming language. Once you've picked a couple of candidates you'll have to take a ton of things into consideration before making your final choice.
At the most fundamental level, you got a choice between an sql and a nosql (not-only-sql) database architecture. Mysql, as you might have guessed, is an sql type database. Whereas couchdb for example takes the nosql approach. The following is all IMHO, but basically, the biggest difference between these two is that an sql solution provides a level of automation whereas a nosql solution, well you are basically in charge of many, many thing manually. These results in a number of benefits as well as drawbacks (as with most things...)
For example, mysql is great as an entry database (not to say that it isnt powerful and couldn't be scaled), as it takes care of a lot of things for you. With a nosql system a lot of those "checks and balances" are removed and it is up to you to set them up yourself. This (again this is all IMHO) allows for generally better scaling and better performance however it's a bit of a double sided gun if you don't know what it is that you are doing exactly.
Again the above description is very, very generalized and there are a great deal of differences between different nosql solutions as well (the same applies for sql solutions too of course). So you should most probably do some further research or consult an experienced developer if you must.
Hope this helps and feel free to drop me a PM if you have further questions.
Cheers
jazzc
Elite Member
- Jan 27, 2009
- 2,964
- 14,717
Since you are not a coder, your job is to make the master plan - i.e. the specification of the program. What does it need to do in every step? In details, every little piece of user functionality. Remember, the coder is not necesarily into internet marketing. Write it as you would write it for your grandmother to read. The more disgustingly detailed you make the specs, the better your mental health and your pocket will be with be after the interaction with your coder
Another benefit is that with a detailed spec, it will be easier to attract better programmers. You see, it works both ways. You can always get a programmer but good programmers choose their clients as well.
A detailed spec will make sure you don't get long delays due to misunderstandings and ambiguity. When a programmer designs an app, he takes in mind the requirements at hand. Changing the requirements at a later point means two things - either a patch work that will lead to future high maintenance costs or a delay in delivery since things need to be thrown away and get re-implemented.
So, the db, for you as a client, it is not really of your concern. Get a good programmer, give him a great spec and he will let you know if he needs to use something other that the standard mysql.
lisper that was articulated very well, I think mysql is my answer since the database shouldn't be that vast. I already have slight knowledge of SQL language anyway so it shouldn't be that bad THANKS
jazzc- are you saying I should articulate with a coder what I want out of my webpage first, then worry about database design? I already have sketches of my site drawn by hand and some pretty detailed descriptions
jazzc- are you saying I should articulate with a coder what I want out of my webpage first, then worry about database design? I already have sketches of my site drawn by hand and some pretty detailed descriptions
jazzc
Elite Member
- Jan 27, 2009
- 2,964
- 14,717
Yes - your coder is going to design the database anyway - there 's a whole theory behind db design
(example: http://r937.com/relational.html)This is knowledge I already have from work in FileMaker Pro 12, seems like MySQL is very similar. The only thing is I hit a dead end once it comes to hosting this database onto a website (I even already have a raw structure for the database on FileMaker Pro). Maybe my best bet is to just use it as a reference in explaining it to a coder.
Zapdos
Power Member
- Oct 22, 2011
- 597
- 710
Most if not all shared hosting (paid for) has MySQL installed by default and is the only database available. If you wish to use any other you will require a VPS or dedicated server and set it up. All you need to do to access MySQL on the host is to go to the control panel link they sent you, login, go to the MySQL area and add a new user and new database. From there you can use PhpMyAdmin (most likely) and add tables, columns, relations etc.
However, you said you're not a developer/coder. You should not be handling any of this. Make the plan for the site in plain english. Do not give technical specifications such as "I need X, Y and Z table". Your coder should be able to discern the best setup for your database.
However, you said you're not a developer/coder. You should not be handling any of this. Make the plan for the site in plain english. Do not give technical specifications such as "I need X, Y and Z table". Your coder should be able to discern the best setup for your database.
very true because at the end of the day, who ever is developing in the site is going to have to know all of the interworkings of the site to edit. you seem like you know what you're doing, you interested? or can refer to anyone who may be?
Zapdos
Power Member
- Oct 22, 2011
- 597
- 710
I'll have to decline. I'm currently working on a project which takes up all my time. Probably would be out of your price range as well.
To find someone willing to do it, I would contact local development companies assuming you're near a big city. You'll get a personalized experience and won't have language or time barriers. Odesk/freelance is a cheaper solution, but cheaper prices mean lower quality generally. You may also deal with time and language barriers.