It's cloud computing. It's just an alternative to buying physical servers and storage.
Within our organization, there are roughly 2,000 employees using this solution. We definitely plan to keep using this solution in the future.
It's cloud computing. It's just an alternative to buying physical servers and storage.
Within our organization, there are roughly 2,000 employees using this solution. We definitely plan to keep using this solution in the future.
It's stable, easy to use, reliable, and cheap.
I have been using Microsoft Azure for the past few years.
This solution is very stable.
Technical support is pretty good. I think they're doing pretty well.
We used to use Amazon AWS.
The initial setup is very straightforward. It only takes minutes because it's cloud provisioning.
I installed this solution myself along with the help of three technical team members.
The price needs to be lower because they're competing with AWS. AWS, price-wise, is sexier. In this case, Azure needs to do better in terms of pricing.
We are on a subscription; we pay on a monthly basis. It's consumption-based, so the price varies depending on usage.
Overall, on a scale from one to ten, I would give this solution a rating of eight. I am satisfied with Microsoft Azure.
I would absolutely recommend this solution to others.
We are a Microsoft Partner for Central America. The solution is in our portfolio, we provide managed services on Azure for our customers and we use it for our services infrastructure.
The most valuable aspect of Azure is the flexibility you have for all the services and solutions it offers, even if you use IaaS, PaaS, or SaaS, you have the option to only pay for the services you use – “pay as you go”, in a Cloud that is compliant with most regulations, using this advantage you have a lot of options and technologies you can adopt, and easily integrate into your infrastructure, to accelerate your Digital Transformation journey.
We integrating Azure to build solutions that we offer to our customers.
Integrate as a service. A lot of Microsoft software licensing options aren’t yet in Azure. Also, the ability to integrate with other technologies, such as other options on the market based on RISC Technologies.
I have been using the solution for 10 years.
I rate Microsoft Azure an nine out of ten.
It comes with a lot of ready-made studies that we can connect with other existing Microsoft applications, for example, Office, Outlook, Chatline, and OneDrive. Everything is behind the scenes running with Azure. It's easy to build the connectors.
They are a bit closed on the customization side. If they open the customization then it will be very good.
It covers pretty much the similar problems that we face in many areas of Azure. If we are planning to use some of the Azure applications within our organization, there are some places that we need to complain about a complaint. Because of the design of Microsoft, we were not able to make this complaint. So, we are not able to use that interface.
I have been using Azure for two years.
The Azure setup itself is a big procedure, but once that setup is done, the adoption is basic, allowing developers to use the Azure platform for their resource site. Then we slowly open the Azure for the website and we slowly allow Azure to impact our office.
We don't have customer reviews of some of those applications. They should provide a lot of understanding. If reviewing and rating also becomes one of the alternatives, I think that will be a big win for them.
They are loaded with functionalities. I would rate Azure a seven out of ten.
They are very open with the options, but customers are not there with the road map. There are too many options. That confusion is a con of the solution.
I would like to see a better understanding about business and compute. Basically, knowledge of your to burn your money efficiently.
We have used this solution for over four years.
There were issues with deployment.
There were issues with stability.
There were issues with scalability.
Customer service is very good. Microsoft Azure support can replace the second level support group. Be aware of it as they are very good at what they are doing.
Technical Support:I would give technical support a rating of 10/10.
We switched solutions due to cost.
It took less than three years for the ROI to be zero. Only experience is left. Over three years is better in-house for the ROI.
These elements are brilliant. It is a no brainer.
We evaluated Lab.
Microsoft recently announced a partnership with Oracle which brings a number of Oracle technologies to the Windows Azure cloud.
In short, they announced:
Items 1 & 2 I’m not that excited about, but it’s item 3 which is interesting.
Microsoft have supported Java on Windows Azure since the start. There’s an SDK and tooling built into Eclipse.
However, Microsoft haven’t been able to install Java, you’ve had to do that yourself. This has meant that the package you deploy to Azure has had to contain the Java installer, any frameworks and web servers you need, as well as your application code. This makes the package too large to work with, in some cases too large to even upload. It certainly slows down application updates.
Utilities such as AzureRunMe have helped bridge this gap, by splitting your package into separate zip files in blob storage which are only downloaded when required. However, ultimately you have to do more work to get Java running, and it takes longer to spin machines up.
Having said that, Java applications work surprisingly well in Azure. Applications are coded against the JVM, rather than the operating system and make relatively few assumptions about the environment. They also tend to use ORMs (like Hibernate) giving you a simple database schema which is easy to port to Windows Azure SQL Database.
I often find that Java applications are quicker to get running in Azure than similar .NET apps.
When we talk about Java here, we’re really talking about the Java Virtual Machine (JVM), the runtime which hosts Java applications.
Java is just one of the languages supported by the JVM, there has recently been a small explosion in language options on the JVM, including:
…to name just a few.
I haven’t got any special knowledge here, but there are few things Microsoft could do now:
Java web applications (in my experience) often hold large object graphs in memory, as state stored against each user session. This means that sticky sessions are required, and the Azure load balancer in Cloud Services is round-robin (sort of). Sticky sessions aren’t very cloud friendly, but it’s difficult to make legacy application stateless.
Whilst there are ways to work around this, they all rely on ‘un-balancing’ the load balancer, and will frequently add network hops and overhead to the processing of each request. We need to be able to select a load balancing strategy on endpoints configured in Azure (i.e. round robin/sticky/performance based decision).
As a side note, the load balancing strategy for Windows Azure Websites is sticky.
Better support for Java on the Microsoft cloud goes well beyond one language, and unlocks a number of possibilities, such as better support for Ruby and Hadoop for example.
Load balancing is one pain point, but something we know they can fix in the platform.
Azure remains an exciting place for everyone from the smallest startup, to the largest enterprise.
As we become more distributed in our everyday lives, we must change our approach and view of how we build software. Distributed environments call for distributed software solutions. According to Wikipedia, a distributed system is a software system in which components located on networked computers communicate and coordinate their actions by passing messages. The most important part of a distributed system is the ability to pass a unified set of messages. Windows Azure Service Bus allows developers to take advantage of a highly responsive and scalable message communication infrastructure through the use of their Relayed Messaging or Brokered Messaging solutions.
-- Relay Messaging --
Relay Messaging provides the most basic messaging requirements for a distributed software solution. This includes the following:
- Traditional one-way Messaging
- Request/Response Messaging
- Peer to Peer Messaging
- Event Distribution Messaging
These capabilities allow developers to easily expose a secured service that resides on a private network to external clients without the need of making changes to your Firewall or corporate network infrastructure.
Relay Messaging does not come without limitations. One of the greatest disadvantages of relay messaging is that it requires both the Producer (sender) and Consumer (receiver) to be online. If the receiver is down and unable to respond to a message, the sender will receive an exception and the message will not be able to process. Relay messaging not only creates a dependency on the receiver due to its remoting nature, this behavior also makes all responses subject to network latency. Relay Messaging is not suitable for HTTP-style communication therefore not recommended for occasionally connected clients.
-- Brokered Messaging --
Unlike Relay Messaging, Brokered Messaging allows asynchronous decoupled communication between the Producer and Consumer. The main components of the brokered messaging infrastructure that allows for asynchronous messaging are Queues, Topics, and Subscriptions.
Queues
Service bus queues provides the standard queuing theory of FIFO (First In First Out). Queues bring a durable and scalable messaging solution that creates a system that is resilient to failures. When messages are added to the queue, they remain there until some single agent has processed the message. Queues allow overloaded Consumers to be scaled out and continue to process at their own pace.
Topics and Subscriptions
In contrast to queues, Topics and Subscriptions permit one-to-many communication which enables support for the publish/subscribe pattern. This mechanism of messaging also allows Consumers to choose to receive discrete messages that they are interested in.
-- Common Use Cases --
When should you consider using Windows Azure Service Bus? What problems could Service Bus solve? There are countless scenarios where you may find benefits in your application having the ability to communicate with other application or processes. A few example may include an inventory transfer system or a factory monitoring system.
Inventory Transfer
In an effort to offer exceptional customer service, most retailers will allow their customers to have merchandise transferred to a store that is more conveniently located to their customers. Therefore, the store that has the merchandise must communicate to the store that will be receiving the product of this transaction. This includes information such as logistical information, customer information, and inventory information. To solve this problem using Windows Azure Service Bus, the retailer would setup relay messaging service for all retail locations that could receive a message describing the inventory transfer transaction. When the receiving store gets this notification they will use this information to allow the store to track the item and update their inventory.
Factory Monitoring
Windows Azure Service Bus could also be used to enable factory monitoring. Typically machines within a factory are constantly monitored to insure system health and safety. Accurate monitoring of these systems is a cost saver in the manufacturing industry because it allows factory workers to take a more proactive response to potential problems. By taking advantage of Brokered Messaging, the factory robots and machines can broadcast various KPI (Key Performance Indicator) data to the server to allow subscribed agents such as a monitoring software to respond to the broadcasted messages.
-- Summary --
In summary, Windows Azure Service Bus offers a highly responsive and scalable solution for distributed systems. For basic request/response or one-way messaging such as transferring inventory within a group of retail stores, Relay Messaging will meet most system requirements. If your requirements call for a more flexible system that will support asynchrony and multiple message consumers, it is better to take advantage of the Queues and Topics that are made available in Brokered Messaging.
Disclosure: The company I work for is a Microsoft Partner - http://magenic.com/AboutMagenic
Windows Azure Backup was recently released as a preview feature in Windows Azure’s already comprehensive suite. This is a great feature, even in its current preview state. However, due to its recent release, it can be difficult to find helpful descriptions of features already available. In this blog, we will highlight five great features of the Windows Azure Backup Preview and a short description of each one.
1. Scheduled Backup
In the world of backup and recovery, scheduled backups are not necessarily a new feature. New or old, it is definitely a convenient and required backup feature, especially for those who value data integrity.
Windows Azure does a great job of providing users with a simple interface that can be configured on the Windows Azure Backup Agent snap in for Windows Server 2012. The snap in (see Figure 1) allows users to easily customize a specific backup schedule, frequency, and granularity for that specific server. After it is configured, the specified data for backup is locally compressed, encrypted, and sent to Azure for storage.
Figure 1: Windows Azure Scheduling Backup Wizard
2. Granular Recovery
While scheduled and convenient backups are helpful, they don’t mean anything unless an equally granular and robust recovery solution is in place. Windows Azure Backup has provided users with just that. The Windows Azure Backup Storage can be recovered from your local server or from the Azure Management Console. The user can decide what folder or file they would like to recover and specify exactly which backup version they wish to recover.
In the event of a server failure, it is even possible to stand up a new instance of that server and recover your data from Windows Azure Recovery Services. Whether you’re missing a file, folder, or entire server, Windows Azure Recovery Services can meet all your needs.
3. Compressed and Encrypted Traffic
If you are already familiar with Windows Azure, you are likely aware that any traffic sent to the Azure Cloud is compressed and encrypted on your local machine before being uploaded. This is not any different for Windows Azure Recovery Services. The reason it has been included as a great feature relates to how it affects your monthly bill. Windows Azure will only bill on your compressed backups. Since Azure charges by GB/month, this can save you a significant amount of money.
4. Competitive Pricing
Windows Azure Backup is a Cloud service; therefore, it is a monthly subscription service just like the rest of Azure’s features. It is priced by the average GB/month. For example, if your compressed storage is 20 GB for the first half of the month and 40 GB for the second half of the month, you will pay the average or 30 GB. The current price is $0.50 per GB/month, but while the service is in preview, Microsoft is offering a 50% discount across the board. This proves to be an attractive and cost-effective option for customers who are considering moving their backup solution to the Cloud. Considering the initial capital saved by choosing a Cloud backup service, this can be extremely beneficial in many scenarios.
Figure 2: Windows Azure Backup Pricing
5. Backups Live in Cloud
In my opinion, the final and most important feature is a simple one. All the backed up content lives in Microsoft’s Cloud. That means two things: (1) no paying for on-premise storage solutions and (2) no data loss during power outages or server failures. It is a simple feature, but if you consider the implications of loosing backed up data, it’s a very important one.
In conclusion, Windows Azure Backup is a highly convenient and robust solution for anyone considering Cloud backup and recovery solutions. The five features described above are only a few of the features included in this fine-tuned machine that is called Windows Azure Backup.
If you are interested in learning more about Windows Azure Backup, please feel free to contact Credera or visit our blog.
We are partnered with both Microsoft and AWS. We use the Azure platform for our systems, and we are also a reseller that offers architecture and design services. One use case for Azure is building Active Directory Systems and creating a hybrid environment for the customers. Another is SQL Database. The third is systems like Linux 365. So we are reselling managed 365 solutions for our customers.
Onboarding customers is a challenge. Sometimes our customers don't know how to deal with the cloud environment. Maybe the customers are more comfortable with the old-fashioned on-premise environment. So it's challenging to move to a new environment in the cloud. Another area where there is room for improvement is maybe security. Also, the interface could use some work. And maybe Microsoft could add some new features for monitoring the environment.
Our company has been using Azure for four or five.
Azure is stable. I don't have any problems with it.
In general, Microsoft support is good. But in some cases, it takes a long time.
The initial setup for Azure was straightforward.
I rate Microsoft Azure six out of 10.
Hi Travis Brown.
Can you please tell that what is the maximum size of message that can be added to the queue for transmission?