Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
(longer explanation about management of requests, insertion of extralayer that eliminates duplicates and decides where exactly to send a request to. it's about queuing requests to not overload the server and/or(?) api... key value pair model for nosql vs er model for relational ...see rabbitmq)
ML: So we exchange our database and add a amqp-layer in front. I still don't get why it can't be done later?
...
ML: The way i would build up ma my data structures would change depending on the database. Since we are talking about scaling and performance here, we should use matching technologies and approaches.
(very technical discussion, in which Pranav shared his idea of how performance could be handled, with millions of users as well. key value pair model for nosql vs er model for relational)
PS: You don't have to worry about the api part at all right now.
...
ML: Well, it wasn't written down, but we addressed the topic, sure. We haven't been very strict on this but the general criteria are clear. we follow the python coding style guidelines. we wanted to do code rewriews, but since we dont have people doing them, we cant...
ML: i I will do more reading on this anyways, and i really think that a framework change is absolutely possible now. basically were strating from zero now.
PS: i I think django is a backend and it normally doesn't need to scale out.
ML: itIt's also about nosql support and i think django lacks a bit in that.
...