Skip to content

Working area for Azure design patterns. Mostly workloads that don't align perfectly to legacy networking concepts.

Notifications You must be signed in to change notification settings

Vallentyne/GC-DesignPatterns

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 

Repository files navigation

GC Design Patterns

Most GC customers will be able to use patterns that are well described and documented in other areas, such as the Azure Architecture center.

Key elements of application design that generally work well in Canadian Government departments are:

  • hub spoke VNet arrangements for IaaS workloads
  • symmetric network routing requirements (see below)

Some workloads do not immediately lend themselves to these legacy models, and while they most often would be considered PaaS, there is enough overlap to cause confusion for some.

API Management

Not to describe what this resource does, but it does have some unique networking requirements and especially when it is to be used as much as possible inside a customer created VNet.

The most common desire is to have everything contained inside a network, and control everything. API Management can be deployed to a VNET in the "internal" mode, where most of the associated assets are contained in a VNET.

APIM VNET configuration

If everything is good, the status should look green.

APIM VNET status

For more detail, check out the Readme.

Azure Data Bricks

About

Working area for Azure design patterns. Mostly workloads that don't align perfectly to legacy networking concepts.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published