Re: Early criticism
@SaneIT, thanks so much for taking time to reply on that. Don't get to talk to people often who are doing some of this modern stuff. Our Corp kind of stuck in the 90's. Of course, I'm probably stuck in 80's so it is good match. :-)
One followup question. How do you architect this? Is it still possible to keep a private non routable IP scheme (10.0.0.0) and still hit these servers? Is that done by using VPN tunnels, so it appears these cloud resources are local?
I'm thinking of stuff like AutoDesk CAD, where we use network based licensing. When you configure. it asks for server name where license service running. It doesn't appear to me it could configure credentials to find this server across a WAN? Or is the idea if you go cloud, you commit to stuff like AutoDesk 360 and Office 360, totally change the way you play the game?
I'm still struggling with the cost side of "rent versus own" on this paradigm shift. We get some incredible ROI on stuff we buy, both hardware and software, lasts way longer than vendors would like you to think. Manufacturing just doesn't change that rapidly, at least the products we make. We have no needs for rapid scaling, we are b2b in our customer relationships.
So I'm having a hard time deciding whether, in the long run, it's any different having local servers/hardware with support help from a local partner(s) or cloud hardware with support from a remote partner/vendor. Not asking you for any answers on this, just insight what I'm struggling with as I try and position this company for the future.
But let me know if you have any input on the IP scheme if you get time. It's so hard to get your head around your entire business sitting outside the firewalls like the bad guys are. But if VPN solves that, then just question of whether VPN concentrators kill your bandwidth. We use VPN for remote access now, the performance can range from bad to dialup bad. :-)