Cloud Computing with Wyse

Cloud Computing involves using information technology as a service over the network.

  • Services with an API accessible over the Internet
  • Using compute and storage resources as a service
  • Built on the notion of efficiency above all
  • Using your own datacenter servers, or renting someone else’s in granular increments, or a combination

We at Wyse believe cloud computing has the potential to change how we invent, develop, deploy, scale, update, maintain, and pay for applications and the infrastructure on which they run.

Cloud Computing Benefits

Efficiency

Drives cost out of the delivery of services, eliminating capital expense in favor of more easily managed operating expense

Agility

Increases speed and agility in deploying services, adapting to seasonal or cyclical computing needs

Speed

Shortens implementation cycle time

Flexibility

With application deployment decoupled from server deployment, applications can be deployed and scaled rapidly, without having to procure physical servers

Ubiquity

Applications can be made available anywhere, any time

Cost avoidance

Minimizes the risk of deploying physical infrastructure, lowering the cost of entry, thin devices enable Green IT

Accelerated innovation

Reduces run time and response time, increasing the pace of innovation

Users

Task Workers

Call Centers addressing the trend to move employees off campus and into home
Challenge: PCs are virus prone, difficult to manage, and at risk of data being exposed or devices being stolen. Tried terminal services and dissatisfied with user experience
Require flexible seating, reduction in energy, and simplified management and deployment

Financial Services

Branch systems with varying classes of users across broad geographies attracted to client vitalization for security and compliance.
Challenges: VDI pilots proving difficult to scale, user experience across branch system is inconsistent, require higher levels of user functionality for banking peripherals.

Healthcare

Hospitals addressing the need for EMR and access to common databases and information
Challenge: Healthcare environment, ease of secure access to up to date EMR, access for field professionals. Risk of theft of traditional PC devices, and the liability of data loss and exposure, universal access throughout the primary and satellite facilities

Education

Schools need to provide common IT functionality to faculty, staff and students
Challenge: shrinking budgets, limited IT administrative support, ageing computing devices, providing lesson and status access to parents, teachers and students from home

Engineering

Technology companies needing to provide secure, access devices to on shore, off shore, and outsourced engineers and developers.
Challenge: Requirements to deliver productivity applications while addressing performance demands of engineers and developers

Simple EndPoint Benefits

Security/Privacy

No HDD prevents data from being stored on the client, improving data security. All data stays on the server / cloud, enhancing privacy enforcement. Devices can be virus proof, removing a security concern for the endpoint component of the environment.

Compliance

HIPPA in Healthcare, Basil-II in banking, and Sarbanes Oxley regulations all require data to be protected and centralized. Thin endpoints enforce this requirement, easing compliance.

Manageability

Lowest TCO is accomplished when all endpoints appear similarly to the server. TCs, TPCs, and Thin mobile devices (handheld and notebook size) are all centrally managed, and look the same to servers. Like the Southwest Airlines strategy – all 737-300s – easier to manage.

Reliability

Thin clients are far simpler in design than traditional PCs, and deliver far greater reliability. Measured in terms of MTBF (Mean time between failure), PCs offer 30 – 40K hours, but TCs deliver far better ratings at 80 – 375K hours.

Rapid Deployment

No imaging requirements on most thin devices make TCs deployable in minutes, not hours as with most PCs. TCs go from carton to desktop to productivity in minutes. No software to load, little configuration needed.

Power, Noise, Cooling

TCs use a fraction (less than 10 percent) of the energy needed by traditional PCs. No fans or moving parts in TCs eliminate noise, and reduce AC requirements in the work areas.

2017-07-27T00:01:11+00:00 June 8th, 2010|Uncategorized|

About the Author:

Clint is cool as a cucumber, but has been aged in habanero brine.

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113