What are the downsides to deploying all my services as separate fly apps within an org (something akin to “microservices”, but I want to stay within the fly model). What would the use case be for Kubernetes on Fly - or the benefits there that I wouldn’t have otherwise on the Fly platform? I use Fly to manage deployment, traffic, and scale apps - something that Kubernetes may solve for on other platforms.
I am drawn to the model of “all my services are internally-networked Fly apps.” However, one factor that comes to mind may be cost.
I am curious to hear the Fly.io team’s take here.