Both localstack and floci live in this weird spot where for a lot of my applications, all the cloud-vendor specific stuff is abstracted out anyway. So the only time I need to touch the cloud is for testing the abstractions and do end to end testing. The abstractions can be tested against real cloud APIs as it is generally cheap to do and provides the highest fidelity results. End to end testing includes testing against a production-like environment, so again, more bang for your buck to just test against the cloud.
I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.
catlifeonmars · · focus · HN ↗
I’ve definitely reached for these local cloud tools from time to time, but in a well-architected piece of software, you aren’t getting that much value from them. Either you don’t have a hard cloud dependency, or you want a high fidelity test of a specific cloud dependency.
mmarian · · focus · HN ↗
Reached the same conclusion. Plus it's a fair amount of effort to set them up and maintain.