Hiveware's 3-2-1 persistence insures that its DApps are always up and on. As a result, TCP ipv4 and ipv6 addresses to inter-instance nodes are permanently connectable (but of course only connected when directly in use).
September 2019: Libra, Gram and Hiveware each have their own valuation architectures. Only one will succeed. The New York Times sums up Libra and Gram's methods:
"Facebook’s Libra is meant to be backed up by traditional currencies held in bank accounts, in order to stabilize the value of the digital coin. The Gram, in contrast, will be backed by nothing and gain or lose its value, like Bitcoin, by whatever someone is willing to pay for it." NYTimes, Aug 29, 2019, "Look Out, Bitcoin, Here Comes Gram"
Hiveware participants, in stark contrast to Libra and Gram, do work on the internet first by fostering digital asset security, ownership and privacy. Having achieved that, Hiveware dApps are exercised to continually earn HVWs distributively, not air dropped or arbitrarily given to investors as will be the case for Gram, or enforced as will be the case for Facebook's Libra fiat-anchored currency.
March 2019 and some people are just discovering how redundant the cloud is. Here is what Marc Clifton has discovered in a discussion of how expensive the cloud will become and how this will push users back to in-house servers:
"Another trend that I'm watching with interest is distributed computing / P2P computing -- technically not "the cloud" but it offers a potential challenge to the (ironically) monolithic providers like Amazon and Azure -- what would it be like if individuals sold storage / compute / page serving capabilities where the web app was distributed across hundreds, if not thousands, of devices, from a simply rPI to a super high performance machine? Redundancy is part of the lure of distributed computing, and of course security is one of the major issues to solve.
Regardless, I see distributed computing as a potential future where these huge, power hungry, space consuming, eye sore data centers become replaced by, well, every connected device that sits their mostly idle." by Marc Clifton in CodeProject Lounge discussion "Cloud vs. Tin"
-Check out "AT&T Cloud Glitch" for an example of what you can expect if you trust big servers.
-For an example of a real grassroots cooperative authoring teamwork which still uses servers to facilitate cooperation, see "Social Knitwork". If this app had been written in Hiveware, there would be no need for servers and the participants would be able to sell their wares directly to each other and their fans.
-At last, someone articulate enough to describe how we, who use the computer to do real work, feel about the mobility craze. Robert Seaton's "I Hate My Smartphone" rant even describes the desire for the functionality of a Hiveware app in the works (see 4th paragraph from the bottom beginning with "The least excusable failing of Android and iOS...is that I can't move from what I'm working on with my MacBook or desktop and then to my smartphone"). It has taken evolution millions of years to develop our 10 fingers. Smartphones only use 8 of them. Not exactly a winning navigation architecture and neither is gesture for real computer work.
-Symantec Unplugs from the Cloud (the Washington Post, 13/12/16)