patmyron/cloud

cloud region / instance type data

cloud's Issues

external software support lag

• function runtimes
  • node
    • 4: Sep 2015, Apr 2016, X
    • 6: Apr 2016, Mar 2017, X
    • 8: May 2017, Apr 2018, Jul 2018
    • 10: Apr 2018, May 2019, Apr 2019
    • 12: Apr 2019, Nov 2019, Jul 2020
    • 14: Apr 2020, Jan 2021, Jan 2021
    • 16: Apr 2021, May 2022, Aug 2021
    • 18: Apr 2022, Nov 2022, Nov 2022
  • python
    • 3.7: Jun 2018, Nov 2018, X
    • 3.8: Oct 2019, Nov 2019, Jul 2020
    • 3.9: Oct 2020, Aug 2021, Jan 2021
    • 3.10: Oct 2021, X, May 2022
  • .net
  • ruby
  • go (only GCP releases minor versions)
  • php (GCP only)
  • java (versions don't overlap)
    • 8:
    • 11:
    • 17:
• DB engines
• K8s

https://endoflife.date/

https://docs.aws.amazon.com/lambda/latest/dg/lambda-releases.html
https://cloud.google.com/functions/docs/release-notes

region sizes

https://ip-ranges.amazonaws.com/ip-ranges.json

https://old.reddit.com/r/aws/comments/j3luvy/can_anyone_tell_me_or_send_me_documentation_on/g7dl4ip/

from collections import defaultdict
import requests
prefixes = requests.get('https://ip-ranges.amazonaws.com/ip-ranges.json').json()['prefixes']
regions = defaultdict(lambda: 0)
sum = 0
for prefix in prefixes:
  mask = prefix['ip_prefix'].split('/')[1]
  regions[prefix['region']] += 2**(32-int(mask))
  sum += 2**(32-int(mask))
for region in regions:
  print(region + ": " + str(round(regions[region] / sum, 2)))
print('total:', sum//1000000, 'million')

us-east-1: 28%
us-west-2: 15%
eu-west-1: 09%
us-east-2: 07%
ap-northeast-1: 06%
eu-central-1: 06%
GLOBAL: 04%

total: 124 million

region price

https://azureprice.net/Region
https://www.concurrencylabs.com/blog/choose-your-aws-region-wisely/
https://leaderboard.vantage.sh/
https://cloud.withgoogle.com/region-picker/
https://github.com/GoogleCloudPlatform/region-picker/blob/main/data/prices.json

region latency

https://www.cloudping.co/
https://www.cloudping.info/
https://aws-api-latency.wolfe.id.au/
http://awsspeedtest.xvf.dk/
http://www.azurespeed.com/
https://azurespeedtest.azurewebsites.net/
http://www.gcping.com/
http://www.gcloudping.com/
http://cloudping.bastionhost.org/en/
https://medium.com/@sachinkagarwal/public-cloud-inter-region-network-latency-as-heat-maps-134e22a5ff19

https://utdemir.com/posts/choosing-cloud-regions.html

AWS availability zones differ by account

This is a nuance which may or may not be helpful. Feel free to close.

With regard to AWS' Availability Zone count in us-west-1, three is the correct documented count. However, AWS only ever lets an account have two availability zones. The third zone is virtually non-existent and similarly unusable.

Region map

https://www.atomia.com/wp-content/uploads/2016/11/[email protected]

https://increment.com/cloud/weather-control-as-a-service/

https://drive.google.com/open?id=1hoeQqcNXo0E5jNRJDjAhUVGrsHqm2iWa

https://mapthe.cloud/

https://www.infrastructure.aws/

https://cloud.google.com/about/locations

https://infrastructuremap.microsoft.com/

Region timeline

http://patmyron.com/aws-timeline

(based on EC2 instance type timeline: https://instancetyp.es/)

Time to provision resource types

old graph:

https://plot.ly/~PatMyron/13

https://github.com/jaredtrog/cfplot

https://aws.amazon.com/blogs/devops/how-we-sped-up-aws-cloudformation-deployments-with-optimistic-stabilization/