Database and Server
Hey, I'm about to start working on a program that will be managing a rather large database on a server, as well as setting up a client GUI to access it remotely. What would be the best language to use to write the server-side program? What would be a good database to use, postegre? And what language for the client? Pros/Cons/opinions appreciated :)
Well I'm rather biased =]
I'd say c++ all the way- for all of the things.
For the database- I have no experience in databases, so someone else would have to lend a hand there.
I'd say c++ all the way- for all of the things.
For the database- I have no experience in databases, so someone else would have to lend a hand there.
closed account (1yR4jE8b)
If the server is going to have a lot of concurrent connections, SQLite is crap.
If you're using MySQL on the server side, then I'd say try either C++ or even plain C with the appropriate bindings for the server-side software. For the client, I'd use Python: the language bindings for mysql are solid and it's very easy to get an application up and running real quick. If you're interested in making a Web Application then Django would be a good choice of Web Framework for the front-end.
If you use Microsoft SQL Server, I'd use C# on both ends.
I don't know too much about PostreSQL other then I've heard that it is excellent, but I don't know how well it is supported by programming languages.
If you're using MySQL on the server side, then I'd say try either C++ or even plain C with the appropriate bindings for the server-side software. For the client, I'd use Python: the language bindings for mysql are solid and it's very easy to get an application up and running real quick. If you're interested in making a Web Application then Django would be a good choice of Web Framework for the front-end.
If you use Microsoft SQL Server, I'd use C# on both ends.
I don't know too much about PostreSQL other then I've heard that it is excellent, but I don't know how well it is supported by programming languages.
You have alot of options and the right type of database depends on your needs and your monetary situation.
MySQL:
- Free and opensource
- You can use existing software such as phpMyAdmin to manage your database. Again free.
- C#, VB, PHP, Java, and many other languages have APIs for accessing database
- Packages, bodies, and spec I find still need developing. No where near as good as SQL Server
- Indexes, rollbacks, commits, etc need more development.
SQL Server:
- $ and very expensive
- For what I've heard, very very easy to manage with tools MS gives you.
- I've also heard that T-SQL is better than PL/SQL but I have never written a package in T-SQL or worked with SQL Server
- C#.NET or VB.NET
- Good support for rollbacks, commits, indexing, optimizing, etc.
Oracle:
- $ and very expensive
- Almost all languages have libraries.
- Good support for rollbacks, commits, indexing, optimizing, etc.
MySQL:
- Free and opensource
- You can use existing software such as phpMyAdmin to manage your database. Again free.
- C#, VB, PHP, Java, and many other languages have APIs for accessing database
- Packages, bodies, and spec I find still need developing. No where near as good as SQL Server
- Indexes, rollbacks, commits, etc need more development.
SQL Server:
- $ and very expensive
- For what I've heard, very very easy to manage with tools MS gives you.
- I've also heard that T-SQL is better than PL/SQL but I have never written a package in T-SQL or worked with SQL Server
- C#.NET or VB.NET
- Good support for rollbacks, commits, indexing, optimizing, etc.
Oracle:
- $ and very expensive
- Almost all languages have libraries.
- Good support for rollbacks, commits, indexing, optimizing, etc.
Last edited on
What would be the best language to use to write the server-side program |
The language you are most comfortable with.
Topic archived. No new replies allowed.