Floci is a free, open-source local AWS emulator for development, testing, and CI.
It gives you AWS-shaped services on your machine without requiring a cloud account, an auth token, or paid feature gates. Point your AWS SDK, CLI, Terraform, CDK, OpenTofu, or test suite at http://localhost:4566 and keep your existing workflows.
https://github.com/floci-io/floci
It gives you AWS-shaped services on your machine without requiring a cloud account, an auth token, or paid feature gates. Point your AWS SDK, CLI, Terraform, CDK, OpenTofu, or test suite at http://localhost:4566 and keep your existing workflows.
https://github.com/floci-io/floci
GitHub
GitHub - floci-io/floci: Light, fluffy, and always free - The AWS Local Emulator alternative
Light, fluffy, and always free - The AWS Local Emulator alternative - floci-io/floci
Two ways to keep a user logged in.
And they fail in very different ways.
After login, you need to remember who the user is.
There's typically two common approaches:
• Session token: a random ID. The server stores the session and looks it up each request.
• JWT: a signed token holding the user's info. The server just verifies the signature, no lookup.
JWTs scale well because there's no server-side storage. That's also their weakness.
This is because you can't easily revoke a JWT before it expires. A logged-out user's token still works until it times out. Sessions you can kill instantly.
The solution, which is still not ideal, for JWTs is short expiration and token blacklisting.
Stateless is convenient, but "can't revoke" is a real security tradeoff.
Source
And they fail in very different ways.
After login, you need to remember who the user is.
There's typically two common approaches:
• Session token: a random ID. The server stores the session and looks it up each request.
• JWT: a signed token holding the user's info. The server just verifies the signature, no lookup.
JWTs scale well because there's no server-side storage. That's also their weakness.
This is because you can't easily revoke a JWT before it expires. A logged-out user's token still works until it times out. Sessions you can kill instantly.
The solution, which is still not ideal, for JWTs is short expiration and token blacklisting.
Stateless is convenient, but "can't revoke" is a real security tradeoff.
Source
LinkedIn
Two ways to keep a user logged in.
And they fail in very different ways.
After login, you need to remember who the user is. …
And they fail in very different ways.
After login, you need to remember who the user is. …
Two ways to keep a user logged in.
And they fail in very different ways.
After login, you need to remember who the user is.
There's typically two common approaches:
• Session token: a random ID. The server stores the session and looks it up each request.…
And they fail in very different ways.
After login, you need to remember who the user is.
There's typically two common approaches:
• Session token: a random ID. The server stores the session and looks it up each request.…
gevent is a coroutine-based Python networking library that uses greenlet to provide a high-level synchronous API on top of the libev or libuv event loop.
https://www.gevent.org/api/gevent.greenlet.html
https://www.gevent.org/api/gevent.greenlet.html
The #1 Open-Source CRM
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
https://github.com/twentyhq/twenty
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
https://github.com/twentyhq/twenty
GitHub
GitHub - twentyhq/twenty: The open alternative to Salesforce, designed for AI.
The open alternative to Salesforce, designed for AI. - twentyhq/twenty
❤3
Django 6.1's tip Fetch Modes: #python #django #fetch_modes
Django 6.1 fixes N+1 without you rewriting your queries you never touch the for loop. You just tell the queryset how permissive it should be about surprise trips to the database — and FETCH_PEERS quietly turns "101 queries" into "2 queries" with zero extra code at the call site.
Docs
Django 6.1 fixes N+1 without you rewriting your queries you never touch the for loop. You just tell the queryset how permissive it should be about surprise trips to the database — and FETCH_PEERS quietly turns "101 queries" into "2 queries" with zero extra code at the call site.
Docs
❤3
Qdrant (read: quadrant) is a vector similarity search engine and vector database. It provides a production-ready service with a convenient API to store, search, and manage points—vectors with an additional payload. Qdrant is tailored for extended filtering support, making it useful for all sorts of neural-network or semantic-based matching, faceted search, and other applications.
https://github.com/qdrant/qdrant
https://github.com/qdrant/qdrant
GitHub
GitHub - qdrant/qdrant: Qdrant - High-performance, massive-scale Vector Database and Vector Search Engine for the next generation…
Qdrant - High-performance, massive-scale Vector Database and Vector Search Engine for the next generation of AI. Also available in the cloud https://cloud.qdrant.io/ - qdrant/qdrant
❤1
FastrAPI is a high-performance web framework that supercharges your Python APIs with the power of Rust. Built on Axum and PyO3, it delivers unmatched speed, type safety, and developer-friendly Python syntax. Create robust, async-ready APIs with minimal overhead and maximum throughput. FastrAPI is your drop-in replacement for FastAPI, offering familiar syntax with up to 6x faster performance.
https://github.com/ppmpreetham/fastrapi
https://github.com/ppmpreetham/fastrapi
GitHub
GitHub - ppmpreetham/fastrapi: ⚡FastAPI alternative for Python, but actually (~6x) FASTER. Written in Rust.
⚡FastAPI alternative for Python, but actually (~6x) FASTER. Written in Rust. - ppmpreetham/fastrapi
❤2👍1