Difference between revisions of "Real World Applications"

From HaskellWiki
Jump to navigation Jump to search
(Additional enterprise wording.)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Introduction ==
 
== Introduction ==
   
It is not always clear how to scale up from small "batch oriented" Haskell applications to large scale "Real World/Enterprise" Haskell systems. In other words, how to create large-scale systems that support business processes, information flows, reporting, data analytics etc. using Haskell.
+
It is not always clear how to scale up from small "batch oriented" Haskell applications to large scale "Real World/Enterprise" Haskell systems. In other words, how to create large-scale systems that support complex business processes, information flows, reporting, data analytics etc. using Haskell.
   
The following articles discuss different ways to attack this problem.
+
The following articles show how to attack this problem.
   
 
== Event Driven Applications ==
 
== Event Driven Applications ==
   
An event driven application/system is here defined to be an application/system that reacts to external events.
+
An event driven application/architecture is an application/architecture that is driven by internal/external events. Most non-trivial applications/architectures (from Operating Systems to Web Servers and Enterprise applications) are event driven.
   
 
Read this: [[/Event Driven Applications/]]
Examples would be:
 
 
* A text editor that reacts to user events (key pressed, mouse moved).
 
* A web server reacting to IO events (message arrived, image compression done).
 
* A commercial game reacting to simulated physics events and user input.
 
 
More here: [[/Event Driven Applications/]]
 
   
 
== Your Contribution Here ==
 
== Your Contribution Here ==

Latest revision as of 14:09, 2 July 2014

Introduction

It is not always clear how to scale up from small "batch oriented" Haskell applications to large scale "Real World/Enterprise" Haskell systems. In other words, how to create large-scale systems that support complex business processes, information flows, reporting, data analytics etc. using Haskell.

The following articles show how to attack this problem.

Event Driven Applications

An event driven application/architecture is an application/architecture that is driven by internal/external events. Most non-trivial applications/architectures (from Operating Systems to Web Servers and Enterprise applications) are event driven.

Read this: Event Driven Applications

Your Contribution Here

Please contribute additional/alternative ways to structure large scale Haskell applications here.

Questions and feedback

If you have any questions or suggestions, feel free to mail me.