4 ms·

The biggest problem with these sorts of “cloud agnostic” approaches is that one is limited to only fairly basic architectures on broadly monolithic apps. The se

by JCM9 5y ago

The biggest problem with these sorts of “cloud agnostic” approaches is that one is limited to only fairly basic architectures on broadly monolithic apps. The second you want to do something more in depth or customized then this model falls apart quite quickly and you’re back to square one real fast. If you really just want a basic website and that’s all you’ll ever do this might work but outside that pick a platform and build natively to get the full benefits of that platform. People like to talk about wanting to be cloud agnostic so they can switch workloads quickly etc. In practice few really do that since the pain imposed by building to the least common denominator is vastly worse than the “benefit” of mitigating some perceived “risk.”

mathverse 5y ago
The same could be said about all the shenanigans involving cloud and being web scale. For 95% of the companies this will never become a problem and your need to spin up a VM in another part of the world does not justify using an expensive cloud provider like AWS,GCP or Azure.
- igorzij 5y ago
  It's all very relative and depends on your operational complexity. If what you are building is working fine with VMs and you don't see negative impact on your business from operating it yourself, then sure - why fix what's not broken? But for thousands of small businesses out there, not speaking of medium and large ones, cloud providers replace one or more full time employees who'd otherwise be busy maintaining and supporting their stacks. You can do the math. From that point of view AWS & co are dirt cheap.
igorzij 5y ago
We believe we've cracked "the second you want to customise" problem. We offer 3 levels of customisation below the UI: config file options, Terraform overrides and entirely custom Terraform targets. So it really is fully native, not a black box. All the simplifications are completely optional - you can change whatever you want, whenever you want.

by JCM9 5y ago

mathverse 5y ago

The same could be said about all the shenanigans involving cloud and being web scale. For 95% of the companies this will never become a problem and your need to spin up a VM in another part of the world does not justify using an expensive cloud provider like AWS,GCP or Azure.

igorzij 5y ago
It's all very relative and depends on your operational complexity. If what you are building is working fine with VMs and you don't see negative impact on your business from operating it yourself, then sure - why fix what's not broken? But for thousands of small businesses out there, not speaking of medium and large ones, cloud providers replace one or more full time employees who'd otherwise be busy maintaining and supporting their stacks. You can do the math. From that point of view AWS & co are dirt cheap.

igorzij 5y ago

We believe we've cracked "the second you want to customise" problem. We offer 3 levels of customisation below the UI: config file options, Terraform overrides and entirely custom Terraform targets. So it really is fully native, not a black box. All the simplifications are completely optional - you can change whatever you want, whenever you want.