Filter
Exclude
Time range
-
Near
SeRvErLeS YaPaRıM
2
250
A banger post by our CTO @khustup on how he made Postgres Serverles and spin up under second. We built a serverless, PostgreSQL-compatible database. Not a modified PostgreSQL deployment. PostgreSQL provides the interface. DuckDB provides the query execution. Deeplake provides the storage engine. The architecture makes a different set of tradeoffs than traditional PostgreSQL. We think those tradeoffs are right for agent workloads: bursty, ephemeral, storage-heavy, and analytical. Link: deeplake.ai/blog/serverless-…
9
530
📢 𝐉𝐔𝐒𝐓 𝐈𝐍: Elastic Boosts AWS Serverless Performance with Up to 50% Throughput Gains - $ESTC $AMZN 👉 𝐊𝐞𝐲 𝐇𝐢𝐠𝐡𝐥𝐢𝐠𝐡𝐭𝐬: ➤ Elastic upgrades 𝐄𝐥𝐚𝐬𝐭𝐢𝐜 𝐂𝐥𝐨𝐮𝐝 𝐒𝐞𝐫𝐯𝐞𝐫𝐥𝐞𝐬 on 𝐀𝐖𝐒. ➤ New virtual compute units use 𝐀𝐖𝐒 𝐆𝐫𝐚𝐯𝐢𝐭𝐨𝐧 instances. ➤ Indexing throughput improves by up to 𝟓𝟎%. ➤ Search latency reduced by up to 𝟑𝟕%. ➤ Performance gains delivered at 𝐧𝐨 𝐞𝐱𝐭𝐫𝐚 𝐜𝐨𝐬𝐭 to users. ➤ Serverless platform supports 𝐢𝐧𝐝𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐭 𝐬𝐜𝐚𝐥𝐢𝐧𝐠 of workloads. ➤ Service is 𝐟𝐮𝐥𝐥𝐲 𝐦𝐚𝐧𝐚𝐠𝐞𝐝 and auto-scaled. ➤ Architecture optimized for 𝐬𝐞𝐚𝐫𝐜𝐡, 𝐨𝐛𝐬𝐞𝐫𝐯𝐚𝐛𝐢𝐥𝐢𝐭𝐲, 𝐚𝐧𝐝 𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲. ➤ Enables 𝐧𝐞𝐚𝐫-𝐢𝐧𝐬𝐭𝐚𝐧𝐭 query response times. ➤ Supports 𝐯𝐞𝐜𝐭𝐨𝐫 𝐬𝐞𝐚𝐫𝐜𝐡 and AI-driven RAG workloads. ➤ Faster indexing improves 𝐧𝐞𝐚𝐫 𝐫𝐞𝐚𝐥-𝐭𝐢𝐦𝐞 𝐝𝐚𝐭𝐚 𝐯𝐢𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲. ➤ Platform efficiently handles 𝐭𝐫𝐚𝐟𝐟𝐢𝐜 𝐬𝐩𝐢𝐤𝐞𝐬 and demand shifts. ➤ Elastic trades on NYSE under ticker 𝐄𝐒𝐓𝐂.
8
1,812
20 Dec 2025
Memory、DynamoDBにしろ、Aurora Serverlesにしろ、メリデメがあるけど、AgentCore Memoryの裏側何使っているか気になる。 #AIBuildersDay
1
2
854
Replying to @CR1337
I like this quote. Perfect for todays threat of chat control in EU. We have decided to keep our freedom and privacy. We communicate without AI reading our messages - with CPUNK p2p DNA-Messenger. Serverles, quantum proof technology. $cpunk #ChatControl #quantumproof
5
1
117
16 Nov 2025
Fechando a triologia - O que é bom você saber/estudar pra se vender bem como Senior: - Fazer Crud - Git - Docker - Algum terminal - 160KG no Squat - Conhecimento em alguma Cloud (sugiro ao menos duas~tres - ex GCP/AWS/Cloudflare) - SIM saber usar varias Clouds vai deixar tua vida muito mais facil - Conceitos comuns dessas clouds tb - serverles, stateless, vpc etc - CI/CD nessas clouds - Teste unitario, E2E, Carga, Stress, Piramide, TESTES, T E S T E S - ParadigmaS de programação (saber algo além de OOP é bom) - Frontend Vanila Algum frame chato desses da moda - Filas, PUB/SUB - Algum DB SQL com profundidade - Algum DB NoSQL com profundidade - TécnicaS de Caching - No plural - Threading, Concorrencia, Programação assíncrona, conhecimento de hardware - Conhecimento um pouco mais baixo nivel das suas tools/lang principal - Técnicas de resiliência e anti fragil - Otimizações básicas de BigO - Otimizações de código/algoritmo - Design Patterns/Estrutura de dados - ProtocoloS de comunicação - no plural tb (protocolos de filas/pub-sub, http, grpc, websocket, ftp etc) - Arquitetura de software - Arquitetura de cloud/soluções - Eventos, Event Driven - Streams - Observabilidade - Experiência com padrões de mercado pra soluções comuns - Ex: Locks em casos de race condition etc - System Design - SOLID, CUPID essas siglas chatas que vc tem q saber falar na entrevista - Algum conceito decorado de DDD pra impressionar na entrevista tb - Algum nome de livro do Uncle Bob só pra falar que leu na entrevista - Tratamento de erro e técnicas de error handling num geral - Modelagem de banco (normalização e denormalização) - Saber explicar coisas técnicas pra pessoas não técnicas - Comunicar como um herói - Documentar como um herói - Passar conhecimento como um herói - Revisar como um herói - Se comprometer com as entregas - 100KG no Supino cansei kkk
16 Nov 2025
Pleno deveria saber os conhecimentos do post de Junior, ter algum tempo de XP e: - Algum banco noSQL (Dynamo, MongoDB etc) - Basico de alguma Big Cloud - AWS/Azure/GCP - Caching - Async Jobs (ex: BullMQ - SQS Lambda) - Design Patterns/Estrutura de dados básicas - BigO - Algum conhecimento sobre modelos de arquitetura (Hexagonal - Clean - Layered etc) - Básico sobre CI/CD - Básico sobre otimização de queries - index de DB tb - Testes com profundidade - Otimizações de código - Básico de observabilidade (ao menos logs e alguma tool ex: new relic/sentry) - Básico sobre Horizontal e Vertical Scaling
45
43
988
100,341
Replying to @brankopetric00
My platform runs on all serverles appsync, lambdas and dynamodb. The client drives the backend and not the other way around. No cycles are spent on AWS unless the client clicks on something. The bill is negligible. Different way of architecting and thinking for maximum cost efficiency
6
1,237
Our v2 is architecturally closer to something like Kafka than Cloudflare now, since we're built at our core to work with wherever your code is already running. We support: - Serverful: your servers autoscale & connect to Rivet, we schedule actors on them - Serverless: you give us a serverles sendpoint, we run actors on your serverless - Orchestrated (coming soon): you give us k8s/AWS/GCP API access, we have a fine-tuned autoscaler to manually boot containers Earlier this year, we put a lot of work in to building an open-source self-hosted serverless platform (custom V8 runtime, container platform, etc). There's a lot of demand there up for grabs, but we had to decide between focusing on Rivet Actors or double down on just serverless. We chose Rivet Actors. This deserves a blog post of its own at some point, we learned a bunch of fun things in the process. Some other options to consider for self-hosted serverless-ish: - @porterdotrun - @ryvnai - @encoredotdev - @coolifyio - @zeitwork - @Railway and @deno_land Deploy can do custom deployments for enterprise afaik Though Deno is the only option that provides true isolates – unless containerizing workerd. Deno at one point had a Helm chart on GitHub to self-host Deno Deploy – I think it might've been pulled.
1
1
4
1,087
27 Sep 2025
Replying to @TurvSec
I always want to create something like this but for all providers that's give free tiers on serverles calls , firebase functions, cloudflare workers , deno deploy , in single project you cloud probably get a million request a day with all providers
1
2
955
20 Jul 2025
Did you know @theblessnetwork used to be called Blockless? 👀 Yup. It started as a project focused on serverles infrastructure. But as it grew, the mission evolved, way beyond just removing servers. It became something bigger: A decentralized compute network where anyone can contribute idle device power to support cloud-scale tasks. Think of it as a shared computer powered by everyday people, with blockchain-based rewards to keep things fair and open. The rebrand to Bless Network (announced Nov 2024) wasn’t just a name change. It was a level-up in vision, purpose, and clarity. From blockless to borderless. This isn’t just infrastructure, it’s a revolution in motion.
94
2
84
675
Think about where your misery lies in your project It starts with choosing a framework and it ends with dependency hell full of leaks and security holes and high hosting costs with scaling issues so you have to land into the serverles landscape Just think about it
2
149
Replying to @midudev
Técnicamente mucha gente desconoce que Cloudflare no es solo un proxy, también tiene un hosting serverles potente y barato. Tengo gran parte de mi producción en Cloudflare. No puedo escapar de ninguna manera del bloqueo. Durante el periodo de bloqueo mi tráfico cae un 99%.
1
3
1,251
Not bad 😅 love the serverles computer in the background
2
2
570
Day52 to 54 of #100DaysOfCode - Finished Backend (serverles hono) of blogging-website from #cohort2 by @kirat_tw - avoided video, gpt. Used Google, stack overflow and blogs for debugging. - Deployed package to npm. - Build landing page for SaaS. #cloudflare #backend #medium
5
155
Dify × ECS × TiDB Serverles試すか。 #TiUG
5
476
TiDB Serverles - Vector Searchの話! 昨日Public Betaになったやつ! #TiUG
2
309
Replying to @the_sambu
Talk of serverles computing. The control plane is financebill2024. They can withdraw the bill to re-strategize or destroy their political careers.
2
788
Me, a dumb idiot: I would like to rent a VM My uncool traditional hosting provider: it will be $3/mo please You, a genius dev: hahaha, cute but my app is serverles Your hip hosting provider: we charge $.00003 per API call so this month you owe us eleventy billion dollars
1
2
7
113