Explore >> Select a destination
|
You are here 
|
www.kuniga.me | ||
| | | | |
kristoff.it
|
|
| | | | | ||
| | | | |
rupertmckay.com
|
|
| | | | | async/await vs promises. | |
| | | | |
masnun.rocks
|
|
| | | | | Whovian, *nixer, business graduate, passionate software craftsman | |
| | | | |
truemped.github.io
|
|
| | | My usual web application stack for the past years was based on a nginx as reverse proxy in front of a number of Python processes. Static resources were served by nginx. Each Python process was stateless, state was stored in some kind of database. If the processes needed some shared ephemeral state like counters a local redis instance solved that. A battle tested common ground for Python based web applications. | ||
