1. Things like Digital Ocean that make it easy and can scale up
2. The PaaS offerings of the major clouds for example Microft Azure Appspaces.
I think your advantage might be that you could eject into something more enterprise ready perhaps with Terraform/k8s etc. You could also sell consulting time to help the ejector transition to cloud. Because rearchitecting is part of the issue but the new devops and maintenance load is another issue people will need to deal with.
I think you're right. In fact, that's the stack I would recommend right now to a new (web) app developer. Write your own Dockerfile, some terraform to spin up a docker host on DO, and a bit of GH Actions yml to pass secrets, build dockerfile, upload to container registry, terraform apply.
It's a fun weekend project. It's interesting how many ways there are to "build your own PaaS".
IIRC with a bloom filter if returns false you can be sure it is not in the set but if it returns true it probably is in the set but might be a clash giving a false positive?
Is the same true with this data structure.
I guess you could mitigate this by storing an additionally hash or the original key in it’s entirety as the value?
1. Things like Digital Ocean that make it easy and can scale up
2. The PaaS offerings of the major clouds for example Microft Azure Appspaces.
I think your advantage might be that you could eject into something more enterprise ready perhaps with Terraform/k8s etc. You could also sell consulting time to help the ejector transition to cloud. Because rearchitecting is part of the issue but the new devops and maintenance load is another issue people will need to deal with.