Azure is based on Windows, so you can write applications in the same programming languages you’ve used for Windows apps: Visual Basic, C++, C#, etc. You can also use familiar tools such as Visual Studio, along with ASP.NET and other familiar Windows technologies. This makes it easy for organizations to find developers who already have the skills to create applications for the Azure platform. And because the Azure environment is much like the standard Windows environment, it’s easier to create a cloud version of an existing Windows application.
2: 64-bit Windows VMs
Applications running on Azure run in virtual machines, with each instance of the app running in its own VM on the 64-bit Windows Server 2008 operating system. The hypervisor on which they run is designed specifically for the cloud. You don’t have to supply your own VMs or deal with managing and maintaining the OS because apps are developed using Web role instances or worker role instances that run in their own VMs. The apps interoperate with other Azure components through a Windows Azure agent that runs in each VM. With Azure, you can focus on the code and don’t have to worry about the hardware.
3: Azure SDK
Microsoft provides the Windows Azure software development kit (SDK), which includes a version of the Azure environment you can run on your own computer. It’s called the Windows Azure Development Fabric, and it includes the Azure agent and storage. You can work locally when developing and debugging an application and then move it to the cloud. You can download the tools for Vista Studio 2008 and 2010, along with the SDK, from Microsoft.
4: Scalability and flexibility
Using Azure, you can easily create applications that run reliably and scale from 10 to 10 thousand or even 10 million users — without any additional coding. Azure Storage provides scalable, secure, performance-efficient storage services in the cloud.
After you create a Web app, you can specify the number of processors for the application to use. If the application needs to scale up to meet growing demand, it’s easy to change the settings to use more processors. The “pay as you go/pay as you grow” approach lets you bring your new apps to market sooner and respond more quickly to changes in your customers’ needs.
5: Cost benefits and pricing model
Taking advantage of resources in the cloud allows you to decrease your costs for building and expanding your on-premises resources. You can also reduce the cost of IT administration because the hardware is being taken care of for you, off-premises. The cost of creating, testing, debugging, and distributing Web-based applications goes down because you have to pay only for the computer processing time and storage space you need at a given time.
Windows Azure pricing will be based on consumption, with a per-hour fee that’s dependent on the size of the instance for Azure computing services and per-month or per-transaction fees for Azure storage services based on data size. For pricing details, see the Microsoft Web site.
6: Data center in the cloud
SQL Azure provides organizations with all the benefits of an enterprise-class data center without the hassle, headaches, and cost of maintaining such an entity. You get high availability and reliability with redundant copies of your data and automatic failover. No more worries about backing up data yourself.
It’s a relational database model that stores data in the same manner as SQL Server (tables, indexes, views) and thus will be familiar to Windows DBAs, but your SQL Azure Server is spread across multiple physical computers for more flexibility. For information about the differences between SQL Azure and SQL Server, see Similarities and Differences - SQL Azure vs. SQL Server.
7: Support resources
Because Azure uses the same familiar tools and technologies as other Windows platforms, you can take advantage of the well-established support structure within Microsoft and company-provided resources, such as TechNet and MSDN, along with the huge ecosystem of Windows developers outside the company. There will always be someone to turn to when you have questions or problems.
With Azure, you can develop hybrid applications that allow your on-premises applications to use cloud services, such as the cloud database and storage services. Communications services work between on-premises applications and the cloud, as well as mobile devices.
Azure supports open standards and Internet protocols, such as HTTP, XML, SOAP, and REST. There are SDKs for Java, PHP, and Ruby, for applications written in those languages, and Azure tools for Eclipse.
Knowing that security is one of the biggest concerns for companies considering a move to the cloud, Microsoft designed Azure with security in mind. The .NET Access Control Service provides a way to integrate identities, and Security Assertion Markup Language (SAML) tokens are used by applications to determine whether a user is allowed access. Microsoft has designed its compliance framework to meet regulatory requirements. For more details, see my article Microsoft Azure: Security in the Cloud.
10: Something for everyone
Windows Azure can benefit hosting providers, ISVs, systems integrators, and custom software developers. Hosting providers can expand their services to areas where they don’t have existing infrastructure and add new services without more infrastructure investment. ISVs can use Azure to create, deploy, and manage Web apps and SaaS without large capital expenditures, and they can scale those applications more quickly and cost effectively. Systems integrators can take advantage of Azure’s ability to work with existing on-premise infrastructures. Custom software developers can create software solutions for customers who can’t afford the costs of in-house development, including hardware costs, and they can deliver their applications to customers as services without building and maintaining an expensive data center.
I'm having real difficulty figuring out whether this is the next big thing or the next big flash in the pan. I'm also unclear on the (nebulous you might say...) concept, papers on the subject don't really carify it for me.
My questions are specifically:
Software as Service: How is this really different from a well designed SOA archtecture over, say, WCF, other than where the code runs
Who owns the code?
Who writes the code?
Where does your code reside and how do you test it? How "transportable" is the code?
Are you locked into a vendor? If so, the dangers this raises surely outweigh than any efficiency gains you might find.
How are security concerns addressed?
Is this really different than outsourcing a company's hardware function (other than the frameworks involved?)
# Software as Service: How is this really different from a well designed SOA archtecture over, say, WCF, other than where the code runs
# Who owns the code?
# Who writes the code?
# Where does your code reside and how do you test it? How "transportable" is the code?
# Are you locked into a vendor? If so, the dangers this raises surely outweigh than any efficiency gains you might find.
# How are security concerns addressed?
# Is this really different than outsourcing a company's hardware function (other than the frameworks involved?)
I don't think it is.
On Microsoft Servers as I understand it. Published I believe via VS2010.
Not very well last time I read about it. They're addressing it, but it still needs work.
I don't think it is. The idea is that Microsoft takes care of all that stuff for you. You buy the level of service you need and the number of instances you want. It gets very contractual. Think their licensing agreements.
I've stayed away from it for the time being because I can't see any sizable company wanting to allow Microsoft to have control and hostage taking power over their data and livelihood. It sounds like a real downer.
That's called seagull management (or sometimes pigeon management)... Fly in, flap your arms and squawk a lot, crap all over everything and fly out again... by _Damian S_
Thanks for the reply, after one week, an answer! This isn't meant as a criticism of you, it just screams volumes about the amount of work going on in the cloud I think.
People keep screaming "next big thing" on the cloud, but when I look at it, the security concerns and the "ransom effect" will prevent business such as banks (who tend to be the drivers on such things) from ever using it. I hadn't considered Miscrosoft's Byzantine pricing structure, even for something as "simple" as VS2010 we had to get an external consultancy in to find the best deal for our company.Their cloud pricing must be horrific. Some people are really fired up about this, and I've been wrong about technologies in the past (Windows devs are resisting WPF, which I think far superior to traditional Winforms), but I think this is a dud, at least in the medium term. My post was really a last-gasp should I take a look at this tech, or should I do something else question.
Cloud Computing might have a use for SMEs though: the security provided will probably be better than can be acheived in-house,but I suspect Google is a better option.
I was having a beer with one of the MS technical reps for cloud computing in SE Asia a couple of months ago, and asked him this exact question. And you are right the primary target is the SME exactly b/c of the security that MS can bring to the service.
Apparently they have some extraordinary service agreements designed to reassure SME's their data is safe and remains theirs. He did admit that the big end of town were not prospects and banks won't touch it, they have enough trouble controlling their (our) environment without more vapourware thank you.
There you go - 2 replies.
Never underestimate the power of human stupidity
I am a student doing masters in computer science engineering.I wish to develop a Multitenant data analytical application in java.Could any one suggest me the procedure to develop a simple multitenant application.. Or else please suggest me any useful links to proceed further.
I have decided to develop the application using Netbeans..
I wish to develop a Multitenant data analytical application in java.Could any one suggest me the procedure to develop a simple multitenant application.
If you do not know the procedure ho do you expect to develop it? I would suggest you try something more suited to your skills, or do some research into the subject you wish to work on. Google is always a good place to start, or possibly your University library.
Just say 'NO' to evaluated arguments for diadic functions! Ash
I find it disturbing that you feel the need to specify the language here. I get the feeling that you have chosen the language first, and the problem second. This is not a good way to do things; I appreciate that you may well be jazzed up about Java, and fairplay to you but you really need to stop and consider what the problem is that you are trying to sort out first.
The first thing that you need to do is to gather your requirements. Work out what you are trying to do; what problem you expect to solve. Talk to people who are doing the task that you are trying to do and find out how they do it. Where possible, you should always try and model your software after the process it is imitating.
Finally, good luck. I look forward to you passing your course, and entering the world of professional development.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Cloud computing is where the program that an end user wants to run is kept on a company's server. Steam is cloud enabled. For example COD6 had the ability to dl it from steam if you bought it. You can then play the game just as if you had it on a disk. I suppose its kinda like that. Maybe you could define it as a web page too tho...
Well I was drinking with a guy who works for MS here in Singapore, job is to sell cloud/azure services. As I work for a bank he didn't bother pushing it, banks are just not potential customers.
His line went something like, we set up a very secure flexible platform supplying all the dev and office tools you need on a subscription basis. You (as a SME, his target market) cannot afford to implement and support the same level of security MS supplies. It was a good line and he believed it so I didn't have the heart to try and pick it apart (besides I was well into my cups at that stage).
Like most tools it has it's application, it is not the panacea the evangelists claim but has it's uses I guess.
My problem, beside the connectivity nightmare, is that everything is via a browser. I know it's getting better but it is still a pretty crappy interface (this from the guy dragging himself kicking and screaming into Silverlight).
Never underestimate the power of human stupidity
No it isn't. Cloud computing is about having access to resources (compute power, memory, perstistent storage) on an ad-hoc basis, with no practical limits to those resources, at a lower cost than you could supply yourself. It has almost nothing to do with web browsers.
Mycroft mentioned some of the tools built on the platform, but from a development standpoint the way I look at it, cloud computing is a suite of development tools built around making scaling an application out the primary optimization.
That's why many of the cloud platforms have things like NOSQL databases and are web based. Relational databases with strong transactional support are notoriously difficult to distribute so there are many different new models of data storage each of which optimizes a different aspect of the whole scale out problem. There are also different constraints on code management and optimization when it is designed to run as efficiently on one system or one thousand. There are also tools that run horribly on anything under 10 systems but awesome on large clusters.
To further muddy things, Amazon, google and microsoft are selling cloud services based on their particular platforms. But if you have a bunch of systems lying around you can set up your own cloud stack. Some of the systems management for the large installations are mind boggling, with setups of cargo containers full of hardware. They leave the container plugged in and wait for a percentage of the systems to fail in the container and just send the whole thing back to the factory to be rebuilt.
It's a server/client relationship where you are the client, and:
1. You don't own the server or anything installed on it.
2. You have no control over changes to applications installed on the server.
3. The server might be a zillion miles away, and could be routed through a zillion miles of inferior wire or severe bottlenecks at any given time, giving you all the performance of a 386.
4. You can be disconnected from the server and/or services at a moment's notice, for any reason (network problems, billing problems, caffeinated keyboard at the server site problems, the-guy-you-complained-to-on-the-phone-doesn't-like-you problems, etc.) (And don't forget the ubiquitous "computer error" problems.)
5. Your work is accessible to a bunch of people who probably couldn't get jobs as developers, or who barely know what a computer is -- and their secretaries.
6. Anyone with a packet sniffer knows exactly where to put it to access your work, as well as the work of everyone else who uses the same server.
7. Most of your processing power is spent on maintaining contact with the server, up and downloading all manner of unnecessary files, background-installing whatever the server owner decides he wants installed on your local machine, and running background processes for licensing agents, update agents, and secret agents (And that's if you only use a word-processor. If you want spreadsheets as well...)
8. You pay and pay and pay for the above privileges, because the server owners obviously deserve money for nothing.
I wanna be a eunuchs developer! Pass me a bread knife!
Hey, I do enjoy reading your description of cloud computing!
Does anybody remmember the grand idea of "Network Computer"? At that time it was said
that a PC should have all its OS and SW on the network, and it needs neither OS no HD
as network will prvide everything. Pleanty of noise and talks were made about it, with
greatest expections from many. And the result? Total bullshit + nonsense. After a couple
of years, we are all still using PC WITH a OS, and with one or multiple HD.
The present claims about Clouding seems to be repeating that rediculous story. Where
is the common sense? Fortunately no everybody has been carried away by the nonsense!
Last Visit: 31-Dec-99 18:00 Last Update: 25-Sep-22 21:39