News for hackers. Stuff that matters.
Re:Discover Flask by icpmacdo on Sunday February 21, 2016 @02:32AM (#11143683)
I don't know anything of flask or python really. Is Flask in python 2 or 3? Do I go learn python 2.7 right now or Python 3? Is stuff broken the the eco system. Does it make sense moving over from JavaScript for easier backend CRUD'ish app's? Thanks HN.
Re:Discover Flask by devishard on Sunday February 21, 2016 @03:10AM (#11143769)
Python 2.7 will be around for a while due to legacy code, but it's only a matter of time before Python 3.x is more widely used. Don't invest time learning skills that will only dwindle in value.

Some stuff is broken in the ecosystem. That's true of all ecosystems. If you're coming from the JS world it's far, far better. But if you are importing every 0.x versioned library that vaguely solves a problem close to your problem, no ecosystem will save you.

Python is a solid choice of language for the back ends of web applications.

Re:Discover Flask by lrem on Sunday February 21, 2016 @05:30AM (#11144006)
> Python is a solid choice of language for the back ends of web applications.

With caution advised when it comes to scaling. You might, or might not, pay a pretty hefty premium in the amount of hardware needed.

Re:Discover Flask by MichaelBurge on Sunday February 21, 2016 @08:21AM (#11144385)
You can always rewrite it if needed. A tactical rewrite of specific heavily-used routes that cuts out unnecessary abstractions often doesn't take too long and gets most of the benefit.

I can't see even a slow interpreted language being unable to process 100 requests/second. That leaves like 40 million clock cycles per request. Especially since they tend to come with built-in bytecode compilers, and most of the pure algorithmic code is written in C. Most web requests just don't take that much work to answer.

Most performance issues I see with web applications are somebody writing ORMTable->find(x) in a loop or the equivalent, and then papering it over with a cache(or 3). Or memory leaks. Or badly-written SQL queries(no index, too many indices, disabling seq scans, using CTEs to elegantly 'refactor' SQL, etc.). Or doing blocking calculations/service requests as part of the original web request. The underlying language is almost never what's holding them back.

Re:Discover Flask by CuriouslyC on Sunday February 21, 2016 @12:06PM (#11145284)
In addition to the things other people have mentioned, you also have the ability to easily call C code from python (compared to the unpleasantness that is JNI, for instance), and there are tools like Cython, Numba, Blaze, etc that let you rewrite your hot code into a more performant variant.

Of course, at megascale these optimizations might still not be sufficient, but there is no reason you can't deliver hundreds of thousands of requests per second very affordably with a python stack.

Re:Discover Flask by ianamartin on Sunday February 21, 2016 @06:37AM (#11144124)
I don't want to come across as a Python zealot here, but in my experience, Python has almost never been the problem in scaling. Certainly not to the extent where I would say that it costs a premium in hardware. Though, I suppose it depends on the application.

My experience has been that Python will give you more than enough rope to hang yourself with, and lots of apps that are meant to scale have some homegrown crap of an architecture, or people try to get fancy when they don't need to and try to write go or scala in Python.

If you have a clear understanding of your data model, Python backends scale quite well vertically. Run one instance of your app per core you have available and use IPTables to round robin (or whatever. you can get fancier if you feel like it) to each app instance. Boom. You are now banging on all 4 or 8 or however many cores your server has without the context switch overhead of the multiprocessing module and also without the headaches that go along with the shared memory space of the multithreading libs. Not to mention cleaner, nicer code.

If you build your product to work well in this way, then scaling horizontally also becomes a non-issue as far as Python code is concerned. You just put haproxy in front of multiple machines, set up health checks, and for the vast majority of use cases, you're done until you need to scale the storage horizontally. Then you have some serious decisions to make. But that's a different topic.

But back to my original point: every case where I've seen Python being all slow has really been an artifact of a crap architecture, or bolting on crap front end frameworks, or depending too much on an ORM like SQLAlchemy without really understanding your data and depending on it to do everything for you instead of thinking rationally about what your data is. Or some combination of all three above.

Yes, I know that there are languages that execute much faster than Python. I work with C#/.NET/SQL Server almost as much as I use the Python/Pyramid/PostgreSQL stack. I can write a crappy, slow, messy architecture on either stack. And in fact, when I was first getting to know C# and still writing Python code in that language, I did that.

The bottom line is that if you understand the strengths, weaknesses, and idioms of the language you are working with right now, almost every high-level language in common use today is sufficient for massive-scale deployments for the most common types of web apps. Heavy computing or scientific purposes obviously excepted. But most web apps that scale to hundreds of millions of users are basically "window-on-data" type applications.

I can't really think of a case where some other language besides Python would be noticeably cheaper hardware-wise.

Maybe you have to know your entire stack a bit better if you want scalable Python apps, maybe you have to do a little more Jiggery-Pokery with your Linux servers, but if you are serving at massive scale, you are going to have to go there anyway, especially when you start dealing with storage. That's part of the game.

Re:Discover Flask by nawitus on Sunday February 21, 2016 @08:32AM (#11144416)
> Run one instance of your app per core you have available and use IPTables to round robin (or whatever. you can get fancier if you feel like it) to each app instance.

But if you're using Flask and you have 4 cores with 4 instances, and you're making 4 database requests at the same time you're whole application is suddenly locked. And it's not uncommon for a single view to make up to 4 separate database requests. Most modern web applications are I/O bound, therefore a single Node.js process would have better performance here.

Re:Discover Flask by dorfsmay on Sunday February 21, 2016 @09:51AM (#11144697)
Wait, in PROD, you don't use Python as the server, you stick uWSGI in front of python/flask, that will deal with the network I/O limitation.
Re:Discover Flask by nawitus on Sunday February 21, 2016 @12:18PM (#11145353)
How does uWSGI help here? The OP recommended running 4 instances of Flask/Python, and with uWSGI you still have 4 instances. It doesn't help with I/O.
Re:Discover Flask by dorfsmay on Sunday February 21, 2016 @03:54PM (#11146465)
Because with uWSGI you can mix a number of threads and processes (recommended because more processes than cores wastes time with context switches, and a low number of threads per process is a waste of cycle. uWSGi is an event loop (not unlike node) which makes dispatching requests to threads and processes very easy.
Re:Discover Flask by devishard on Sunday February 21, 2016 @11:24AM (#11145078)
It has not been my experience that web applications are I/O bound using typical architectures in Python. I think you would have a very hard time arguing that Node.JS is more performance than nginx.
Re:Discover Flask by nawitus on Sunday February 21, 2016 @12:19PM (#11145360)
"It has not been my experience that web applications are I/O bound using typical architectures in Python."

Okay, my experience differs. Most modern web applications are relatively lightweight, and are mostly "proxies" or thin wrappers between the load balancer and the database.

Re:Discover Flask by devishard on Sunday February 21, 2016 @05:02PM (#11146821)
That's exactly the kind of apps I usually write, and nginx is fast enough that the DB is typically the bottleneck. In rare cases I've run into CPU as the bottleneck for computationally intensive tasks. If I/O is your bottleneck, then that indicates to me that Node.JS is actually performing worse for you on I/O than nginx is for me.
Re:Discover Flask by ianamartin on Sunday February 21, 2016 @08:46AM (#11144465)
That hasn't been my experience. If your ACLs are set up properly, you won't encounter a full table lock, and therefore won't have problems like you described.

I agree that this could be a problem in theory. In practice, it has not been. Again, it boils down to how you architect your code.

EDIT: you need to stick your sessions to a specific instance. Otherwise, you are correct that there's a problem. But as long as you stick your sessions, there's no problem with a database lock.

Re:Discover Flask by nawitus on Sunday February 21, 2016 @12:20PM (#11145368)
I wasn't talking about database locks. My point was that making a database request takes a really long time relative to processing a request in the web application. Therefore the web application spends most of the time doing nothing and waiting for the database request to complete.
Re:Discover Flask by ianamartin on Sunday February 21, 2016 @01:08PM (#11145626)
So, write data-backed applications without calling a database?

Not sure what you are getting at here.

If you are talking about the raw scalability of your database, yes, you are correct. The speed with which you are able to get info from your DB will be a limiting factor.

But that's a totally different point than the one I was making, which was about how to scale Python, not your database.

If I understand you correctly, the time spent in retrieving stuff from your database will be a limiting factor no matter what language you are using. The DB I/O will eventually limit C# or go or node.js or whatever. I really don't see how this is relevant.

But since you brought it up, you can really cut down on data access times by relying less on ORMs and getting your fingers dirty with stored procedures and building tables that make sense to SQL instead of pretending everything in your RDBMS is a class.

Re:Discover Flask by nawitus on Sunday February 21, 2016 @01:43PM (#11145804)
Node.js can asynchronously make multiple (i.e. hundreds) database requests without locking the instance.
Re:Discover Flask by mixmastamyk on Sunday February 21, 2016 @03:09PM (#11146224)
Why do you believe four requests from python would lock a database but hundreds from js wouldn't?
Re:Discover Flask by carlosrg on Sunday February 21, 2016 @07:10AM (#11144202)
> it's only a matter of time before Python 3.x is more widely used

I've been hearing that for a long time...

Re:Discover Flask by cyphar on Sunday February 21, 2016 @02:39AM (#11143698)
You can use Flask with either Python 2 or Python 3. I personally use Python 3 for everything, so I can't comment on packages that don't work in Python 2.
Re:Discover Flask by icpmacdo on Sunday February 21, 2016 @03:03AM (#11143760)
Any experience with meteor vs flask and if its worth going through one or the other these days. Flask seems better hooked up to Postgres than meteor and having weird stuff with mongo but I'm still new to backend.
Re:Discover Flask by devishard on Sunday February 21, 2016 @03:29AM (#11143792)
I would choose Flask over Meteor any day. JavaScript is the unholy union of various browsers introducing hacks which are then standardized by committee. Considering that's the design process, it actually is pretty well done. But there's no reason to inflict JavaScript on yourself when you can use a language with a coherent design.

I haven't used meteor, but I have used a few other JS frameworks and libraries on the backend. My major criticisms of JS on the back end are: they like magic, in that they tend to decouple code to the point that there's no way to trace the code. Instead, pieces are structured and tied together by convention, i.e. thingController goes with thingModel, and stuffController goes with stuffModel. It creates terse code, but a) if you need to do anything slightly unique (and you will) you're screwed, b) it's a huge pain to debug and trace because you can't just read function calls, and c) since the JS world doesn't care about reverse compatibility, you have to always know when the convention changes, and if you fall a few versions behind, you're basically stuck there. In particular, Ember.JS gave me PTSD. Meteor may avoid some of these issues, but when I evaluated it a while back it didn't seem like it did.

Re:Discover Flask by auvrw on Sunday February 21, 2016 @08:02AM (#11144327)
reframing the question to "python vs. node" on the server-side, the answer seems very dependent on the use-case. there's not (to my knowledge?) much agreement in the python community about how to compile to javascript, much less regarding an ecosystem of client-side libraries. if a rich client-side that shares logic with the server-side is part of the story, i don't think python is a good choice. i wonder if the Django project could do anything a/b this or if it's too big a chunk to bite off?

all that aside, i like Flask a whole lot. Proxy objects are brilliant, and i wouldn't be surprised if koa.js was partially influenced by Flask. i'm considering going back and fiddling w/ Sinatra for the project after next as i'm given to understand that it was a partial inspiration for Flask's routing.

all in all, there's a lot of cross-pollination. i suppose jquery + html -> frontend framework (angular, marionette, etc.) -> express.js + sequelize/bookshelf -> Flask + SQLAlchemy would be a pretty smooth transition w/ lots of docs, stack overflow, community, and sample code to help out.

Re:Discover Flask by devishard on Sunday February 21, 2016 @04:52PM (#11146768)
I don't think many python devs are espousing Python for the client side. I use react/underscore/Jasmine/sinon with ES6 run through Babelify for the client side.

Sharing logic between client and server side means that your client and server side don't have clearly-defined responsibilities. The one exception to this might be input syntax validation, but generally that's a place where you don't want to roll your own anyway.

Re:Discover Flask by auvrw on Sunday February 21, 2016 @10:11PM (#11148168)
idk, could imagine wanting computation to run on the client when it's a desktop (to save server cycles) or the server when it's mobile (to save battery)... not a level of optimization i practically run into, but not an unreasonable example.

i guess a better thing to say is "exactly": specs often change and responsibility gets shifted around. so "runs everywhere" can be useful, whether it be js or otherwise.

Re:Discover Flask by devishard on Tuesday March 01, 2016 @11:59PM (#11208169)
I disagree, that's a totally unreasonable example. Not only is that a bizarre combination of requirements, but that's not a good way to approach meeting those requirements. I'd write the code to run on the server and then profile and optimize on the server. JavaScript if never going to outperform hot spots rewritten in C.

You're forgetting the first rule of optimization: profile.

Re:Discover Flask by nawitus on Sunday February 21, 2016 @08:35AM (#11144425)
> But there's no reason to inflict JavaScript on yourself when you can use a language with a coherent design.

JavaScript has a coherent design specially if you're using ES6+ in strict mode with a linter. Modern JavaScript is a great language, and comparable to Python.

Re:Discover Flask by devishard on Sunday February 21, 2016 @11:15AM (#11145030)
I'm using ES6 in strict mode with a linter and Babelify to transpile for browser compatibility and I stand by what I said. I've been writing JavaScript since there was JavaScript to write, and the situation has improved drastically, but JavaScript is still far from being a coherently designed language.
Re:Discover Flask by tedmiston on Sunday February 21, 2016 @08:59AM (#11144509)
Most people will tell you they're using 2.7 in production.
Re:Discover Flask by dorfsmay on Sunday February 21, 2016 @09:57AM (#11144711)
Because of legacy, but these days there is no reason not to use python 3 on new projects. Note that Python 2.x will no longer be supported in 2020.
Re:Discover Flask by drdaeman on Sunday February 21, 2016 @12:21PM (#11145372)
New projects depends on that legacy - in form of existing libraries. So, one may find themselves writing somewhat more code than they had expected, either as a new libraries or patching the existing ones to work with Python 3.

Well, not that doing so is a bad thing - it's the contrary, esp. if the patch goes to the upstream - but still this may be frustrating to some.

(Most common libraries are actually work pretty well with Python 3. But there are still a lot of stuff PyPI that's Python 2-only at the moment.)

Re:Discover Flask by dorfsmay on Sunday February 21, 2016 @03:48PM (#11146431)
This used to be an issue, but, in the past 2 years pretty much all the most used libraries have added a python 3 version.
Re:Discover Flask by tedmiston on Monday February 22, 2016 @08:35AM (#11150653)
I wish I could say this about our dependencies but it's not quite true yet.

I do run our requirements.txt through https://caniusepython3.com every few months though.

Re:Discover Flask by tedmiston on Monday February 22, 2016 @08:33AM (#11150641)
There are a good amount of dependencies that haven't been ported to 3 yet. Using one of these directly, or as a secondary dependency, is the reason running 3 in prod is impractical for many of us.

http://py3readiness.org/

Re:Discover Flask by zardeh on Monday February 22, 2016 @02:21PM (#11153489)
So, ndg-httpsclient, mrjob, numpy, scrapy, monotonic and possibly others do have python3 compatibility.

Then there's a bunch of deployment tools like ansible, fabric, and marionette which don't really need to be python3 compatible for use.

Then there's tools like MySQL-python, python-gflags, python-cjson, INITools, filechunkio, which have python3 compatible alternatives, often in the standard library.

That brings the total up to 331

That leaves basically 3 categories of things left: mozilla tools, database connectors (many of which probably have python3 bindings though I haven't looked), and single sign on tools. Those account for 12 of the remaining 29 libraries.

That's pretty ready.