Talk:Cloud computing/Archive 1: Difference between revisions

Content deleted Content added
mass archive to revitalise and refocus discussion
archive ramu50
Line 589:
--[[Special:Contributions/82.203.173.213|82.203.173.213]] ([[User talk:82.203.173.213|talk]]) 09:44, 12 October 2008 (UTC)
* Yeah, sure... FTP clients for example usually just connect to a single server for a point-to-point transfer... use it to access a cloud based CDN on the other hand and you've got 'cloud computing'. [[Special:Contributions/84.72.91.139|84.72.91.139]] ([[User talk:84.72.91.139|talk]]) 08:34, 12 November 2008 (UTC)
 
== What is Cloud Computing (simplified version) ==
 
'''DO NOT''' go back to the Archive and read
* [[Talk:Cloud_computing/Archive_1#Easy_to_understand_Cloud_Computing|Easy to understand Cloud Computing]]
:That is a horrible example I made before and it is way too technical.
 
New Explanations (Digrams)
[[Image:Traditional server infrastructure.png]]
 
----
 
[[Image:Cloud computing infrastructur.png]]
 
 
Cloud Computing for me I think is probably a new sets of technology that work in an infrastructure, known as The Cloud. First you should know how traditional internet works. For most programmers I think the first chart is very obvious.
 
=== Diagram 1 ===
Database
* (e.g. SAN [storage area network], VTL [virtual tape library], holographic storage])
 
Purpose-based server
* (refer to application server, game server, web server…etc.)
 
ISP
* mainly control the network traffic
ATM & SONET was placed there just to show that other types of network infrastructure also exist.
 
MAN (Metropolitan Area Network)
WAN (Wide Area Network)
Home Business (SOHO, Enterprise)
 
=== Diagram 2 ===
AI (Artificial Intelligence)
SAN (Storage Area Network)
 
 
 
So to implant cloud computing there are two method.
Implant technologies in purpose-based server.
Implant virtualization in your purpose-based server. Since webpage scripting should be build using JSON, XML (interchange formats) and in the future Aspect-Orientation (traffic control) Programming. Each virtualized application act as a (communication portals) and thus it can connect to multiple devices mediums (e.g. mobile devices, desktop devices, game consoles).
 
Another way to connect to other mediums it to build web applications that can support synchronization and integration technologies such as Office Live.
 
 
(Read the Virtualization Classification)
 
Implant technologies in your Databases
-for the past decade bioinformatics and IT have been trying to work together to develop a technologies that can make database information act as DNA so it can behave artificial intelligently
-Well for a start you can implant Storage Virtualization and The Semantic Web (efficiently classifying and managing the data) and than implant an AI. Since middleware itself is an API, you can implant it to communicate with other devices mediums. Except our technologies is so little right now that probably the only service middleware can provide is XMPP phone calls. Or while you are skiing, you take a couple of photos and use the middleware to gather a bunch of friends from other place and share the picture (temporarily).
 
Since purpose-based and database in the future might be standalone, and do not require each other, they itself will act as a service provider and servicing desktop web services thus making the entire web acting like a P2P and P2P just looks like a cloud.
 
 
==== Virtualization is usually classified into the following ====
<u>Hardware based<u></br>
* Hardware-assisted (Virtual Machine, codes are complied or interpreted e.g. JVM)
:benefits: Cross-platform
 
 
* Emulator
 
----
 
* OS level virtualization
:the most common form of virtualization that uses a Hypervisor to virtual a Virtual Machine.
 
 
* Network Virtualization
:programming the entire network using network devices (such as Routers) to create a VLANs
 
 
* Storage Virtualization
:basically they use a different set of (Network) File System interface technologies, e.g. [[Logical Domains|LDOMs]] (LUN, SMB, CIFS)
 
 
They are other types of Virutalization that many coorporation claim to be a type of virtualization, but some of them I am still trying to understand them, while the other I totally disagree with their concept.
 
Mobile devices usually use a bytecode or runtime compiler to run the mobile framework and hosted Virtual Machine or Browsers to communicate with applications. Since webpage can be entire build with XML (static interaction), JSON (dynamics interaction) and AOP the entire browsing will totally speed up, because (runtime engine---via---MVC).
 
The mobile framework is acting as a framework.
 
=== Commentary ===
I REALLY suggest you learn and implant JSON and XML. The currently world believing in JavaScript must be needed or must not be needed is entirely stupid, aspects, objects and data are the fundamentals elements of programming computer science, you can’t omit them, you have to organize them at “EVERY” single level, MVC level, coherency, traffic flow, behavior….etc.
--[[User:Ramu50|Ramu50]] ([[User talk:Ramu50|talk]]) 00:54, 26 November 2008 (UTC)
 
=== Summary ===
Server (XML, JSON, AOP) interchange, synchronization, integration
Virtualization layer
: Purpose: to act as a service provider
 
In Diagram 2, I draw the ISP as the background, because I think in the future ISP will be integrated into the purpose-base server, but that will only happen if the industry decide to implant the TCP/IP OSI model + GSM specifications. Because I think the industry is dumb not to develop a management systems for managing traffic control.
 
Of course, they are other implementations that most industry haven't notice at all, but I am not going to reveal it, because they are just going to steal my information.
 
 
Reference: [[Template talk:Database implementations and models#new|Database (template)]]</br>
Other brainstorming topics: Visual Thesaururs
--[[User:Ramu50|Ramu50]] ([[User talk:Ramu50|talk]]) 23:16, 26 November 2008 (UTC)
 
 
: Wow, you're obviously putting your heart and soul into this... thanks for your efforts and apologies for archiving something that may have still been current. To be honest I'm still a little confused by these diagrams (mostly by the relevance of some of the components) but it's clear that you are viewing the cloud from a different perspective - from 'underneath' perhaps while I am looking at it from a user's point of view. Anyway, interested to see what comes next. -- <u style="text-decoration:none; font-family: papyrus;">[[User:SamJohnston|samj]] <small><sub><font color="maroon">[[User talk:Samj|in]]</font></sub><sup><font color="green">[[Special:Contributions/SamJohnston|out]]</font></sup></small></u> 11:33, 26 November 2008 (UTC)
 
===Suggestion===
Thanks for your efforts. I was thinking you should be able to represent cloud computing with the actual physical things involved: computers. The Internet is fundamentally three different kinds of computers: servers, clients, and let's call the in-between computers routers. So could you draw a diagram using these three basic elements, and then show how the information flows through the system. I think this will help simplify it more than protocols and acronyms and artificial intelligence, because that's about as illuminating to most people as drawing a cloud on a whiteboard.--[[Special:Contributions/72.39.35.178|72.39.35.178]] ([[User talk:72.39.35.178|talk]]) 03:29, 3 December 2008 (UTC)
 
: Ramu50 has been blocked indefinitely due to a long history of tendentious editing, editing against consensus, and NPA violations. I haven't looked at what he's written (or drawn) here in much depth, but based on the quality of many of his other contributions, the number of times he's been reverted, the zeal with which he attacks anyone who disagrees with him, and the repeated calls for him to "please stop", I wouldn't count on his material here to provide any new insights into how to best describe cloud computing. His way of looking at things seems to be unique and is almost never in agreement with either reliable sources or consensus. I would advise simply moving the section he's written here to an archive and forgetting about it. [[User:Jeh|Jeh]] ([[User talk:Jeh|talk]]) 05:22, 3 December 2008 (UTC)
 
::Already did that once, and he's back. Maybe you're right. [[Special:Contributions/93.3.248.168|93.3.248.168]] ([[User talk:93.3.248.168|talk]]) 00:08, 5 December 2008 (UTC)