TailwindTraders VS Enterprise-Scale

Compare TailwindTraders vs Enterprise-Scale and see what are their differences.

Enterprise-Scale

The Enterprise-Scale architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture (by Azure)
Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • Scout APM - Less time debugging, more time building
  • SonarQube - Static code analysis for 29 languages.
TailwindTraders Enterprise-Scale
1 9
611 1,035
0.8% 6.0%
0.6 8.4
about 1 year ago 14 days ago
CSS Bicep
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

TailwindTraders

Posts with mentions or reviews of TailwindTraders. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-12.

Enterprise-Scale

Posts with mentions or reviews of Enterprise-Scale. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-30.
  • The "hubs" in "hub and spoke" - how many do you have, and what is the nature of them?
    1 project | reddit.com/r/AZURE | 20 Apr 2022
    Most orgs can probably get away with a single subscription for all of their central platform resources. Take a look at this example. You'll need to scroll down the README a bit, but this condenses the network hub, domain controllers, and logging resources into 1 subscription.
  • How to block all public IP addresses
    1 project | reddit.com/r/AZURE | 26 Feb 2022
    good point, there isn’t a built in definition for it. There is a policy definition called ‘deny public ip’ as part of the Enterprise scale landing zones though https://github.com/Azure/Enterprise-Scale/blob/main/docs/ESLZ-Policies.md
  • Working on a startup, trying to figure out how to layout initial setup...
    1 project | reddit.com/r/AZURE | 15 Jan 2022
    i would suggest looking at this: https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/contoso/Readme.md
  • How are you structuring Hub & Spoke vNets?
    2 projects | reddit.com/r/AZURE | 30 Aug 2021
    Take the example from Cloud Adoption Framework enterprise-scale landing zones hub and spoke architecture https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/adventureworks/README.md. It should'nt be all about vnets, but how you really design the landscape especially for the services you have listed. If you plan to have multiple hubs in different regions and you want a spoke vnet in a hub communicate with another spoke in a different hub you could run into transitive routing issues which you would need Azure Route Server or Azure Virtual WAN to solve. Start from the landing zone architectures because these examples would mostly fit your requirements and are desinged to scale.
    2 projects | reddit.com/r/AZURE | 30 Aug 2021
    The example is for a single region deployment. You are mentioning the potential of more services to be in Azure. Where do you get your subscriptions from? Do you have Enterprise Agreement? If so, then it really doesn't matter and you could reference the example desing. Based on the service you determine the destination subscription. If you have multiple teams/partners working on different services then this design is excellent for RBAC. If you have a small team then you could have a maximum of three subscriptions, from the example desing you could put together the management, connectivity and identity subscription and seperate the resources based on resource groups for RBAC. Each new service that you are offering is in the corp or online subscription and you create your services and vnets and peer them on the basis that should the vnet be corp connected or is exposed to the outside. Something like this https://github.com/Azure/Enterprise-Scale/blob/main/docs/reference/treyresearch/README.md
  • Real live examples or tours of Azure accounts
    2 projects | reddit.com/r/AZURE | 12 Jun 2021
    Make one for yourself and have a play: https://github.com/Azure/Enterprise-Scale
  • SSL VPN Choice for SMB
    1 project | reddit.com/r/msp | 2 Apr 2021
    Roughly inspired by that. I guess you could go much crazier with Azure Firewall, etc...
  • Azure "sub-tenant" like functionality?
    1 project | reddit.com/r/AZURE | 1 Apr 2021
  • How are you managing resource groups in your organization?
    2 projects | reddit.com/r/AZURE | 12 Mar 2021
    If you are a little larger company, you should look at the enterprise-scale part (https://github.com/Azure/Enterprise-Scale)

What are some alternatives?

When comparing TailwindTraders and Enterprise-Scale you can also consider the following projects:

terraform-azurerm-caf-enterprise-scale - Azure landing zones Terraform module

azure-quickstart-templates - Azure Quickstart Templates