The conference is over, I'm back home and it's time to digest and make plans. AWS re:Invent 2017 was my first big conference and it was a lot of fun. I learned a lot, and now I have a bunch of new stuff to learn. When will it end? Hopefully never!
Here is the list of the announcements that I was hoping for and never dreamed they would announce.
DynamoDB Global Tables
The biggest and most welcome announcement at re:Invent for me was DynamoDB Global Tables. Yep, Kubernetes support, graph databases and Golang for Lambda is great and all, but cross-region replication is going to be a hit at work. No more loading 100's of GB in three regions from a Data Pipeline job that takes days. YAS!!!
The announcement of AWS Neptune was a complete shocker for me. I've been researching graph databases for a couple of months and the industry is decidedly against using the common graph database flavors in a transactional system like the one I work on.
Time will tell, but from what I've read, Neptune is limited to an in-memory store with read replicas in the same region. For me, that won't work. I still think Dgraph would be a better fit with their distributed transaction and multiple machine support. I might start a Dgraph POC in a few weeks and I'll try to blog about the results.
Most cloud providers now have Kubernetes support and it could not have come at a better time. I still need to dig into Kubernetes more and start using it in anger. This announcement was expected but nice to hear.
Go for Lambda
This was a surprise and a very welcome announcement. It's not released yet, and we did not get a good timeframe for its release. Or at least good enough for me. When it is, we will be using it heavily at work.
For those of you that have never been to one of these conferences, here is what my days looked like. I was lucky that all of my sessions were in the Venetian Hotel. Other people I went with had to move between two or three hotels during the day.
|ATC303||Cache Me If You Can: Minimizing Latency While Optimizing Cost Through Advanced Caching Strategies||11/27/17 10:45 AM|
|ATC301||1 Million bids in 100ms – using AWS to power your Real-Time Bidder||11/27/17 12:15 PM|
|GAM307||Ubisoft: How For Honor Runs Using Amazon ECS||11/27/17 1:45 PM|
|GAM401||Designing for the Future: Building a Flexible Event-based Analytics Architecture for Games||11/27/17 3:15 PM|
|DAT321||From Minutes to Milliseconds: How Careem Used Amazon ElastiCache for Redis||11/28/17 9:15 AM|
|ARC209||A Day in the Life of a Netflix Engineer III||11/28/17 10:45 AM|
|ARC401||Serverless Architectural Patterns and Best Practices||11/28/17 1:45 PM|
|DEV206||Life of a Code Change to a Tier 1 Service||11/28/17 3:15 PM|
|DAT305||ElastiCache Deep Dive: Best Practices and Usage Patterns||11/28/17 4:45 PM|
|GEN25||Andy Jassy's Keynote||11/29/17 8:00 AM|
|DAT328||Tinder and DynamoDB: It's a Match! Massive Data Migration, Zero Down Time||11/29/17 11:30 AM|
|DEV314||Monitoring as Code: Getting to Monitoring-Driven Development||11/29/17 1:45 PM|
|DAT304||DynamoDB - What's new||11/29/17 3:15 PM|
|GEN06||Werner Vogels' Keynote||11/30/17 8:30 AM|
|ARC319||How to Design a Multi-Region Active-Active Architecture||11/30/17 11:30 AM|
|DAT327||DynamoDB adaptive capacity: smooth performance for chaotic workloads||11/30/17 2:30 PM|
|ARC321||Models of Availability||11/30/17 4:00 PM|
I think I'm going to need the rest of 2017 to recover, but all in all, I think it was worthwhile to go to the conference even though you could watch the reply on Youtube. If you ever have the chance to go, you should take it. One of the benefits of going is speaking to the engineers who built the systems you use. I had a great conversation and a good chuckle about AWS support with them. See you next year at re:Invent 2018.