Urgent.News

What's breaking now, across thousands of outlets.

Tech

Microservices and a “zoo” of databases: why small teams don’t always need this

В конце 2000-х главным вопросом проектирования был «SQL или NoSQL». Прошло полтора десятилетия, и оказалось, что победителя нет — но не потому, что все договорились. А потому, что сам вопрос перестал иметь смысл. Исследование Datadog, построенное на анализе более 2,5 миллиона сервисов в продакшене, показывает, как микросервисная архитектура переопределила то, как компании используют базы данных —…

Translated from Russian Read in Russian

A recent study by Datadog analyzed over 2.5 million production services and found that most organizations use multiple database technologies simultaneously. On average, companies use three or more databases, with a quarter of clients using five or more. Almost half of companies use both SQL and NoSQL databases. The study also found that many teams are using GraphQL to integrate data from multiple sources, but this can add complexity and cost.

Small companies may struggle with using multiple databases, as it can lead to increased maintenance and integration costs.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I built my friend a voice-based recipe note-taking app

What I built Built a browser-based app which takes audio input from the microphone and transcribes it into recipe notes/memo. Building for a Friend Made it for my friend, Arnesh.

  • Browser-based app records audio and converts it into recipe notes.
  • Uses microphone APIs and Transformers.js with open Whisper-tiny model.
  • Structured code into modules for audio, transcription, parsing, storage, rendering.

Benchmark Android User Journeys with Macrobenchmark

Unit tests can prove that a ViewModel returns the right state, but they cannot measure the latency and frame behavior a user experiences across a sequence of screens and a real application process.

  • Macrobenchmark simulates end-to-end user journeys from app launch to refreshed state.
  • Measure frame timings and milestones to detect performance issues missed by isolated tests.
  • Configure app for profile mode, build dedicated benchmark variant with .benchmark suffix.

Stop Hand-Rolling an Exclusive Accordion. `<details name>` Does It

You're building an FAQ page. Ten questions, each collapsed by default, and — this part's in every design spec — only one answer open at a time. Click a second question, the first one closes.

  • Native details and summary tags provide built-in accordion functionality.
  • name attribute enforces mutual exclusivity across multiple details elements.
  • Grouping related elements with the same name simplifies accordion implementation.

More from Sunday 4 October →