This document discusses four common open source workloads that could be migrated to Azure: 1) Three-tier web applications which typically have presentation, business, and data layers that could utilize Azure VMs, SQL databases, and PaaS services. 2) Websites which are commonly hosted externally and could benefit from Azure's auto-scale, CDN, and security capabilities while reducing costs. 3) Content management systems for internal and external sites that manage content and could take advantage of Azure PaaS offerings. 4) Education management systems like Moodle that address the needs of academic institutions and could utilize Azure VMs or PaaS depending on the solution.

2. Major Characteristics

3. A) 3-tier Web Application
(presentation, business and data layers)
Summary:
The basic architecture for a three-tier web application is very often found in many customers. A server to
host the data layer with a DBMS installed and another one or two to host application’s business objects with
the rules required and the presentation of the user interface is a very common environment in many different
organizations.
Why we should drive this workload to Azure:
This environment tends to be a “always growing” workload YoY in most cases, since the number of users tend
to increase and the performance requirements are pretty much fixed. When based on OSS, all three layers
can be migrated to Azure in very different forms, depending on the specifics of what’s being evaluated. When
considering this workload, we should always address the development, test, quality assurance and production
environments.
OSS softwares commonly used as application and database servers:
MySQL, Postgree, SOLR, Cassandra, Java, JBOSS, Tomcat (application containers), PHP
Initial avg sizing: 4 XL Linux VMs, 15TB storage
Estimated revenue/year: U$ 28,000 in EPG, U$ 14,000 in
CAM
Key industries/segments: all
Target audience as a single scenario: CIO-1, ITDMs, IT pros
Target audience as part of OSS Outsourcing: CIO/CFO
Up & Cross selling:
QA/Dev/Test environments based on proportional config.
Disaster recovery in other geos (replication)
Backup solutions for database and applications
DevOps tools + Visual Studio
Performance monitoring tools
Consulting services
Available Partners:
Key points for the pitch:
• Reduce TCO
• Offload administration in the VM/server level
• Increase the IT capacity to dynamically support business
requirements
• Increase the IT capacity for creating test/dev
environments
• For every PaaS component:
• Auto-scale, CDN, global reach/redundancy and
security (as VMs administration is not required)
• Sys-admins focused on bringing value to on-prem
systems
More info:
Key characteristics. It Looks like a …
• Database layer: IaaS or PaaS (particular analysis is required). Consider each alternative for any Database
supported on Azure (Oracle, MySQL, Mongo, SQL Server and others) or any other product running on a
Linux VM.
• Storage: Evaluate the use of Tables/Blobs
• Rest encryption can be evaluated as value added for security with customer provided keys (probably not
there on-premise)
• Business layer: IaaS or PaaS. OSS components can be packaged and deployed as cloud services. Considering
the case, IaaS can be an option to host a Java container (TomCat, JBOSS)
• Presentation Layer: PaaS looks like a first option. Azure web sites (PHP, Java, Node.js and others)
• More often this scenario would be a compound one as an on-premise migration with hours of services
attached to it.

4. B) Websites
Summary:
Every company or organization host their institutional website somewhere. Usually, if not on-premise
(on an Internet exposed server) it is likely to be on a web development, media or IT
outsourcing provider.
Why we should drive this workload to Azure:
As this workload might generate usage of PaaS services on Azure and benefit customers with
features like auto-scale, CDN, improved security by delegating VMs administration to MSFT
among other reasons, we should approach every customer with our value proposition of
hosting different types of Websites on Azure.
OSS softwares commonly used for Website creation/maintenance:
PHP, Wordpress, Java (Different web servers can be used but not so relevant in the case of a
website migration)
Initial avg sizing: 1 large VM + 800GB egres traffic
Estimated revenue/year: U$ 4,800
Key industries/segments: all
Target audience as a single scenario: CIO-1, ITDMs,
IT pros + CMO/CFO
Up & Cross selling:
Other internal applications with interfaces with the website
CMS applications (content-related)
Disaster recovery with other geos (replication)
Backup solutions
Stoarge
Available Partners:
Key points for the pitch:
• Reduce TCO
• Offload administration and migrate it to PaaS
• Increase the IT capacity to dynamically support
business requirements
• Auto-scale, CDN, global reach/redundancy
• Security (as VMs administration is not required)
• Sys-admins focused on bringing value to on-prem
systems
More info:
Key characteristics. It Looks like a …
• PaaS option. Azure web sites (PHP, Java, Node.js and others)
• IaaS in a Linux VM + <same web server> as the original environment can be an
option when customers are not willing to change the web server for any reason
• Born in the cloud architecture
• Soft migration of contents (copy web files from the original environment to Azure)
• DNS migration with domain provider

5. C ) Content Management Systems
(Internal and external facing)
Summary:
CMS can address a large range of solutions, among them: document management, work flow,
records management, document imaging and web content management. The last one is more
relevant concerning OSS.
Why we should drive this workload to Azure:
As web contents are being used by a large number of customers in their private networks as
well as solutions to manage external web sites with contents that need to be managed in a daily
basis such as blogs, web sites and news threads, we might offer Azure as a platform to such
initiatives.
OSS softwares commonly used as CMS:
Wordpress, Drupal, Alfresco
Initial avg sizing: 1 A8 Compue intensive instance in PaaS
Estimated revenue/year: U$ 22,000
Key industries/segments: all
Target audience as a single scenario: CIO-1, ITDMs, IT pros +
CMO/CFO
Target audience as part of OSS Outsourcing: CIO
Up & Cross selling:
Other internal applications with interfaces with the CMS
Websites (content-related)
Disaster recovery with other geos (replication)
Backup solutions
Stoarge
Available Partners:
Key characteristics. It Looks like a …
• PaaS option. Azure web sites or cloud services
• IaaS could be considered if faced with some technical limitation
• Born in the cloud architecture
• Soft migration of contents (copy web files from the original environment to Azure)
• DNS migration with domain provider
Key points for the pitch:
• Reduce TCO
• Offload administration and migrate it to PaaS
• Increase the IT capacity to dynamically support
business requirements
• Auto-scale, CDN, global reach/redundancy
• Security (as VMs administration is not required)
• Sys-admins focused on bringing value to on-prem
systems
More info:

6. D) Education Management System
Summary:
Many educational institutions in Brazil suffer from the lack of a good platform to create courses,
keep track of classes and engage with their students. The absence of a web solution that is
flexible and at the same time easy to maintain is driving the institutions to develop their own
systems since most ERPs don’t implement an educational module or the ones specific to
academic are way to expensive for the local reality.
Why we should drive this workload to Azure:
Since Moodle is an open source framework for this type of business need, we should capture
this space and combine its value proposition with Azure. Once in use, it will demand use and
services on top of Azure.
OSS softwares commonly used as Education Management System:
Moodle
Up & Cross selling:
Other academic applications as IaaS/PaaS
Disaster recovery in other geos (replication)
Storage and backup solutions
Other applications with heavy interfaces
Available Partners:
Programmers
Key points for the pitch:
• Reduce TCO
• Offload administration in the VM/server
level
• For every PaaS component:
• Auto-scale, global reach/redundancy
and security (as VMs administration is
not required)
• Sys-admins focused on bringing value
to on-prem systems
More info:
Key characteristics. It Looks like a …
• IaaS solution – Moodle over a Linux VM
• PaaS could be used since it was originally packed in PHP by Programmers (local partner)
• Born in the cloud or on-premise migration
Initial avg sizing: 4 XL Linux VMs, 15TB storage
Estimated revenue/year: U$ 28,000
Key industries/segments: Academic
Target audience as a single scenario: CIO-1, ITDMs, IT
pros
Target audience as part of OSS Outsourcing: CIO/CFO