My dream world is to run the “same thing” in a public cloud, datacenter, and (limited resource) remote facility.
The latter wouldn’t need to be failure tolerant, just quickly recoverable as a service (not necessarily the data).
If I could provide 1 app usage pattern and 1-3 operational patterns that would solve so much.
This is hard for every data service, partly because of technical debt/entrenchment and data has gravity. But cache is the most flexible.
The joys of having a portfolio of 1000s of apps ranging from COBOL to “cloud native.”
Not a demand, just sharing the “needs” of my big traditional company for perspective. I feel that often times IT as an enabler vs IT as the product gets lost in the shuffle.
And so much assumes more Human Resources can be dedicated than a company that sees IT as overhead can dedicate.
All that said, constraints + scale can be a fun problem to solve. Making “right” easiest is always better than rules.
My dream world is to run the “same thing” in a public cloud, datacenter, and (limited resource) remote facility.
The latter wouldn’t need to be failure tolerant, just quickly recoverable as a service (not necessarily the data).
If I could provide 1 app usage pattern and 1-3 operational patterns that would solve so much.
This is hard for every data service, partly because of technical debt/entrenchment and data has gravity. But cache is the most flexible.
The joys of having a portfolio of 1000s of apps ranging from COBOL to “cloud native.”
Not a demand, just sharing the “needs” of my big traditional company for perspective. I feel that often times IT as an enabler vs IT as the product gets lost in the shuffle.
And so much assumes more Human Resources can be dedicated than a company that sees IT as overhead can dedicate.
All that said, constraints + scale can be a fun problem to solve. Making “right” easiest is always better than rules.