> What is your definition of End Product here? Eg if we have an app and website under one brand is that two end products or one?
One brand with web + mobile app would be one product. To be more explicit, a software development consultancy with multiple clients would need one license per client.
For updates, you are 100% in control of the data once it is on your S3. This means that it won't change from under you, change pricing, or disappear. This also means you'll have to explicitly copy updates from upstream, and I'm figuring out the right cadence for that (likely ~quarterly)
I've tested Backblaze B2 as a storage option, and I found that with the level of traffic a typical map backend incurs, there were enough 503 errors to cause problems. This is an intentional trade-off of the B2 design that allows them to set an aggressive price point: https://www.backblaze.com/blog/b2-503-500-server-error/
I'm constantly evaluating all of the different deployment combinations and new features on cloud providers, so part of the service I'm offering is advice for your specific provider and this workload.
One brand with web + mobile app would be one product. To be more explicit, a software development consultancy with multiple clients would need one license per client.
For updates, you are 100% in control of the data once it is on your S3. This means that it won't change from under you, change pricing, or disappear. This also means you'll have to explicitly copy updates from upstream, and I'm figuring out the right cadence for that (likely ~quarterly)