mf4dl1 / jaksafe

JakSAFE - InaSAFE feature to support DaLA for Flood
https://bitbucket.org/irisiko/jaksafe
GNU General Public License v3.0
0 stars 1 forks source link

RFC: System Architecture #4

Open mf4dl1 opened 9 years ago

mf4dl1 commented 9 years ago

General Overview

3 architecture

Requirement

jj0hns0n commented 9 years ago

Lets consider to use a message queue to control the AUTO jobs in the Web Based Interface. Look at how InaSAFE realtime is handling this. Perhaps use http://www.celeryproject.org/ @timlinux can you shed some insight on your methodology.

timlinux commented 9 years ago

We currently arent using celery / a message queue in realtime since the quake reports are generated using a separate service in and pushed over to the realtime site in the new architecture (and generated as static pages in the old).

We are using celery in other projects - you can see an example here if you are interested:

https://github.com/kartoza/watchkeeper

And I would be happy to adapt InaSAFE realtime to use celery where needed.

jj0hns0n commented 9 years ago

@timlinux are you just using a database queue or something like rabbitmq?

timlinux commented 9 years ago

For current realtime implementation we have:

Its very simple but pretty bullet proof

In the new architecture we are working on right now we will have:

In the future we plan to extend the system to do more hazard types and we will most likely provide for a mix of approaches, so if you want to you can write an app for the django project that listens for events e.g. from a GeoRSS feed and then triggers a process request on an event queue.

@lucernae is the developer working on current implementation for realtime, so feel free to chip in here Rizky