Servers, buckets and queues: Perbedaan revisi
(→Queues) |
|||
| Baris 34: | Baris 34: | ||
==Buckets== | ==Buckets== | ||
| + | |||
| + | =====com.isikhnas.queuefiles===== | ||
| + | |||
==Queues== | ==Queues== | ||
| Baris 47: | Baris 50: | ||
**origfilename: the name of the file as sent in the email | **origfilename: the name of the file as sent in the email | ||
**userid: iSIKHNAS internal ID of the sending user | **userid: iSIKHNAS internal ID of the sending user | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revisi per 13 Agustus 2014 13.35
Daftar isi
Servers
Master database server
- db.isikhnas.com
- Single instance (not elastic)
Slave database server
- Hot standby server, with automatic promotion to master in case of failure
- .isikhnas.com
- Single instance (not elastic)
Database read-replicas
- .isikhnas.com
- Elastic
- Used for analysis and generating output reports
Master web server
- testwww.isikhnas.com
- Elastic - needs re-imaging when modified
Messaging server
- mx5.isikhnas.com
- Single instance (not elastic)
- Manages incoming and outgoing email, sms, Instant messaging
Report processing server
- .isikhnas.com
- Elastic - needs re-imaging when modified
- Processes database reports, against read-replicas
Template server
- .isikhnas.com
- Single instance (not elastic)
Buckets
com.isikhnas.queuefiles
Queues
emailinput
- Purpose: Send a message from message server to report server to notify of
- Push: message server, email_parser.py
- Pop: report server, emailinput_processor.py
- Message content
- to: incoming email 'to' address (an @isikhnas.com address)
- from: sender's email address
- filename: the GUID filename on the S3 server (just name and extension)
- origfilename: the name of the file as sent in the email
- userid: iSIKHNAS internal ID of the sending user