640 karma · joined February 1, 2022
A good example is probably IoT. I've heard first hand anecdotes of very difficult migrations off this service.
You can configure cloud run to always allocate CPU but it's a lot more expensive. I don't think it would be a good autoscaling story since autoscaling is based on http requests being processed. (maybe can be done via CPU but that's may not be what you want, it may not even be cpu bound)
The nice thing about this is that you can use a runtime like cloud run or lambda and allow that runtime to scale based on http requests and also scale to zero.
Setting up autoscaling for workers can be a little bit more finicky, e.g. in kubernetes you might set up KEDA autoscaling based on some queue depth metrics but these might need to be exported from rabbit.
I suppose you could have a setup where your daemon worker is making http requests and in that sense "push" to the place where jobs are actually running but this adds another level of complexity.
Is there any plan to support a push model where you can push jobs into http and some daemons that are holding the http connections opened?
The author stated they had millions if not 10s of millions in the bank and a bit of runway. And they had already done layoffs. Based on this, they were not under pressure to raise or do a down-round.
Separately and related to a sibling comment, the fact that Thrive Capital invested in Airplane and Airtable means they can now have a positive "tombstone" for Airplane by saying it was an "exit" while receiving a bunch of their original investment back.
There is very light gray font against a white background.
The chip comes to consumers overclocked by default with a TDP of 105W. I suspect this is the case so that it can beat Intel on benchmarks on "default" settings.
You can set it to "eco mode" and have it run at 65W or 45W TDP. Under load, this only results in like a 5% reduction in performance for a dramatic reduction in electricity consumption, fan speed, heat, etc.
Not sure if the 5500x series chips are overclocked but using eco mode could be a good approach.
In such cases, if I am using dependency injection and creating a (stub?) versions of that client which returns a hardcoded or configured output, would that be considered a mock? OR would this be OK and not "coupled"?
I am doing UI,backend API services, ML research, ML services
I used to use Linux as a primary OS and sometimes dual boot in Windows. However, I have since transitioned to using Windows directly and WSL2. It is seamless overall.
There are a few edge cases, e.g. it was as little annoying to set up LUKS encryption and it's a lot easier to just use BitLocker. Other minor edge cases with permission of volumes that are mounted from Windows into Linux.
Further, there are some nuances around networking, especially if you are running docker in WSL2.
Once you get over these hiccups, it's quite comfortable.