Re: exaggerated title...
Just to be clear - I picked Aurora for it being easily name recognizable, not for its complexity. Simple tasks are not the issue here, complicated, advanced ones are.
What I see as success factors are:
- don’t go hog wild on multiplying alternatives. Too many dilutes the knowledge pool and drives back to the better known: AWS, Azure.
- be sensitive to knowledge pools. Good docs, for sure. But then spend $ on blogs YouTubes podcasts that _explain_ not just market. Digital Ocean has brilliant mini blogs about configurations, for example.
- Keep it simple at first. And mimic known Azure and AWS setups (or simplify them). Or follow/define standards. Advanced features are great but if they require complex configuration that isn’t commonly known about : people will nod out faster than attending a Baptist revival choir on a hangover.
- be careful around X-Y integrations. In the existing US vendor world, the most common combinations draw people because they are most known about. A dominant X will have its customary, known, Y pairings. In a world where X’ and Y’ alternatives are not yet fully established, each X’ needs to make sure people know their way for integrations (that’s probably why Digital Ocean writes up so much quality guidance). Work on interop with your peers.
> it's a vicious circle of "everyone uses X…”
That is PRECISELY my point. To me, apps aside, that is very much what doomed BB10 despite having a solid offering. You don’t have to despair that it cant be overcome. But you do have to allow, watch for and compensate.
p.s. I am a happy DO user, no other links.