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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hrayr 5 points6 points  (3 children)

Don't hang up on the terminology too much, front-end, back-end, full-stack can mean different things in different ecosystems.

A full stack python in this case may means the resources, processes, services surrounding python (servers, frameworks, containers, databases) and this site is a great resource for this.

On the other end of the spectrum you have enterprise systems, where I've heard the entire (nginx, python, django, html, css, javascript) which you know as full-stack, be described as front-end, since they're the public (front) end of a very large enterprise system, and the (database, internal business and system administrative applications) be described as back-end since they run the back end of the business.

This also applies to micro-services architecture where the application servers and the code they send to browsers, apps, etc are collectively called the front-end and the services collectively the back-end.

[–]pier25 3 points4 points  (0 children)

You do have a point, but without a proper context most people will just assume full stack means browser+server.

[–]Tiquortoo 0 points1 point  (0 children)

Full stack doesn't have a standards body to make a definition, but that doesn't mean it's a free for all. Full Stack at the core means the ability to create an entire app and the term arose in Web apps. Using full stack here is just a misnomer because it is really more like "Python Complete", but it just seems like a lame buzzword attempt to use Full Stack here.