- cloud native is weird/hard - old ways were better! - misconceptions about boundaries and aspects
Remember folks. When choosing technology, your selections always depend on a list of concerns, including:
- cost - complexity - developer audience - support audience - change management - vendor relations - mapping out dev strategies - getting consensus from team
No matter what tech is used, you still need to go through planning and design.
More often than not, cloud enables us to hack first. That is never a good strategy.
There’s nothing inherently bad about cloud native. It’s just different and _can_ be highly beneficial to outcomes.
I was in that position once, with Microsoft functions, which my boss wanted to use, but fortunately convinced my boss to get rid of it. Maybe others don't have the same luck.
- cloud native is weird/hard - old ways were better! - misconceptions about boundaries and aspects
Remember folks. When choosing technology, your selections always depend on a list of concerns, including:
- cost - complexity - developer audience - support audience - change management - vendor relations - mapping out dev strategies - getting consensus from team
No matter what tech is used, you still need to go through planning and design.
More often than not, cloud enables us to hack first. That is never a good strategy.
There’s nothing inherently bad about cloud native. It’s just different and _can_ be highly beneficial to outcomes.