501–510 of 539 posts
Earlier quoted context omitted.
How about pg on Unix socket?
Running 100,000 `SELECT 1` queries: PostgreSQL (localhost): 2.84 seconds PostgreSQL (Unix socket): 1.93 seconds SQLite (in-memory): 0.07 seconds SQLite (tempfile): 0.06 seconds ( https://gist.github.com/leifkb/b940b8cdd8e0432cc58670bbc0c33... )
This is similar to what I do. Linode, Debian, Go, HTMX, SQLite (with modernc.org/SQLite so I have no CGO dependency) and Caddy. If I have apps that need a lot of storage, I just add an S3 bucket.
- backups - upgrades to the os packages (and downtime from reboots) - updates to container images (if you run any) - monitoring and alerting (logs, http 500 increase, http 200 drop, etc)
Asking because I’m looking for pointers on how to solve this myself when deploying to a VPS rather than AWS alphabet soup or a PaaS
Earlier quoted context omitted.
not at all meaningless. unless you have money to invest, at the beginning you don't have an income. i could not afford to spend $300 a month to host a new product that doesn't make any money yet. i can afford the $20 however, but then once the product does make money, why should i change it if it works?
As a student you might be living in a 6sqm dorm with shared bathroom and a kitchen for 400 USD a month. You get a job paying you 200k afterwards. Why would you change where you live if it works?
moving from self hosting to a hosted service gives me other advantages. whether those matter depends on the specific situation. the reality is that in many cases the hosting costs rise faster than the costs for self hosting would, and big companies save lot of money by moving back.
switching from $20 a month to $300 a month is only worth it if i save at least a day of work per month. but that's often not the case. and the more you scale up the less work per revenue/profit you have.
the one big advantage of paid services is that they lets you scale up faster. if that is what you need, then sure. OP does not scale fast.
Earlier quoted context omitted.
I’ve seen multimillion dollar “enterprise” projects get no where close to that. Of course, they all run on scalable, cloud native infrastructure costing at least a few grand a month.
> a few grand a month. A negligible cost for a successful tech business that also works when your requirements exceed the capabilities of a single VPS.
Earlier quoted context omitted.
Yes. It strikes me as odd how many people will put forward Python with the argument of "simplicity". It is not. Simple. It may be "easy" but easy != simple (simple is hard, I tend to say). I'm currently involved in a project that was initially layed out as microservices in rust and some go, to slowly replace a monolyth Django monstrosity of 12+ years tech debt. But the new hires are pushing back and re-introducing py…
I am not following the difficulties you have mentioned. Setting up a local dev environment in Python is trivial with UV. The only major downside of Python is its got a bit poor module system and nothing as seamless as Cargo. Beyond that the code is a million times easier to understand for a web app.
"trivial" falls in the "easy" category. So it may not be hard to do. But what UV makes "easy" is managing something very complex under the hood.
Better example:
FROM python:3.9-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
CMD ["python", "app.py"]
While "easy" it is nowhere near simple. Aside from the entire complexity of the stack of docker, that `python:3.9-slim` it itself is very complex. It installs over 20 "dev" packages (from bluetooth via tk to xz), it downloads source files, builds a python runtime, (patches that?), installs pip, setuptools, does some (to python people probably familiar?) "wheel" stuff, etc¹. Point being: what you end up with, while easy to get, is very complex.
uv manages a runtime, some virtual environment to hot-swap that with other runtimes, it hooks into a package manager, manages additional tools (linter, typechecker, lsp, etc) and so on. What lies under that is very complex.
¹ I am well aware that node, ruby, php are quite similar.
Earlier quoted context omitted.
I've seen A LOT of public sector projects starting out with loads of Azure services and >$3000 montly bills for applications that could've easily run on a single VM.
This a structural problem not an awareness one. Is not like they don’t know they can run it on a 5$ VPS, the problem is that there are no incentives to do so. You’d be surprised to know how much of engineering is there to address organisational challenges rather than technical ones (ie: micro-services)
Earlier quoted context omitted.
Are you guys interested in some ideas? It seems to me that I am getting much more good ideas than I can carry on.
Sure fire away maybe this time something clicks for someone :)
https://github.com/mikko-ahonen/arch-ascent/tree/main/doc/de...
Modern tech stacks always remind me of this cartoon: https://www.toontales.net/short/lumber-jerks/ Acme Toothpicks