[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] #  @nikitabase Nikita | Scaling Postgres Nikita | Scaling Postgres posts on X about protocol, all the the most. They currently have XXXXXX followers and XXX posts still getting attention that total XXXXXX engagements in the last XX hours. ### Engagements: XXXXXX [#](/creator/twitter::158914930/interactions)  - X Week XXXXXX -XX% - X Month XXXXXXX +3,021% - X Months XXXXXXX -XX% - X Year XXXXXXX -XX% ### Mentions: X [#](/creator/twitter::158914930/posts_active)  - X Week X +25% - X Month X +17% - X Months XX -XX% - X Year XX +34% ### Followers: XXXXXX [#](/creator/twitter::158914930/followers)  - X Week XXXXXX +0.10% - X Month XXXXXX +1.30% - X Months XXXXXX +13% - X Year XXXXXX +45% ### CreatorRank: XXXXXXX [#](/creator/twitter::158914930/influencer_rank)  ### Social Influence [#](/creator/twitter::158914930/influence) --- **Social category influence** [technology brands](/list/technology-brands) **Social topic influence** [protocol](/topic/protocol), [all the](/topic/all-the) ### Top Social Posts [#](/creator/twitter::158914930/posts) --- Top posts by engagements in the last XX hours "SQL over http should be standardized. It makes too much sense. So great step by @PlanetScale. Also do implement HTTP and not just web sockets - its much lower latency as pg protocol is quite chatty for establishing a connection" [X Link](https://x.com/nikitabase/status/1976509385422799179) [@nikitabase](/creator/x/nikitabase) 2025-10-10T04:45Z 11.2K followers, 79K engagements "We managed XXXXX% of database operations successfully on US-East-1 throughout the outage. Mostly because we depend on a relatively short list of AWS services. We buy big metal instances from AWS relatively infrequently and then handle all the tenant provisioning ourselves" [X Link](https://x.com/nikitabase/status/1980399551883407787) [@nikitabase](/creator/x/nikitabase) 2025-10-20T22:23Z 11.2K followers, 51.4K engagements "Kk. The point Im making is a simple one. If you dont have elasticity you have to provision for peak. As a provider you dont want of course provision for peak yourself and just eat the cost. But this requires architectural changes: separation of storage and compute multi tenant storage and packing microVMs. So compute is also multi-tenant just less granular. If you do that you dont need to keep reserve capacity but to your point we do need to pack as dense as possible and thats tricky. So yes there IS spare capacity but much less than 40%" [X Link](https://x.com/nikitabase/status/1980438217703956957) [@nikitabase](/creator/x/nikitabase) 2025-10-21T00:57Z 11.2K followers, XXX engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@nikitabase Nikita | Scaling Postgres
Nikita | Scaling Postgres posts on X about protocol, all the the most. They currently have XXXXXX followers and XXX posts still getting attention that total XXXXXX engagements in the last XX hours.
Engagements: XXXXXX #
- X Week XXXXXX -XX%
- X Month XXXXXXX +3,021%
- X Months XXXXXXX -XX%
- X Year XXXXXXX -XX%
Mentions: X #
- X Week X +25%
- X Month X +17%
- X Months XX -XX%
- X Year XX +34%
Followers: XXXXXX #
- X Week XXXXXX +0.10%
- X Month XXXXXX +1.30%
- X Months XXXXXX +13%
- X Year XXXXXX +45%
CreatorRank: XXXXXXX #
Social Influence #
Social category influence technology brands
Social topic influence protocol, all the
Top Social Posts #
Top posts by engagements in the last XX hours
"SQL over http should be standardized. It makes too much sense. So great step by @PlanetScale. Also do implement HTTP and not just web sockets - its much lower latency as pg protocol is quite chatty for establishing a connection"
X Link @nikitabase 2025-10-10T04:45Z 11.2K followers, 79K engagements
"We managed XXXXX% of database operations successfully on US-East-1 throughout the outage. Mostly because we depend on a relatively short list of AWS services. We buy big metal instances from AWS relatively infrequently and then handle all the tenant provisioning ourselves"
X Link @nikitabase 2025-10-20T22:23Z 11.2K followers, 51.4K engagements
"Kk. The point Im making is a simple one. If you dont have elasticity you have to provision for peak. As a provider you dont want of course provision for peak yourself and just eat the cost. But this requires architectural changes: separation of storage and compute multi tenant storage and packing microVMs. So compute is also multi-tenant just less granular. If you do that you dont need to keep reserve capacity but to your point we do need to pack as dense as possible and thats tricky. So yes there IS spare capacity but much less than 40%"
X Link @nikitabase 2025-10-21T00:57Z 11.2K followers, XXX engagements