High Level Overview of Windows Azure- EPC Group


Published on

High Level Overview of Windows Azure- EPC Group

Web: www.epcgroup.net | E-mail: contact@epcgroup.net | Phone: (888) 381-9725 | Twitter: @epcgroup
* SharePoint Server 2013, Office 365, Windows Azure, Amazon Web Services (AWS), SharePoint Server 2010 & SharePoint 2007: Review, Architecture Development, Planning, Configuration & Implementations, Upgrades, Global Initiatives, Training, and Post Go-live Support with Extensive Knowledge Transfer | Custom Branding and Responsive Web Design (RWD)
* Health Check & Assessments (Roadmap Preparation to Upgrade to 2013 or 2010) - Including Custom Code & Solution Review
* Enterprise Content Management Systems based on Microsoft SharePoint 2013, Office 365 Hybrid Cloud (Both On-premises and cloud)
* Enterprise Metadata Design, Taxonomy | Retention Schedule Dev | Disposition Workflow, and Records Management | eDiscovery | Microsoft Exchange 2013 Migration \ Integration | Roadmap, Requirements Gathering, Planning, Designing & Performing the Actual Implementation
* Best Practices Consulting on SharePoint 2013, Office 365, SharePoint 2010, 2007 | EPC Group has completed over 900+ initiatives
* Intranet, Knowledge Management, Internet & Extranet-Facing as Well as Mobility (BYOD Roadmap), Cloud, Hybrid, and Cross-Browser | Cross-Platform Solutions for SharePoint 2013 with Proven Past-performance
*Upgrades or Migrations of Existing Deployments or Other LOB Systems (Documentum, LiveLink, FileNet, SAP, etc.)
* Custom Apps, Custom Application Development, Custom Feature, Master Pages, Web Parts, Security Model, Usability (UI) & Workflow Development (Visual Studio 2012, Visual Studio 2013)
* Migration Initiatives to SharePoint 2013 \ Office 365 and those organizations with both on-premises and cloud assets for a SharePoint Hybrid Architecture and Deployment
* Key Performance Indicators, Dashboard & Business Intelligence Reporting Solutions (PerformancePoint 2013, SQL Server 2012 R2, SQL Server 2014, BI, KPIs, PowerPivot, Scorecards, Big Data) and Power BI
* Experts in Global \ Enterprise Infrastructure, Security, Hardware Configuration & Disaster Recovery (Global performance considerations)
* Tailored SharePoint "in the trenches" Training on SharePoint 2013, 2010, 2007 + Office 365
* Support Contracts (Ongoing Support your Organization's 2013, 2010, or 2007 Implementations)
* .NET Development, Custom applications, BizTalk Server experts
* Project Server 2013, 2010, and 2007 Implementations
* SharePoint Roadmap & Governance Development: 6, 12, 18, 24 and 36 months (Steering Committee & Code Review Board Development)
* EPC Group's HybridCloudAdvisor.com - Navigating the Ever Changing World of the Hybrid Cloud to include SLA development & consulting services | advisory | best practices around PaaS, IaaS, SaaS, VDI, Windows Azure, AWS as well as security, compliance & and regulatory issues facing cloud and Hybrid Cloud deployments throughout the globe.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Here we can see that the Front-End layer takes incoming requests, and a given front-end server can talk to all of the partition servers it needs to in order to process the incoming requests. The partition layer consists of all of the partition servers, with a master system to perform the automatic load balancing (described below) and assignments of partitions. As shown in the figure, each partition server is assigned a set of object partitions (Blobs, Entities, Queues). The Partition Master constantly monitors the overall load on each partition sever as well the individual partitions, and uses this for load balancing. Then the lowest layer of the storage architecture is the Distributed File System layer, which stores and replicates the data, and all partition servers can access any of the DFS severs.It is important to understand that partitions are not tied to specific partition servers, since the data is stored in the DFS layer. The partition layer can therefore easily load balance and assign partitions to different partition servers, since any partition server can potentially provide access to any partition.The partition layer assigns partitions to partition severs based on each partition’s load. A given partition server may serve many partitions, and the Partition Master continuously monitors the load on all partition servers. If it sees that a partition server has too much load, the partition layer will automatically load balance some of the partitions from that partition server to a partition server with low load.
  • High Level Overview of Windows Azure- EPC Group

    1. 1. • Client Layer - Used by application to communicate directly with SQL Database. • Services Layer – Gateway between Client layer and Platform layer. • Platform Layer – Includes physical servicers and services that support the Services layer. • Infrastructure Layer – IT administration of the physical HW and OS.
    2. 2. Topics to Review • Windows Azure SQL Database • Architecture • Application Connectivity • Scalability • Windows Azure Table Storage • Architecture • Querying • Best Practices and Considerations • Cost • Transactions
    3. 3. Application Connectivity Considerations And Best Practices • login: [login]@[server] • Idle connections • Long running transactions • DoS guard • Failover events • Throttling • Connection pooling and Retry logic • Latency introduced for updates • No cross-database dependencies
    4. 4. A Seamless Offering from the Private Cloud to the Public Cloud
    5. 5. Scalability Model For The Cloud Cloud Applications • Require Scale Beyond Scale-Up • Demand the Best Economics • Best Price/Performance • Elasticity + Pay-as-you-go
    6. 6. Obstacles • Defining the Tenant • Establishing Tenant’s surrogate key • Elastic Scalability (Splits/Merges/Tenant Moving) • Application Lifecycle Management (Dev; Test; Deploy; Upgrades) • Overcoming limitations of existing tools & available features • Transient nature of connectivity
    7. 7. Azure Storage Architecture
    8. 8. Table Storage Concepts
    9. 9. Table Details Not an RDBMS! Table Entities
    10. 10. No Fixed Schema
    11. 11. Querying
    12. 12. Purpose of the PartitionKey Entity Locality • Entities in the same partition will be stored together • Efficient querying and cache locality • Endeavour to include partition key in all queries Entity Group Transactions • Atomic multiple Insert/Update/Delete in same partition in a single transaction Table Scalability • Target throughput – 20,000 tps/partition, several thousand tps/account • Windows Azure monitors the usage patterns of partitions • Automatically load balance partitions • Each partition can be served by a different storage node • Scale to meet the traffic needs of your table
    13. 13. PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Bikes Super Duper Cycle … 2009 Bikes Quick Cycle 200 Deluxe … 2007 … … … … Canoes Whitewater … 2009 Canoes Flatwater … 2006 PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Rafts 14ft Super Tourer … 1999 … … … … Skis Fabrikam Back Trackers … 2009 … … … … Tents Super Palace … 2008 PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Bikes Super Duper Cycle … 2009 Bikes Quick Cycle 200 Deluxe … 2007 … … … … Canoes Whitewater … 2009 Canoes Flatwater … 2006 Rafts 14ft Super Tourer … 1999 … … … … Skis Fabrikam Back Trackers … 2009 … … … … Tents Super Palace … 2008 Partitions and Partition Ranges