Thanks, that makes sense. One advantage then of running the cloud internally then would be the REST API shenanigans would all be within our own network. (This is probably a pretty minor item though.)
Seems the best course of action is to spin up some [eg RackSpace] cloud IaaS account and start to learn how we would build/deploy the sorts of things we build now. Leave looking into setup/admin of the cloud components for another day. -- Craig Constantine, http://constantine.name On Jun 8, 2016, at 7:20 AM, Dan Ritter <[email protected]> wrote: The "services" run on clouds are provided by daemons, same as you are used to everywhere else. They need to be load-balanced in front and have HA storage in back. It is trendy for the daemons all to have HTTP-accessible APIs, which have the advantage of being networked and easily load-balanced, and have the disadvantage of having to make network roundtrips for everything. The "cloud" is a set of machines that are managed by a system like OpenStack, which arranges for services to come up, go down, get billed, and so forth. The cloud management system can work directly on real machines ("bare iron") or manage VMs or containers. Nothing runs directly "on the cloud", that's just a metaphor. There is no free lunch. -dsr- -- https://randomstring.org/~dsr/eula.html is hereby incorporated by reference. there is no justice, there is just us. _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
