https://notes.logicsquad.net/2020/09/22/detecting-a-toc-in-a-word-document-with-apache-poi/2020-09-22T01:28:40+00:00monthlyhttps://notes.logicsquad.net/2019/05/31/using-an-application-load-balancer-for-ssl-termination/https://notes.logicsquad.net/wp-content/uploads/2019/05/alb-setup.pngalb-setup2019-05-31T03:02:28+00:00monthlyhttps://notes.logicsquad.net/2018/10/25/delayed-job-execution-with-quartz-and-elasticache/https://notes.logicsquad.net/wp-content/uploads/2018/10/redis-job-store2.pngApplication structure using RedisJobStore and ElasticacheThe final application structure involves using a RedisJobStore to handle jobs on each node, but note that data storage is offloaded to Elasticache. Job metadata persistence is no longer handled by the node creating the job, freeing up the node to be shutdown (or crash) at will. A job can be created by one node and executed by a completely different node later.https://notes.logicsquad.net/wp-content/uploads/2018/10/ramjobstore.pngFirst phase of migrationThe first step was to migrate each node to submit Quartz Jobs to a Scheduler, backed by a RAMJobStore. Obviously this suffers from the same problems as the original structure, but was an easy way to test Quartz in this setting.https://notes.logicsquad.net/wp-content/uploads/2018/10/original.pngOriginal application structureThe original application structure with respect to handling delayed execution of jobs involved fully self-contained application nodes. Each node was responsible for storing every job it created in-memory, which was both inconvenient and risky.2018-10-25T23:45:52+00:00monthlyhttps://notes.logicsquad.net/blog/2018-10-16T09:49:46+00:00weekly0.6https://notes.logicsquad.net/home/2018-10-16T09:49:46+00:00weekly0.6https://notes.logicsquad.net/contact/https://notes.logicsquad.net/wp-content/uploads/2018/10/person-smartphone-office-table.jpegPlaceholder Image2018-10-16T09:49:46+00:00weekly0.6https://notes.logicsquad.netdaily1.02020-09-22T01:28:40+00:00