Apathy is the suck. Login and vote now.
By alashcraft
via dotnet.dzone.com
Published: Jan 19 2009 / 08:02
For a while now, I’ve held the opinion that the “sweet spot” for functional languages on the JVM and CLR will be in the services space, since services and functions seem pretty similar to one another in spirit—a given input produces a given output, with (ideally) no shared state, high concurrency expectations, idempotent processing, and so on. This isn’t to say that a functional language is going to make a non-trivial service trivial, but I think it will make it simpler and more likely to scale better over time, particularly as the service gets more complicated.
Tweet
SaveShareSend
Tags: .net, how-to, other languages, web services
-
Google: Bigger Than a Country [Infographic]
-
Reach Higher Scalability from your Web Applications Tuning vs. Adding Additional Hardware
-
Linux Kernel Update Beefs Up Security and Graphics Support
-
Process Debt and Team Scalability
-
jQuery.mobile.lazyloader - A Proper jQuery Mobile Widget For Lazy Loading Listviews - Functionn
-
Introducing Apache Hive Query Patterns
Add your comment
