Database Driven Website, C# front-end F# back-end meaning?

Question

4.00/5 (1 vote)

See more:

, +

Hi I am an intern working with ASP.NET.

My current task is to make a website which will incorporate some jquery viewing features. This project seems to me will be primarily dealing with reading data from a database and making graphs out of them. This will require me to make custom queries from whatever the client is looking at. I think it is going to be what this guy calls an Ad Hoc Query tool

My plan for this is to make it a database-driven website. So I can utilize the jquery dynamic viewing capabilities. I stumbled upon the functional programming paradigm and found F#. I read that because of it's functional programming paradigm, it makes it a good language to do asynchronous functions. I read about how you can use this with LINQ to SQL and how easy it is to make queries without actually putting the query language in. I understand the concept of the MVC design pattern.

But I don't understand what they mean about C# being the front-end and F# being the back-end. Can someone clarify this to me? Also what are your thoughts about doing this project in this way? Any comments and thoughts are greatly appreciated. I feel as if learning F# will be a great learning experience for me.

Posted 21-Jun-12 6:06am

Member 8336910

Updated 21-Jun-12 6:19am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

db7uk · Accepted Answer · 2012-06-21T10:05:00

I too am a little confused regarding the front and back end language choice.

The only thing I can think of is that you could have a website written in C# and maybe a class library / service (more likely service) that is F# providing functional aspects to the site.

In terms of asynchronous behaviour, it appears that the F# language does provide the asyc methods that are to be released to c# and vb.net in .net 4.5. So in terms of asyc at this point in time f# is probably better but, the question is, does the website you are creating really need a functional (declarative) programming language?

At this point in time, c# and vb.net use the normal .net threading methods and in .NET 4 with TPL (Task Parrallel library). TPL is fantastic and really does provide easy to use and understand threading mechanisms that can provide asyc behaviour.

f# is something I am yet to learn but to be honest for most websites, c# will be enough to deal with.

So with that in mind, I would (in your situation) focus on MVC, C#, with Linq to SQL or Linq to EF.

hope any of this helps.