dprotaso

What are the issues?

Curious how you settled on your pricing?

Curious is there a go lib that can read the config file? I’d love to have this in some testing to make it more accessible.

That’s why Knative (Serverless on Kubernetes) accepts containers. It’s the standard packaging format that lets you lift and shift apps to many different platforms.

Funny to see a little go library you wrote [1] show up in a blog post years later. I need to update it now that go has iterators and generics.

Another great blog post [2] covers performance issues with go tool

[1] https://github.com/dprotaso/go-yit

[2] https://blog.howardjohn.info/posts/go-tools-command/

Is Render still using Knative?

https://render.com/blog/knative ?

What free monitoring tool do you use?

This seems timely given iOS 18 has limited contact list syncing [1]. Curious if you have a social app focus or thoughts?

[1] https://x.com/nikitabier/status/1836612494938509664

Splitting your operations into containers then breaks the monolith into microservice pieces and introduces all the downsides

A pattern here is to not split the monolith and use the same container for your main app and hot operations. The hot operations just need some different configuration eg. container args or env vars

https://knative.dev/ - (CloudRun API is based on this OSS project)

Curious - what are you using to power/style your docs website?

No need to fork anymore http://concourse.ci/configuring-resource-types.html