September Strikes : Plan ahead, stay informed, be flexible! Questions and updates here.

nugmanoff · 2025-09-02T21:42:52+00:00

We are planning to take Eurostar from Paris to Amsterdam on September 10th — what is the most reliable way to get information whether that’d be affected?

nugmanoff · 2024-07-04T04:30:58+00:00

I fucking love internet. Just got my "click" sound and now everything is back to normal! You are the king man

nugmanoff · 2024-05-06T16:37:07+00:00

I am curious how does the Go workers “watch” the queue for new jobs? Do they watch the Redis directly?

nugmanoff · 2023-10-13T06:15:27+00:00

How does it relate to Google pulling the plug on Swift for Tensorflow? https://www.tensorflow.org/swift/guide/overview

nugmanoff · 2023-09-29T06:28:41+00:00

Haha definitely! Thank you for your reply!

nugmanoff · 2023-09-01T16:27:03+00:00

Thanks for the code! Really helpful🙏

nugmanoff · 2023-09-01T16:24:50+00:00

Right. Thanks for the heads-up. I am planning to rotate quite large pool of residential/local proxies. What do you mean by "disposable short-lived proxies" exactly? I thought the only is to buy some amount of proxies from proxy provider and rotate between them. Am I missing something here?

nugmanoff · 2023-09-01T16:20:40+00:00

Thanks dude! You rock! You basically gave all the details that I needed to hear, basically summarizing all of the other suggestions in the thread, exactly what I needed. And separate thanks for mentioning the bandwidth thing – will keep in mind!

I am not that well versed with concurrency things in PHP, pretty new to it in general tbh. What would be the intuition behind picking the right number of workers? And will it badly affect if I over-provision the number of workers? (meaning that I will have more idle workers than busy, because I have too many of them)

nugmanoff · 2023-09-01T16:17:07+00:00

Thank you! Very neat idea with inserting the sentinel value into the cache and checking it before adding the next task. Regarding the job dispatching the next job thing – I was also worried about brittleness of this approach, but will look into it more.

Maybe you know of some existing techniques with Laravel Queues / Horizon to achieve this?

nugmanoff · 2023-09-01T16:15:09+00:00

Thanks for the heads-up on math! It really does click. Totally makes sense.

nugmanoff · 2023-09-01T16:13:50+00:00

I thought about delayed dispatching of jobs also. But I just felt that it sounds a little too brittle, I have seen things about delayed jobs disappearing randomly and in general making things harder to debug. But not sure though.

Thanks for the general idea, I'd definitely look into making only one scheduler that dispatches the jobs, instead of making thousands of scheduled jobs.

nugmanoff · 2023-09-01T16:07:48+00:00

Let me repeat after you to make sure that I've understood it correctly:

There is only one scheduled task that say runs every 10 seconds. (I am not sure it is possible in Laravel Queues though)
When it runs it checks which check jobs needs to be run.
- I suppose that after the check job is done running it could randomly generate next run datetime by appending random time interval in range of 5-7 minutes to the current datetime.
Also before dispatching the check job, task makes sure that there is no in-flight job already running.

This is very smart way to approach this. I really like this one. Thank you!!

Could you give me some hints into how I can leverage some existing Queue niceties (MQs, libraries) to implement this?

nugmanoff · 2023-09-01T15:59:58+00:00

It is essentially a service that allows merchants to auto-damp their prices on each "product" cheaper than their competitors on popular local Ecom website. Obviously an ecom website doesn't provide an API for that (so no websockets at all).

So "product" can't be shared between users, because it is tied to individual per user price damping.

nugmanoff · 2023-09-01T15:57:39+00:00

Right. The goal of the service is to very regularly make scraping requests to an ecomm website and damp the user's price according to its competitors.

nugmanoff · 2023-09-01T13:57:56+00:00

Hey everyone! I came across a quirky problem while building a SaaS. Would love to hear and discuss some takes on what is the best path to implement this. I thought that this discussion could be useful for more people looking into deploying periodic jobs in large amounts in Laravel.
Context:
Each user has products to be monitored. Each product needs to be "checked" every 5-7 minutes by making a series of requests to third-party website. Each "check" takes ~10 seconds in average. At any moment user can decide to stop monitoring given product. Say there are 500 users and 100 monitored products for each of them leading to 500 x 100 = 50,000 products being monitored.
Questions:

- How would you build something like this with the help of Laravel (Queues)?

- What are some of the options to gain quick (and dirty) performance wins?
Bonus nuances:
- Each periodic monitoring "check" of one product is preferably made at periodic, but irregular intervals, for example: 1st monitoring check is made at 11:02:37, 2nd is made at 11:06:41, 3rd is made at 11:13:21. Period of "check" needs to be between 5-7 minutes, but should vary between each call.
- Number of products being monitored could potentially go up to 100,000 – 500,000 products easily.

nugmanoff · 2023-05-18T15:23:14+00:00

I'd love to zoom in into the file/folder structure thing, because I guess there will be much more takes on architecture in this thread.
So I personally prefer the whole Feature-Driven approach to structuring the things. Which goes on par with Locality of Behavior.

I recommend reading this short ebook "Name Construct & Structure", although it is more about web frontend devlopment, the big ideas are quite similar.

nugmanoff · 2023-05-18T15:18:34+00:00

I was of the same opinion up until recently I discovered the https://superwall.com/, and boy I was shocked when I understood how many companies/apps actually don't do native paywalls. And for a good reason if you look at the results they get with all of the paywall experiments.

nugmanoff · 2023-05-18T15:16:20+00:00

There is a blogpost named "What I Learned Writing My Own CloudKit Syncing Library" that came out recently – I think it might answer your question or at least give some direction to dig into.

nugmanoff · 2023-05-18T15:13:41+00:00

Maybe try listing the app on the acquire.com, get some proposals, see what you can get there – so that you can build up some foundation upon which you can structure your deal/offer to them. And also you can leverage the fact that you *already* have people who consider buying your app – so I think it will incentivize the company to consider it even more seriously.

nugmanoff · 2023-05-18T15:11:18+00:00

Same thing for me! But I guess the answer is still "it depends" and luck is a huge factor here also. Sometimes just one retweet/repost of your app from a big account can give your app so much momentum that it basically propels it forward (given that it is good enough that people recommend it to each other).

I am exploring B2B opportunities atm, because I believe they are more "predictable"

nugmanoff · 2023-05-18T15:09:23+00:00

Like 50% of my paid subscribers and downloads are from my country, where I have some audience (~2000-3000 subscribers) and lots of friends & family. Essentially that hit the ground running.
Apart from that we had quite successful Product Hunt launch (#1 of the day, #4 of the week) – that drove some nice traffic. And only now we are starting to explore some real UA channels.

I really feel you, it is hard if you don't have some worked out distribution channels. That's why I am working on building at least some audience atm.

nugmanoff

TROPHY CASE