|
|
|
|
|
by ianamartin
2817 days ago
|
|
Totally agree with this. No idea why anyone would do things different. Other paradigms are cool and fun, but if you need to get your prototype out there now, this is absolutely the way to do it. I do the same thing with the components of the monolith. I'll use Pyramid + SQLAlchemy + WTForms all day long with a reasonable separation of concerns. When I hit a real problem where the ORM is causing a bottleneck, hey, that's a good time to drop the ORM and use stored procs. Same thing with almost any element of the web app. When it's a clear bottleneck, drop one layer of abstraction and move on. This will get you excellent performance without the overhead of an SPA for 99% of your use cases. Design your way around page refreshes, and judiciously apply ajax calls, and you're done. If you aren't one of the big 5, this is good enough, even with a slow language like Python. |
|