Channels ▼
RSS

Parallel

Google Chromebooks: Developer Freedom or IT Complexity?


With Google's launch of its first Chrome OS-powered "Chromebooks", IT monitoring software provider Opsview has warned that such devices are going to create a new set of IT monitoring challenges which will ultimately include developer-related issues.

The launch of Chromebooks highlights the growing trend towards more applications and services being delivered from the cloud. With many of these new services being hosted for application testing purposes in the public cloud, developers have been attracted by the opportunity to sandbox in an off-premise environment now that cloud-driven virtual machine instances can be spun up and initiated in literally seconds.

"Today we can see some compelling business arguments for cloud-based devices such as the Google Chromebook. In the future, we could see developers using them as a means to access development services in the cloud; however, I would suggest that it is a young and unproven strategy," said James Peel, product manager at Opsview.

"Consequently, organizations need effective IT monitoring tools which can provide them with automated and timely service-level reporting, which can give them real insight into IT performance. This can also help ensure that they are getting value for money from their service provider."

Opsview also comments on organizations now needing a fresh approach to the manner in which they monitor and manage their IT infrastructure. For instance, IT and project managers that oversee teams of developers are now monitoring less physical infrastructure as services are being developed using PaaS (Platform as a Service).

"The transition to such services raises the importance of network monitoring in particular, as it is vital to monitor the end-to-end performance from the developers' perspective but at the same time have the visibility to see if your service provider is meeting their service-level commitments," said Opsview's Peel.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video