3 ms·
Changing a button was just one example. How about this? https://twitter.com/dvassallo/status/1166700686467166208 https://twitter.com/dvassallo/status/1166700686
by DVassallo 7y ago
Changing a button was just one example. How about this? https://twitter.com/dvassallo/status/1166700686467166208 https://twitter.com/dvassallo/status/1166700686467166208
- capableweb 7y agoYou know, instead of linking to your Twitter, you could just embed the content directly here instead. For people who don't want to go to Twitter since they are here, Tweet is about that AWS changed the limit of ElastiCache names from 20 characters to 40 and author says about it: "If you can make a change like this to your SaaS without any fuss, you can probably outcompete AWS on innovation pace and agility. For AWS, this is a significant accomplishment worthy of the “2019 What’s New” page"
- privateSFacct 7y agoInteresting, the claim is that if you can easily change ElastiCache cluster names "you can probably out compete AWS..." It will be interesting to see if that happens soon then. I know IBM and the many other Openshift partners are chasing this. Will be interesting to see if they can deliver. My own view - do not underestimate the depth of services and innovation AWS and GCP can bring to bear. I'm just not hearing folks go - oh, this provider let me use a longer name for my elasticache cluster. Instead its, why shouldn't we just use AWS or GCP.
- jayd16 7y agoThis just seems like a pretty dig. The issue of feature verticals/microservices/soa leading to complex UI interaction is a fundamental issue we can actually sink our teeth into. I'm not really interested in the minutia of particular aws failures.