Logging Analyser

Go to file

Denis Knauf c6ff411ae1 bin/logan: Proof of Concept, but it looks nice. CStruct: I do not know. It is not what i want. bin/box.rb: $SAFE-tests.		2010-02-26 01:57:26 +01:00
bin	bin/logan: Proof of Concept, but it looks nice. CStruct: I do not know. It is not what i want. bin/box.rb: $SAFE-tests.	2010-02-26 01:57:26 +01:00
lib	bin/logan: Proof of Concept, but it looks nice. CStruct: I do not know. It is not what i want. bin/box.rb: $SAFE-tests.	2010-02-26 01:57:26 +01:00
AUTHOR	CStruct: first test	2010-02-24 15:04:56 +01:00
LICENSE	CStruct: first test	2010-02-24 15:04:56 +01:00
README.md	bin/logan: Proof of Concept, but it looks nice. CStruct: I do not know. It is not what i want. bin/box.rb: $SAFE-tests.	2010-02-26 01:57:26 +01:00
Rakefile	CStruct: first test	2010-02-24 15:04:56 +01:00
VERSION	CStruct: first test	2010-02-24 15:04:56 +01:00
logan.gemspec	bin/logan: Proof of Concept, but it looks nice. CStruct: I do not know. It is not what i want. bin/box.rb: $SAFE-tests.	2010-02-26 01:57:26 +01:00

Status

Proof of Concept!

Derzeit lote ich nur aus, was alles benoetigt wird.

Sicherheit

Verarbeitung wird jeweils abgeschottet und darf nicht auf andere Daten zugreifen. $SAFE = 4

Liest aus der Queue, verarbeitet und schreibt in eine andere Datenbank.

Eine DB, die speichert, wer an was arbeitet. Koennte langsam werden.

Woher kommt die Information, dass gearbeitet werden kann? Queue/Stream/im Prozess.

MapReduce hintereinander gepipet. Queue/Stream simpel, wenn jeweils ein Prozess/Thread zustaendig ist. Ein Prozess komplexer.