jordic
No user record in our sample, but jordic has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
No user record in our sample, but jordic has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
Google is no longer interested in returning good search results, their priority are ads. (Good results are on ads)
I use acme as a personal wiki where I can store useful playbooks (executables from there). From sqls to kubectl commands. Just a big wiki with the unix at the mouse.
Perhaps we need an expert on design history. Typefaces are a complex thing with lot's of design decisions behind.
At my past job we have something like for newsletters and 250k/tasks per day was fine. The only design problem we have had is that if you keep past tasks on the queue table, when it grows it traches a lot cache due to…
This is one of the firsts principes of critical thinking: it's not only about understanding something, it's about being ready to challange it.
We do something like this, also we took some inspiration from hashura. Asyncpg it's so fast an ergonomic.
Think on it like a middleware that wraps a transaction. It's fine, till you start consuming other Io based services (elastic/solar/...) And you find that this blocks one connection per request..
Synthetic event system + render decoupling. Preact uses the event system of the platform (browser) and only renders to it (there's no react native support). Anyway we are using it at prod and allowed us to reduce our…
Also it'so easy to start making new components dependent on the store, and ending with reusability.
I'm more used to preact, it's small it's fast, and it's near the DOM. Last, with preact/htm it doesn't need any tooling :)
Cool! Thinking so many times in something like this, but sql it's not easy composable...
Our front service it's a nextjs/nodejs project. But I still prefer python :) and our API's are python based, typed async python.. but python..
Someone should take care of it, but doesn't seem like a trivial problem.. btw, I also will be so happy to be able to reuse part of twisted core on asyncio services :)
I must say that python3.8 does a better job detecting not awaited awaitables. Anyway,asyncio it's not new to python, the stdlib still has asyncore in it. There are still awesome web servers around (threaded) but using…
Mostly agree around reusing existing libs, and being and split point on the community, but I also can't understand why so many detractors. It's a tool and does it's job quit well. Anyway, in my test I prefer explicit…
Nice one, but.. I prefer sqls that you can debug without rendering.. (it's not so manageable when you deal with ctes, window functions, joins different schemas, custom functions...
On one project we use Databases, with a custom opensourced "adapter" for sqlalchemy models: https://github.com/vinissimus/asyncom Our cms, is based on Guillotina (https://github.com/plone/guillotina) that uses a…
For example: https://discuss.tryton.org/t/wsgi-server-choice/2766 https://mail.zope.org/pipermail/zodb-dev/2010-December/01389... https://docs.rhodecode.com/RhodeCode-Enterprise/admin/tuning...…
We are also using starlette and works quite well.. in combination with asyncpg..
The thing is that you can serve a lot of requests on a single core.. (and at least us we pay per core)
In our use case, from 12 cores to 2 :) (mostly for ha)
With async Django views we can use Django with asyncpg... o_o but middlewares are still synch...
Python context managers are a great way to prevent this type of issues. Anyway feels like a bit strange to not use the current connection (from between the transaction) to query things. Perhaps the problem is between…
I would also add to the article, that when you try to alter a busy table add it a timeout (otherwise you will lock the world). SET statement_timeout = 50; Alter .... ;
Agree, at least for me, I don't discovered the sqlsuperpowers till I got inside it... I would love to see some of this pretty clever orm migrations applied on a busy potgresql server.. with a bit of concurrency... :)