The right tool has more to do with ecosystem tools (ex: solid data science libs), runtime constraints (ex: low resources, device driver, embedded), etc. When your constraints are lighter, its more a matter of the what your team already knows and preference.
System components
This is probably the most obvious place for "right tool for the job". After helping team mates write multiple queries, I realized that a graph database is a good option for: "does this user have access to this resource". When there is a dynamic path between the user and resource.
And there are plenty of components with multiple options to choose from. Ex: stateless vs stateful auth. Data shipping vs function shipping. Sharding or replication (or which for what pieces).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Languages
The right tool has more to do with ecosystem tools (ex: solid data science libs), runtime constraints (ex: low resources, device driver, embedded), etc. When your constraints are lighter, its more a matter of the what your team already knows and preference.
System components
This is probably the most obvious place for "right tool for the job". After helping team mates write multiple queries, I realized that a graph database is a good option for: "does this user have access to this resource". When there is a dynamic path between the user and resource.
And there are plenty of components with multiple options to choose from. Ex: stateless vs stateful auth. Data shipping vs function shipping. Sharding or replication (or which for what pieces).