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'm new in WCF. In the application there will be CRUD and also some business rules.
Please recommend what should I chose EF or LINQ to SQL?
or WCF Data Services?
To add to Pawel's points:
Use EF. Linq to Sql is mainly in maintenance mode while Entity Framework is in active development.
I recommend exploring EF Code First.
Scott Hanselman has a good intro post on EF Code First.
I'd also STRONGLY recommend Julie Lerman's EF Code First book - it'll help answer many of the questions you may have as you begin development.
Finally, be sure to keep an eye on the Data Access team's blog - EF Code First is evolving VERY quickly and lots of great features are arriving regularly (my latest favorite being migrations in 4.3) :)
HTH.
Use EF. Linq to Sql is mainly in maintenance mode while Entity Framework is in active development.
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.
How deep knowledge of T-SQL do I need to have in order to fully grasp all concepts of EF (Entity Framework)?
To be more precise, currently my knowledge of SQL is not small. I know all the basics very well as well as some intermediate concepts like stored procedures, UDF, trigers etc.
But do I need to know things such as XQuery and XPath, SQL CLR Programming or Catalog Views and Dynamic Management Views to fully understand EF or this is not needed as EF has it's own way of achieving the same thing?
I hope you don't find this question stupid as it will save me some time due to my novice knowledge of EF.
I have to add that I am not a database administrator nor will I be (at least for now) but a .NET developer learning EF.
Basically, you have to know less with EF than without it. It shields you partially from the underlying database technology. You kind of have to accept trade-offs the less you know (worse performance or inelegant design). But you don't need any of the things you quoted:
But do I need to know things such as XQuery and XPath, SQL CLR
Programming or Catalog Views and Dynamic Management Views to fully
understand EF or this is not needed as EF has it's own way of
achieving the same thing?
Because mostly, they are not supported by EF anyway...
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.
I'm exploring options for a PHP5 framework (to migrate old codebase).
Requirements:
High performance (project gets ~10 million daily hits & is growing rapidly)
Popular & mature
Actively developed
Good support of components & web services
What could be the options? Pros & cons.
I'm looking into Yii, Zend. But other options are welcome.
Also we have experience with Ruby On Rails so built-in similar ActiveRecord pattern would be great.
Symfony will be a good option for you. Its somewhat similar to ROR. Now its version 2, which is php 5.3. You can use symfoy 1.4 or so, if you don't wish to choose 5.3. Regarding the performance, you can never expect high performance using any framework. You need to focus on other optimizations like caching, db replication etc.
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.