Composite Azure Publis her Produc t Sheet Composite 2013-04-04
Composite A/S Nyg책rdsvej 16 DK-2100 Copenhagen Phone +45 3915 7600 www.composite.net
Make Your Website Location-Friendly If you have a popular website, you may eventually face a challenge of keeping serving the content to visitors quickly and without a failure. A common solution is to have multiple “clone” websites that handle load balancing. Plus, having website instances running in different parts of the world, you can point, for example, visitors from Australia to a website instance in South East Asia and Canadians to a North American one, which always makes sure an optimal response time. Windows Azure with data centers placed around the world and its Traffic Manager is perfect for such a solution. And Composite C1 with its seamless integration with Windows Azure is perfect for a location-aware and load-balanced website. You can have a website running locally on WebMatrix, on Windows Azure, your ISP server, anywhere and its multiple “clone” instances on Windows Azure. All you have to do is to ensure that the changes you make on your “source” website are synchronized to your websites in the cloud.
And this is where the Azure Publisher package comes in handy allowing you to publish these changes to your multiple website instances on Windows Azure. The websites in the cloud must be "read only" or need Azure-aware code. And with its website-downloading feature, you can easily set up a "staging" environment by downloading a "production" website running on Windows Azure to the host of your choice, make changes on this staging website and publish those changes back to the production website. The user-friendly administrative tools for managing the publication are integrated into the C1 console.
Page 2 of 6
Composite Azure Publisher Product Sheet
All you need to do is to provide some information on your Windows Azure account and the website instances, and from now on, whenever you change something on your website, simply publish them into the cloud and monitor the progress as you go.
Features The following are major features of the Azure Publisher package:
Synchronization to multiple instances Various options for the source website Quick synchronization Status information Synchronization progress monitoring 4 licenses for various scaling-out needs Website download Performance counters Blob change log
Page 3 of 6
Composite Azure Publisher Product Sheet
Synchronization to Multiple Instances Do you have one or more instances of your website in the cloud? Actually, it doesn’t matter, provided that they use the same storage and are “read-only” or have Azure-aware code. So you can be sure that the latest version of your website is always available to visitors from various parts of the world.
Various Options for the Source W ebsite Do you run your original website locally on WebMatrix, remotely in the cloud on Windows Azure or on your ISP server? No matter where you website is running, with the Azure Publisher package aboard, you can make changes have them published into the cloud.
Quick Synchronization Wondering how long it will take to synchronize changes? The first synchronization might take a while depending on the size of your website. All the further changes will normally take a short time because only the files that have been changed will be synchronized.
Page 4 of 6
Composite Azure Publisher Product Sheet
Status Information Do you want to know whether it is about time to update your website instances in the cloud? The information about their update statuses will help you decide.
Progress Monitoring Interested in what websites have been already updated or how much is left to synchronize after you click Publish? The progress is being monitored and presented to you real-time - just watch.
4 Licenses for Various Scaling -Out Needs Do you own a single-instance website on Windows Azure? Use the free license and pay nothing. Want two instances of the same website? Use the cheapest license. And pay more if you want more – instances or data centers.
Page 5 of 6
Composite Azure Publisher Product Sheet
W ebsite Download Publishing changes from the “staging” website to the “production” website? How about making a “staging” website from the “production” website first? Download a "production" website from Windows Azure to the host of your choice. Then make changes on this “staging” setup and publish the changes back to the “production” website.
Performance Counters Wondering how much of the resources your website instances are using on Windows Azure? Check performance counters right in your “source” website and for as many instances and data centers as you have.
Blob Change Log Need to know exactly what website files have been modified when you publish changes to your website on Windows Azure? Or wondering exactly when a specific file has been changed? Why not look up those in the blob change log? It will show when and what right in your “source” website.
Page 6 of 6
Composite Azure Publisher Product Sheet