FKs, indexes and constraints in general make the process more difficult, but possible. The data migration took some hours in my case, but no need to be fast.
AFAIK GitLab has tooling to run tasks after upgrade to make it work anywhere in a version upgrade.
It's a one page document that deals with a very specific situation - if a human were to write it, I'm sure they would come up with pretty much the same thing. I actually have no problems with this particular case
Location: Brazil
Remote: Yes, remote only
Willing to relocate: No
Technologies: mostly Python, but always hacking with other things
Résumé/CV: https://www.linkedin.com/in/iurisilvio/
Email: iurisilvio@gmail.com
Worked as CTO for one company from the begining and it was acquired by a big local retailer. Now doing consulting for local companies.
New Relic. Unfortunately it reduced their free plan (and the paid plan is expensive), but I was always amazed about their free features. I'm still didn't find a good alternative. :(
I thought lambda was configured to use a single exit IP that rotates every 4 hours. How many IP's are you getting via this method, and are you using any tricks (multiple accounts, etc) to get a wider variety of IPs?
To be honest, I have no idea. Maybe I'm even wrong about why it works.
I have a toy service with ~200k requests/day to a public service and I was blocked all the time.
After I changed to use API Gateway + Lambda as a proxy, never had these problems again. I just monitor the 4xx and 5xx errors and they are almost zero now.
