[tmwatson100]

Correct, writing code does not make money. However this change is a little bit like starting a blog... You don't see the immediate benefits straight out but you'll realise them over time. You can put it off and put it off but the longer you do the harder it gets, especially in this scenario.

This architecture doesn't make sense for everyone and we could have continued with Django. But making these changes now mean that we will be able to fix all the above a lot quicker going forward.

[adambratt]

Don't take this the wrong way, but you have 3 people writing code right now according to your Team page on the website.

Isn't it way more confusing to have a bunch of different code repos that only a single person owns? Sounds to me like you'll be locking up too much code in a single individual's head. Not to mention if they're using different frameworks and libraries you're only going to add to the headache.

For smaller teams, it usually is best to stick with one or two codebases/languages for your backend. Sure there are often "better" tools for specific applications but at the end of the day there's usually a way to handle them with your existing codebase that will let you scale for now.

As an example, we needed a robust messaging framework to support our chatrooms and private messaging features. We originally built it out in Tornado, then switched to NodeJS with a rabbitMQ backend, and finally realized it was easier for us to just use PubNub and fire off the pushes from our main Django app. It'll scale with us for probably 10x our current size and by that time we'd have a team of 4-5 people dedicated just to this feature anyways.

[indymike]

Finding architecture that makes sense to everyone is a tall order.