As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Interested in some opinions on whether SQL is becoming obsolete. At my place of work, ORMs (in particular, Doctrine) are growing more popular for our web dev projects, and early indications seem to be suggesting that it's capable of doing pretty much everything we need for these small to medium sized apps (haven't yet had any major reporting requirements though). Is this the future of data modelling for web dev projects? (Apologies in advance if this is not the forum for this type of question).
SQL is not obsolete nor is it becoming so. There are plenty of programmatic interfaces that make it less of a requirement to learn it in the early stages of application development, but nothing replaces good knowledge about it.
It is also interesting to note that several NoSQL backends support a subset of SQL as an interface to them. It will be a long time before it goes away.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
At the moment, I write a WCF Service that gives the following functionality:
Videoupload and -download
Usermanagement
Groupmanagement
Filemanagement
A forum
Presencemanagement
As database I use a SQL Server 2012 from Microsoft.
The service gets called via REST, so this would not be the problem.
My question is, what advantage can I get with node.js or better said, is there any advantage?
The biggest advantage is in my point of view, that I am fully platform indipendent. Are there any other advantages?
Greets Knerd
Update, I posted a new question here https://softwareengineering.stackexchange.com/questions/188926/migrate-wcf-to-node-js
You get the usual advantages and disadvantages Node.js has.
I.e.:
Platform independence
Everything is asynchronous
You have the same language for the backend as for the HTML frontend
...
Basically, the question whether you can benefit from Node.js IMHO comes down to whether you need to scale pretty much, and if you have lots of I/O to do.
If the answer to both is 'yes' then Node.js may be a pretty good catch for you.
PS: Completely off-topic, but - are you Knerd from the discussion forum of winfuture.de?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Note: I have been out of touch with the PHP world for quite a long time. I am primarily a Python developer.
I have to build a small app in PHP5. Please suggest me a lightweight framework which:
Has MS SQL Server Support that runs on Linux as the app will be running on Ubuntu.
Is fast to learn, use and setup.
Performance is not a critical issue. As the app will be used on a private LAN by about 10 people for data entry mainly.
Suggestion about a templating engines will also be appreciated
Regards
Let's kill off the easy question first - by tempting, I'm assuming you mean templating. If so, Smarty is usually a very good contender as it is simple to learn and very powerful.
Now, for the framework. A wide variety of PHP frameworks have switched to PDO for SQL requests, which means that most of them will easily accomodate MS SQL. CodeIgniter does, so does CakePHP last time I checked.
Ultimately, pick what you know rather than picking something that looks fancy, unless you need the extra features. The learning curve will be smaller.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
In this day and age, with a new NoSQL databases popping up every weekend..
Are there any good and up-to-date resources on how to pick a database(s) that will suit your web application needs?
If you're interested in trade-offs and feature comparisons Wikipedia tends to be updated more than others.
Relational Database Comparison: http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems
NoSQL Feature Comparison: http://en.wikipedia.org/wiki/Comparison_of_structured_storage_software
If you want a more direct answer you can always post the requirements you have and you'll get a lot of helpful answers. It's a pretty broad subject and, other than feature comparison matrices like the ones above, you'll mainly get subjective answers unless you have an objective question (ie specific requirements).
Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Membase vs Neo4j comparison
NoRAM DB => “If It Does Not Fit in RAM, I Will Quietly Die For You”
Although I would also advise considering a SQL data back end ( e.g. PostgreSQL, Drizzle ) with a cache layer, e.g. Redis on top of it. Unless you have an actual reason to use NoSQL. The reason can by the way be NoSQL is cool and I'd like to learn it, but if that is all, usually it may hurt at the end.
Does the problem have to do with money transactions? Are you going to have a distributed system?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I've been learning PHP OOP for quite a while and I've loved getting to know the language, finding solutions to problems and so forth.
Although, quite often, people keep recommending different frameworks for me to start using. I can imagine using a framework is more efficient, time effective and so forth but It seems to take quite a lot of the fun out of things.
My next challenge is to create a fully functional tutorial website and blog.
My question is, do you use a PHP framework and should I really start using one?
I was also debating whether to use CodeIgniter or CakePHP...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 13 years ago.
I recently got interested in web development coming from kernel based applications. I am curious to what the best development environment and language that one can use to build a nice looking website. I have a distant familiarity with PHP, CSS and the like but I am comfortable with HTML.
To be perfectly frank: it doesn't really matter.
As long as it produces useful HTML, CSS, and perhaps JavaScript, you can have a beautiful website (and you can also produce bad websites!). The development environment is purely a matter of taste for the programmers.
As long as you are disciplined and attack the project with a plan, know a good designer or two, and have the will power to see it through till the end, you'll be successful.