Hi Tom On 1/22/07, Tom Benson <[EMAIL PROTECTED]> wrote:
Primarily I develop in house business systems. They are single server, with between 5 and 500 (and normally a growing number) users accessing the database, all with persistent connections because any changes one user makes need to be immediately reflected in the clients other employees are using. They could be accessing it from the local LAN, through a frame relay or other WAN, Secure Tunnel or other wise externally. MySQL give me the ability to do this for a single, one off payment of 250 Euro. No subscriptions, no other payments EVER. I don't have to consider how many people will be using my solution when I sell it, ever.
On this basis I think its roughly comparable to Valentina. As an aside, you can also be a MySQL developer partner for 2000 Euro
annually. This allows you to distribute as many installations as you like during each paid year, and those solutions will NEVER need to be licensed. Even if you choose not to renew your license, any installations you completed while your license was valid will never need to be licensed. So you can see, because I'm serving an arbitrary (undefined) number of clients from my server, MySQL offers the better deal for me.
Ive been doing some research into this after talking with some others who have been in contact with MySQL. They do not list all options on their website, but instead want to know about your project, then lock you into a plan that they can estimate your needs and ability to pay and what the long term value of the relationship is. MySQL has several options, including a Classic and Pro option. My understanding is that the most flexibility is with the Classic version which is not really updated. When we have a large volume customer who knows they are going to have large sell throughs, we work out a plan for them. But when we do that its for our current, updated product. In your case, I think they've established a buy in price for you and their own willingness to risk on an annual basis. My guess though is that MySQL is content with the notion of using Classic because later they are hoping to get direct upgrade revenue from your customer and by-pass you. That is a common enough tactic in infrastructure product companies. In that respect, they compete directly with their customer: you the developer. At the end of the year (however long they give you on that agreement), they can acquire your customer easily enough. That is exactly what we dont do - our Embedded Server is customizable enough that it doesnt need to look like a Valentina database. We dont need to acquire/compete our customer's customers. Best regards, Lynn Fredricks President Paradigma Software, Inc Joining Worlds of Information Deploy True Client-Server Database Solutions Royalty Free with Valentina Developer Network <http://www.paradigmasoft.com> http://www.paradigmasoft.com _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
