I just burned hours trying to figure out why basic D1 SQL queries against a 100MB database are taking 20-30 seconds wall time. Turns out there's an ongoing D1 issue, but it's only being acknowledged in Cloudflare's D1 Discord channel, while cloudflarestatus.com says everything is a-ok.

Posting here in case it saves someone else the debugging rabbit hole.

Comments URL: https://news.ycombinator.com/item?id=46734283

Points: 10

# Comments: 4

After reading Healing Back Pain: The Mind-Body Connection by John E. Sarno ( https://www.goodreads.com/book/show/144873.Healing_Back_Pain ), I recognized that my body was trying distract me from my troubled relationship at that time. On my next painful episode, I mentally said "F*ck it, there is nothing wrong with me physically" and the next day the pain was gone, never to resurface again. The whole thing coincided with my relationship finally ending, so that might have had a positive impact as well.

It still blows my mind though, how much grief my brain gave me over the years.

Comments URL: https://news.ycombinator.com/item?id=39777440

Points: 4

# Comments: 3

Unfortunately, I have a similar experience with Firebase, where I wish I would have known that:

* Don't like the text of your Firebase Auth SMS verification message that we send on your behalf -> tough luck

* Your app name is longer than 15 characters? We are not going to include that hash in your Firebase Auth SMS message that is required by Android to perform an automatic login.

* Global Firebase Auth SMS pricing does not work you economically? Welcome to implement the whole thing yourself anyways.

* Dealing with development environments is flakey, as Firebase's emulators work 98% similar to production, but you will regularly hit things that are different.

* You can't completely automate environment creation/tear down, as not everything is covered by Terraform or Google's own APIs, so you will end up doing manual things in their admin interface.

* Real-time subscriptions in Firestore end up not being worth the tight schema coupling between client and server, as you can't control when the updates fire and you end up with a lot more unintended side effects than what this technology benefits you.

So after a year of workarounds you finally end up deeply understanding the trade-offs involved in Firebase and make the decision that its downsides exceed its out of the box benefits. :(

Comments URL: https://news.ycombinator.com/item?id=36019391

Points: 28

# Comments: 6

Looking for help with converting a small Android app (36 .java files) to Kotlin and add two smaller features.

Interested? -> project+kotlin@k2labs.net

--8<--

Existing Laravel/MySQL-based dashboard needs a successor. Looking for someone who has experience creating Nova dashboards with role-based access control.

Interested? -> project+dash@k2labs.net

--8<--

Looking for someone who has experience building scheduling/workflow systems to convert existing crontab that simply runs 30 scripts at different times pulling data from external sources (that sometimes fail and need to be retried) and also have dependencies between each other into a more robust & manageable system.

Interested? -> project+byecron@k2labs.net

Google is a big bully and if you try to compete with them in an area they care about, they will use their market dominance to keep your product out. They have been deserving that fine for a long time.

IP addresses as Targets You can load balance any application hosted in AWS or on-premises using IP addresses of the application backends as targets. This allows load balancing to an application backend hosted on any IP address and any interface on an instance. You can also use IP addresses as targets to load balance applications hosted in on-premises locations (over a Direct Connect or VPN connection), peered VPCs and EC2-Classic (using ClassicLink). The ability to load balance across AWS and on-prem resources helps you migrate-to-cloud, burst-to-cloud or failover-to-cloud.

Looks like you need an active VPN connection to access external IPs.

- Route 53 failover record * primary record: Google global load balancer IP * secondary record: Route 53 Geolocation set (really need that latency) - Elastic Load balancer record per region * routes to mirror region GCP IP address (ELB's application load balancer seems to able to point to AWS external IPs) * optionally spin up mirror infrastructure in AWS

Seems brittle. Does Azure support global load balancing with external IPs?

Does anyone have such (or similar) setup actually in production? How did it work today?

What is going to be faster? Updating DNS records with TTL 3600 to point to a single data center or Google fixing their problem.

We host DNS at AWS, but servers in GCP. Should we use AWS's automatic DNS failover feature to cover for such a case?

Given that we are surrounded by an incredible amount of high-calorie food (100g of a Snicker's bar provide 488 calories), it is easy to forget how difficult it is to source calories in the wild.

Can somebody please explain to me why this can't be mitigated against? Is it because they offer DNS as a free add-on and can't be bothered to spend the bucks to make their service more DDOS-proof?

- After EC2 East was slow like molasses, I switched over to EC2 EU which was still speedy

- That caused their CLI tool to fall on its nose when trying to tunnel to the database (right now the bridge always gets installed in EC2 East). Fixed with a simple patch in the Ruby source

- Looks like the backend connector in nginx won't connect to your app if you have Basic-Auth on your root index

- Later MySQL became unavailable with "Host '10.0.47.186' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'". No connection limiter between different apps?

I think AppFog is offering a great value should they be able to iron out all the kinks. I'm crossing my fingers that this will happen quickly.

Comments URL: https://news.ycombinator.com/item?id=3240045

Points: 1

# Comments: 0

e.g. Adele is on tour right now, but DDG won't return a SeatGeek listing for it

Is GitHub a great product because the founders optimized for happiness or where they only able to optimize for happiness because they had a home-run product on their hands?