Note that there are some explanatory texts on larger screens.

plurals
  1. POStored Procedure VS. F#
    primarykey
    data
    text
    <p>For most SP-taught developers, there are no option between Linq and Stored-Procedures/Functions. That's may be true. </p> <p>However, there are a road junctions nowadays. Before I spending too much time into syntax of F#, i would like more inputs about where the power (and opposite) of F# lies.</p> <p>How will F# perform on this topic (against SP)? </p> <p>F# have to communicate with a database on some way. Through Linq2Sql/Entity-app-layer or directly though AnyDbConnection. Nothing new there. But F# have the power of parallellism and less overhead in thier work (<a href="http://geekswithblogs.net/akraus1/articles/79880.aspx" rel="nofollow">Functional Programming with C#/F#</a>). Also F# has it's effeciency as a layer for data and machine. Pretty much like C# power of being a layer between human and machine.</p> <ul> <li>Would I really still let the DB Server handle a request of recurring nodes, or just fetch plain data to F# and handle it there? Encapsulated nice and smoothly as a object method call from C#? </li> <li>Would a stored procedure still be the best option for scanning 50 millions of records for finding orphans or a criteria that matching 0,5% of the result?</li> <li>Would a SP or function still be best for a simple task as finding next parent node?</li> <li>Would a SP still being best to collect a million records of data and return calculated sums and/or periods?</li> </ul> <p>Wouldn't a single f# dll library fully built on the Single responsibility principle being of more use then stored procedures hooked up inside a sql server? There are pros and cons, of course. But what are they?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload