5 ms·
Eh. The further AWS moves up the stack, the less dominating their products are. EC2? Awesome. S3? Great. ELB? Good. CodeCommit? Eh. I'd be interested to hear a
by paulddraper 10y ago
Eh. The further AWS moves up the stack, the less dominating their products are. EC2? Awesome. S3? Great. ELB? Good. CodeCommit? Eh.
I'd be interested to hear about experiences using CodeCommit, CodeDeploy, etc. but I doubt AWS found the One True Workflow.
- taurath 10y agoThe more tooling you get around the higher level products, the more whole industries you will capture, at least in part. So many startups are just services adding a bit in the middle of AWS and clients, value that is slowly chipped away by Amazon. Instead of the "full team" you now have an automated lightweight SaaS. AWS's strategy is not looking for the one true workflow, its to envelop enough common usecases that it dominates nearly the whole field, giving you as custom a service as you want.
- paulddraper 10y agoTotally agreed. I call it the "Atlassian strategy": be mediocre at enough things that you become enormously successful. It's a long way from a death knell to competitors though.
- Androider 10y agoThis does seem to be the case. CodeCommit, CodeBuild, CodePipeline and CodeDeploy feel like (and most likely were) developed by entirely different teams, and the actual experience of using any of them is not as good as your average 3rd party provider that fully focuses on just one of the pieces. The main thing the AWS equivalents have going for them at this time is the ultra-low pricing (by selling the underlying AWS services, and mostly not charging for the Code* tools).
- Kocrachon 10y agoI use CodeCommit, CodeDeploy, CodePipeline. I admit, it wasn't the easiest thing to setup. But its nice. When I commit my changes to my mainline, it deploys the code to the host and configures everything for me, and keeps all my hosts up to date. Coworker uses it all to kick off lambda functions. CodeCommit is just a basic Git setup, so nothing special. But working with CodeDeploy and Pipelines is ok. I wouldn't say its much better or worst than other products, and you can use them to deploy to non-aws environments also. I don't know, I can't really sell it well. It does what it does, and it works well enough for me.
- fernandopj 10y agoI use them too, and it works well. However, I do miss the days we used Heroku to handle those deploys _in seconds_ rather than 10-15 minutes AWS uses to roll out an EBS update.
- justicezyx 10y agoHmm, you are missing the big picture. AWS needs these to prevent other players encroach their ecosystem. The higher the upper-stack offerings in the tech stack, the lower the quality is requires to be dominant. But the ecosystem will secure the customers. It's not that you cannot beat AWS in one or two offerings, but you cannot beat them as an ecosystem.
- mooreds 10y ago> It's not that you cannot beat AWS in one or two offerings, but you cannot beat them as an ecosystem. Very true! If you only offer one piece, then you have to 1. integrate with them and other providers And 2. Be substantially better (2x, 5x?) in order to beat the default provided by AWS And 3. Don't forget you are competing with open source options as well (where the cost is the time to set up a solution, but no cash outlay)
- thoughtpalette 10y agoCodeCommit is about 10% where it needs to be in regards to other competitor features. They only support a single archaic code review tool (ReviewBoard). Once they manage a better UI and add additional features around their hosted git, should be a better sell. As is, I wouldn't use it without an extreme organizational requirement.
- stcredzero 10y agoEh. The further AWS moves up the stack, the less dominating their products are. Is this because the further they move up the stack, the more UX matters? That's Amazon's perennial weakness. Remember that Bezos says, "Your margins are our opportunity." They will get around to gobbling your market, unless it requires something that doesn't scale for them.
- mifeng 10y agoThis is called stack fallacy, the "mistaken belief that it's trivial to build the layer above yours," as coined by this blog post from a while back: https://techcrunch.com/2016/01/18/why-big-companies-keep-failing-the-stack-fallacy/ https://techcrunch.com/2016/01/18/why-big-companies-keep-fai...
- paulddraper 10y agoEspecially if your name is the letters AWS and the stack above you requires the letters UI.