issues
search
SEAPUNK
/
jobber
Simple job queue.
1
stars
0
forks
source link
idea tracker 2: architecture nightmare boogaloo
#10
Open
SEAPUNK
opened
8 years ago
SEAPUNK
commented
8 years ago
Things to keep in mind when building this thing:
[ ]
THE
SERVER
STORE IS THE SOURCE OF TRUTH AND ATOMIC OPERATIONS
[ ]
THE STORE IS JUST A PERSISTENCE LAYER
[ ] All-atomic operations where it counts
[x] Server API architecture: #7
[ ] Fault tolerance: #9
[ ] Server listeners (external APIs): #10
[ ] How the runner "registers" its runs: #8
[x]
XBPF requirement
Merging of jobs: #4
[ ] Alternative job data formats: #3
[ ] Timeouts: #12
[x] Job ID generation: #1
SEAPUNK
commented
8 years ago
Job is one task, it will only ever have one runner at the same time.
SEAPUNK
commented
8 years ago
Design for only one server, and one store at a time, and one API at a time.
APIs to keep in mind while designing: Local, REST, WebSocket
Stores to keep in mind while designing: Memory
Don't think about Redis and SQLite stores just yet. You need to get up close and personal with them before using them.
Things to keep in mind when building this thing:
SERVERSTORE IS THE SOURCE OF TRUTH AND ATOMIC OPERATIONSTHE STORE IS JUST A PERSISTENCE LAYER