How Fly.io and Tailscale Saved Notado

Post by bsnnkv » Sat, Oct 22, 2022, 3:02 PM UTC

RamblingCTO wrote: post #37

bsnnkv wrote: post #33

Earlier quoted context omitted.

Thanks for this question! Back in early 2020, Meilisearch did not have a Rust client library, but it did have a Go client library[1], and there was nothing comparable to lib/pq[1] in the Rust ecosystem which would allow me to create a listener on a table.[3] Go is generally my "fallback language" when something would not be practical to do in Rust; it has a very nice, mature ecosystem, and as long as you aren't conde…

Thank you for taking the time to answer, I'm always curious as to the why ;) Sounds like a good decision in that case! Good luck with your project!

Just wanted to share with you that I recently published another article on this component.[1]

[1]: https://notado.substack.com/p/how-notado-syncs-data-from-pos...

Post by deznu » Tue, Oct 25, 2022, 12:31 AM UTC

pclmulqdq wrote: post #86

deznu wrote: post #73

Earlier quoted context omitted.

Or just have billing alerts...

Billing alerts can tell you exactly when you have spent 4 figures after the fact. Using a VPS prevents 4-figure bills. Actual billing caps are very hard for cloud providers to implement with the HA distributed systems clouds use for billing, and would carry a significant performance cost. Alerts are the best you can do if you take the variable costs.

Thanks for explaining that. I didn't think about the complexities of billing caps. Is there a contract from a cloud provider that even if they do go over the billing cap, since you set that as your "limit", they can't bill you for over that amount? I imagine that the responsibility for managing billing caps lies on the provider, and the consumer should be comfortable that they will not be charged above the limit they set.

Re: How Fly.io and Tailscale Saved Notado

Re: How Fly.io and Tailscale Saved Notado