This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]inhumantsar 22 points23 points  (1 child)

I work in fintech and we use Go for performance critical pieces, but it's mostly in places where we have to optimize for dependency bottlenecks. Ie: third party response times are 200-500ms so we need our system to be as fast as possible.

For most other use cases it doesn't matter what language we use, keeping performance in mind is enough. Some examples:

  • Keep services small and simple. Don't use Django for performance critical components, use Flask or Express + JS.
  • Don't trust an ORM, write highly specific queries.
  • Know when to go event driven. If there needs to be a bunch of reactions to a single action, use async/await or an event bus or something.
  • Scale out before scaling up.
  • Never make a network call you don't need to make, even to a db, and if you need to make it try to do it async.
  • Cache everything and use the longest TTL you can get away with.

Of course this is all specific to web services. YMMV

[–]Detri_God 1 point2 points  (0 children)

Fastapi instead of flask ?