856 karma · joined December 6, 2009
Frequent speaker and author on tech subjects. Expert in building, scaling and maintaining complex web applications with Python, Django, React, PostgreSQL usually on Kubernetes.
Email: frank@revsys.com Twitter: @fwiles Mastodon: https://frankwiles.social/@frank Homepage: https://www.frankwiles.com/ LinkedIn: https://www.linkedin.com/in/frankwiles/ Work: https://www.revsys.com
https://grove.io/blog/grove-here-stay
Happy to help in any way if you're having trouble with it.
As for recommendations you should be looking at Ruby on Rails and Django as your first two choices in my opinion.
Adding far future Expires headers and ETags would also help the perceived user download/render time. Neither are HUGE deals mind you, but easy to do for a bit of extra snappiness.
Perhaps it's a double standard on my part, but the sexism in our industry is poisonous to our future and I think we would all be better off if we considered these topics to simply be off limits.
As for PEP712, while I wouldn't present it at a conference, I would be ok with whatever flack I received due to using the first two letters of a profane word.
However, I would also expect to be spit roasted online and hopefully in person if the proposal was to pop up a nude porn pic if all of the tests passed.
While it is "raw performance of one part of the system", it's also the hardest aspect of a system to scale properly. Not doing these three things can often get a user months or years further down the line without having to worry about it at all.
It's really more about using the right tool for the job, Splunk, Loggly, NoSQL solutions, etc. are a MUCH better fit than an RDBMS for this sort of work.
Startups are hard enough as it is, no need to make them harder.