Don't want to steal your topic but I had written a lightweight task runner to learn GoLang [0]. Would be great to have your and others' comments. It works only as a Go library.
2. I see you're using a UUID for the primary key on the jobs, I think you'd be better served by an auto-inc primary key (bigserial or identity columns in Postgres) which will be slightly more performant. This won't matter for small datasets.
3. I see you have an index on `queue`, which is good, but no index on the rest of the parameters in the processor query, which might be problematic when you have many reserved jobs.
4. Since this is an in-process queue, it would be awesome to allow the tx to be passed to the `Create` method here: https://github.com/oneapplab/lq/blob/8c9f8af577f9e0112767eef... -- so you can create the job in the same tx when you're performing a data write.
Thanks a lot for the review you did which was much more than i requested. i noted all the 4 comments you did to apply on the package. Thanks again.
Also currently we have Laravel backend and Laravel + Redis + Horizon [0] + Supervisor as a queue runner for our production and it's working fine for us. but would be great to can access Hatchet from php as well which we might switch in future as well.
Another thing since you mentioned handling large work load do you recommend Hatchet as kafka or Rabbit message queue alternative to microservice communications ?
One year ago we successfully migrated to a new version (totally big bang) with less than 4 hours downtime, for us it was version 3 and v1 and v2 (plus a side service) both was working side by side (v2 was a failed migration so they ended up a frankenstein system which some requests goes to v2 and some other to v1 and they put data in each other's databases. yes not a single source of truth for all the data in database) and here are my three cents:
1. Don't - i don't know the size of the software but for us it was lots of works specially at weekends and holidays. after release almost half of the developers quits and the other half were exhausted. totally doesn't worth that.
2. Don't - if its possible to fix and refactor current version please do that. you would thank yourself later. we had 15 months of developments and in the middle of the project we need some features and fundemental fixes for our current version which we ended up another minor migration that we called v2.9.
3. Don't - only do it if you had to and do it incrementally as others suggested. start by building a microservice for most used domain of your application with api backward compatibility (if possible) and even use same database you are already using.
If you can't refactor current version (which i can't understand why) and you insist to have a bigbang migration know the current system well and know every column in the database(s) since you will need to migrate millions of data at the end which is a big project by itself.
we have almost 10m MAU, which would increase in comming months to more than 50MAU. half of this numbers are on our blog which is now running by wordpress but soon we might migrate it to laravel with wordpress backend as an admin panel.
may we consider the other 3% (3.23) as linux as well ?
if so linux total market share is about 10% (including chromeos since you can install linux apps on them as well)
i wish when people talk about Finasteride they always mention it that you won't be able to donnor blood after that. (FDA says you need at least 30 days Finasteride free for doing that)
See "model driven architecture" except (1) that is trademarked, (2) that vision is not quite realized in the standards that have been published, but has come closer to realization in some proprietary projects.
If those ideas were fully realized and brought to the people the impact would be huge.
Thanks for your advise, i get that advise that work on something you can finish from everyone have experience in PhD but then it should be too easy and meaningless i guess (i know even the easiest one would get at least 3 years) and yes i don't want to jump in another black hole (or rabbit hole at least).
Thank you again i would noted that too.
There are two things actually and sadly no one investigate both of them:
1. Is Covid a lab leak ? (which had poor investigation)
2. Could China stop it (Whether its lab-leak or not) in early stages and prevent it from spreading out of their borders ? (which they achieved successfully for other provinces)
work from home is not a problem, even before pandemic many of us had remote jobs and it was great (at least for me). the real issue here is after pandemic we lost every joy we had like seeing family and friends, going restaurant and cafes, doing sports together and etc. trust me you fix your bunt out even if you work from office.
Glad to see that stack works for author, but honestly one man show's shouldn't be multi lingual stacks at all IMO.
for me php (laravel for back and front with blade templates) or js (express and vuejs for frontend) and docker-compose for deploying and developing stuff is fast and enough stack.
[0] https://github.com/oneapplab/lq
P.S: far from being alternative to Hatchet product
reply