re:Invent is coming - and the frenzy of releases that will build up to the event is just around the corner.
I have always had in the back of my mind that all the products announced at re:Invent are great for the press releases and the small digs at other vendors, but sometimes it takes a while until we actually get what was announced on stage in front of ~20,000 people and the rest of the world.
And I went out to look for some data. It is obvious that not everything that we heard about on stage was baked and ready for production use.
Here are some examples from last years re:Invent
EKS (188 days)
Bare Metal (170 days)
https://aws.amazon.com/about-aws/whats-new/2018/05/announcing-general-availability-of-amazon-ec2-bare-metal-instances/ (May 17, 2018)
Serverless App repo (83 days)
Neptune (183 days)
Aurora Multi-master (Still not released)
Yet to be released (Oct 14, 2018)
Aurora Serverless (254 days)
IOT 1-click (169 days)
Translate (127 days)
Transcribe (127 days)
Appsync (137 days)
S3 Select (126 days)
Lex (141 days)
PostgreSQL for Aurora (329 days)
GreenGrass (190 days)
X-Ray (140 days)
https://aws.amazon.com/blogs/aws/aws-x-ray-update-general-availability-including-lambda-integration/ (Apr 19, 2017)
Batch (36 days)
Lambda Edge (229 days)
At a glance it looks like the average amount of time from the list above was about 5 months.
Now don’t get me wrong. For all of the above items that were not actually available at re:Invent - I would estimate that there were the same number of products (if not more) that were available (at least in a limited number of regions) the same day they were announced. Above and beyond - the problems that AWS is trying solve and really complex - and a almost all of them have never been done before - so please AWS take your time in developing the game changing technology that you have been giving to the world.
So when Andy Jassy and Werner Vogels get up on stage at the end of November, and announce whatever wonderful stuff they are going to announce - we should all take into account that it could take anything from 1 day to almost a year until we can actually use it in all the AWS regions that we are consuming today.
How can this / does this affect you? I can give an example from the EKS announcement. We were actively looking at a kubernetes deployment on AWS and were contemplating whether we should deploy our own or wait for the managed solution that was announced at re:Invent.
Since we did not have an official release date - we decided to roll our own - and not wait for some some unknown time in the future.
It is nice to know what is coming. You will need to evaluate how long you can wait - are you ready to go with a version one product (that could / will probably have a good number of limitations) or come up with a contingency plan to solve your issues.