Picodata: Distributed Rust Database Supporting PostgreSQL, Redis, and Cassandra Protocols

·1 views

Picodata is a distributed, PostgreSQL-compatible database built in Rust that supports multiple wire protocols through a plugin architecture. It natively speaks the PostgreSQL protocol, while the Radix plugin adds Redis compatibility and the Sirin plugin enables Cassandra Query Language support. The system uses Raft consensus for schema management and cluster topology, and employs a shard-per-core model with active-active multi-datacenter replication. Descending from Tarantool, Picodata is designed for horizontal scalability and claims production performance of over 10,000 transactions per second per core. It is self-hosted via Linux packages or Docker, with source code available at git.picodata.io and documentation at docs.picodata.io.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Workers Across Industries Earn Just $3/Hr for On-Call Time That Limits Their Freedom

Standby pay rates of $3 to $4 per hour are common across nurses, EMTs, utility workers, and tech employees, despite requiring sobriety, proximity to work, and rapid response times. U.S. labor law under 29 CFR §785.17 distinguishes between 'engaged to wait' (compensable) and 'waiting to be engaged' (not required to be paid), a framework shaped by the 1944 Supreme Court case Skidmore v. Swift & Co. A 1999 Seventh Circuit ruling found that Wisconsin EMTs required to stay sober and respond within seven minutes were still not entitled to full pay for on-call hours. Recent contract data shows the pattern persists: IBEW Local 1245 raised standby pay to $3/hr in January 2024, and a New Hampshire public works contract pays under $1/hr for off-shift standby. Critics argue that while workers may not be actively performing tasks, the employer's ability to demand sobriety and a fast response represents a significant restriction on personal time that current compensation rates fail to reflect.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Runway's AI renders websites as live video, no code required

Runway has previewed an 'Interface World Model' that generates entire websites and app interfaces in real time as video frames, with no traditional source code running underneath. A language model interprets user actions such as clicks and drags, while a video model draws each resulting frame on the fly. In blind evaluations, human testers preferred these AI-rendered interfaces over those built by a leading coding model in most head-to-head comparisons. The system still has notable limitations, including garbled text and drift during long sessions, but represents a tangible step toward on-demand, code-free web interfaces. The development coincides with video-generation models becoming fast and affordable enough to make the concept practically viable for the first time.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Android Developers Can Meet Google Play's 12-Tester Requirement Without Resets

Since November 2023, Google requires Android app developers to complete a closed test with at least 12 active testers over 14 continuous days before an app can go live on the Play Store. The process is harder than it appears, as Google monitors genuine engagement rather than just app installs, meaning a lack of visible activity or tester drop-offs can still result in rejection. Developers are advised to recruit 14–15 testers to account for drop-offs, ship at least one update during the testing window, and track daily active usage rather than total installs. One effective strategy is reciprocal testing, where developers exchange testing duties with peers who face the same requirement, creating mutual incentive to stay engaged for the full two weeks. Communities focused on this kind of peer exchange, such as the Google Play Console Help forum, can help developers find committed testers beyond their personal networks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build an Enterprise E-Commerce Platform for Agricultural Fertilizer Sales

A technical guide published on DEV Community outlines the architectural challenges of building a specialized e-commerce platform for agricultural fertilizer sales, as opposed to standard retail setups. The guide explains that conventional tools like Shopify or WooCommerce fall short when handling complex requirements such as bulk weight variants, NPK chemical ratio filtering, and strict chemical safety regulations. It proposes a PostgreSQL database schema using Prisma ORM that separates core chemical specifications from physical packaging variants, enabling cost-per-kilogram comparisons across different container sizes. The guide also details a custom Node.js freight calculation engine to handle LTL and FTL shipping scenarios, since standard parcel APIs are inadequate for multi-ton fertilizer orders. Overall, the article positions agricultural fertilizer e-commerce as a distinct AgriTech engineering problem requiring purpose-built, scalable solutions.

0 comments Read more at DEV Community