|
|
|
|
|
by tw04
3132 days ago
|
|
Serious question: why? I mean, maybe as a really, really lazy hack if you've got free azure credits and don't ever plan on actually supporting Azure in your codebase. But that seems like a very, very corner case. Would anyone ever actually do this for something production? Why wouldn't you just write native azure support, it's not THAT difficult. |
|
In terms of use case: my company has a customer that requires us to locate an instance of our product in Azure, and some of that infrastructure is much easier to move with a compatibility layer.
You might as well ask why there are any standards in software and networking at all, as each new protocol or library isn't THAT difficult to support.