I heard that MySQL is open source and it is free of charge [....] I wish to use as back end of database applications.
Do you realize that your inquiry is not much different from the classic "I want to photograph nature, and I heard that the Can-kon XYZ101 is on sale for $999; should I buy one?"
Such an inquiry
omits nearly all the
information that should
inform selection & purchase of a camera: How do you plan to use it [
♢]? How much of a
load, quantified as number of exposures made, do you reasonably expect to put on it each month? What's your level of
skill & relevant
experience?
Returning to your computational inquiry, your level of
training or
skill, plus relevant
experience matter quite a lot. What level of
technical support do you expect to need to keep your project on schedule, and to resolve later problems? As a "
back end of
database applications", what
query load do you need it to handle gracefully [
#]? Do you reasonably expect that a
single server will suffice until after you retire from the project (or go to your final reward), or will you need to scale its thruput significantly upward, e.g., distribute processing over a network, incurring the complications of database-
integrity?
Oh! I
almost forgot: Who'll be
paying for development & maintenance of your project?
-------
Note
♢: E.g., keeping the proposed camera at home in a comfy temperature-controlled room, shooting activity at an outdoor bird-feeder thro' a large window; or tromping thro' forests or swamps with a tripod, stalking wildlife that's active mostly in typically, um, sloppy weather?
Note
#: Are there any occasions on which you should expect your database to get cruelly pounded, like the landline telephone system on Mothers' Day, or maybe Amazon on December 20--23?
Topic: MySQL - using for free (Read 1050 times)