For my own personal projects, i keep using PostgeSQL (not really sure why, but it's just seems to work for me). On the work side, MSSQL is the go to one. Here in Denmark, im not sure how many applications runs on other database platforms. I have never heard any coworker or other professional usie something else, but then again Denmark is a big Microsoft fanboy :D
Hi. For internal company systems I use Microsoft SQL Server, for the majority of customers in the industry I also use MS SQL Server + PostgreSQL. But for Linux and low-cost solutions mainly PostgreSQL.
I've been trying out Surrealdb and I like it a lot. I can use it as an embedded db or as a server/client model (makes testing pretty easy). The query language is nice and it also has built-in vector functions so I'm using it as a vector store for a Retrieval-Augmented Generation (RAG) pipeline.
I also recently learned about recfiles but haven't had a chance to use them yet.
Honestly I haven't really experimented with anything else, I could easily switch to MariaDB (which is more or less a drip in replacement) or Postgres (since most of my projects use an ORM that can use MySQL or Postgres interchangeably). I know that MySQL works for me, after 10 years of using it I know how InnoDB works and how to optimize for it, I know which tools I need with MySQL (mostly tools from Percona)... So I don't really feel the need to start over with another DB.
I'll definitely use something like Mongo if I ever need to store non relational data, or Cassandra if I need to store data over many decentralized servers, and I indirectly use Elastic search for time series when I use graylog to store my logs. But it turns out most of the applications I build need a centralize datasource (with a few Replicas for availability) to store relational data, so MySQL it is !
I NextGen AI creator! To create a new AI evolutionary code, you can follow these steps:
1. Define the problem: Clearly outline the problem you want to solve using AI evolutionary algorithms.
For the back end, I prefer MySQL or PostgreSQL in GCP/AWS. For analytics, I use BigQuery daily.
Because of my specialty (data engineering), I must use all the databases mentioned and even more (depending on the project). Imagine migrating Access to SQL; it's very funny.
Hey, I'm head of product over at Xata. A large portion of our team came from Elastic and a common architecture we saw at scale was PostgreSQL + Elasticsearch as a way to get all the OLTP benefits of a relational database with full text search and metrics / aggregations for other application / analytical needs. This was seen across industries ranging from the ecommerce to commercial applications to the federal government. With the boost in AI use cases, I can only imagine this has become even more common of an architecture.
We've decided to productize this architecture as a service. If you're interested in learning more about the implementation details for inspiration, here's the architecture behind our platform: xata.io/docs/concepts/serverless-d...
French web developer mainly but touches everything. Volunteer admin mod here at DEV. I learn AI and Astro at this moment and databases. — Addict to Cappuccino and Music
Hey there! I'm a software engineer who absolutely loves crafting web applications. Ruby is my go-to programming language, it's just my cup of tea! But hey, there's more to me than just programming.
Full-stack developer with 10+ years building software and managing infrastructure. Now focused on penetration testing, vulnerability research, and responsible disclosure.
Location
Latvia
Work
Full-stack dev & development manager. Co-owner @ hive5.
Hi everyone, my name is Jesus Guerrero. I am a Full-Stack developer from the Dominican Republic. I love to learn new things, share knowledge and create things..
For my own personal projects, i keep using PostgeSQL (not really sure why, but it's just seems to work for me). On the work side, MSSQL is the go to one. Here in Denmark, im not sure how many applications runs on other database platforms. I have never heard any coworker or other professional usie something else, but then again Denmark is a big Microsoft fanboy :D
Nice
great!
Hi. For internal company systems I use Microsoft SQL Server, for the majority of customers in the industry I also use MS SQL Server + PostgreSQL. But for Linux and low-cost solutions mainly PostgreSQL.
amazing!
I've been trying out
Surrealdband I like it a lot. I can use it as an embedded db or as a server/client model (makes testing pretty easy). The query language is nice and it also has built-in vector functions so I'm using it as a vector store for a Retrieval-Augmented Generation (RAG) pipeline.I also recently learned about
recfilesbut haven't had a chance to use them yet.Great!
MySQL (and Redis for cache and queues).
Honestly I haven't really experimented with anything else, I could easily switch to MariaDB (which is more or less a drip in replacement) or Postgres (since most of my projects use an ORM that can use MySQL or Postgres interchangeably). I know that MySQL works for me, after 10 years of using it I know how InnoDB works and how to optimize for it, I know which tools I need with MySQL (mostly tools from Percona)... So I don't really feel the need to start over with another DB.
I'll definitely use something like Mongo if I ever need to store non relational data, or Cassandra if I need to store data over many decentralized servers, and I indirectly use Elastic search for time series when I use graylog to store my logs. But it turns out most of the applications I build need a centralize datasource (with a few Replicas for availability) to store relational data, so MySQL it is !
great to know!
I am building one. Kind of insane.
Interesting... Why?
super!
For the back end, I prefer MySQL or PostgreSQL in GCP/AWS. For analytics, I use BigQuery daily.
Because of my specialty (data engineering), I must use all the databases mentioned and even more (depending on the project). Imagine migrating Access to SQL; it's very funny.
nice!
Hey, I'm head of product over at Xata. A large portion of our team came from Elastic and a common architecture we saw at scale was PostgreSQL + Elasticsearch as a way to get all the OLTP benefits of a relational database with full text search and metrics / aggregations for other application / analytical needs. This was seen across industries ranging from the ecommerce to commercial applications to the federal government. With the boost in AI use cases, I can only imagine this has become even more common of an architecture.
We've decided to productize this architecture as a service. If you're interested in learning more about the implementation details for inspiration, here's the architecture behind our platform: xata.io/docs/concepts/serverless-d...
MySQL and Redis (with SQL Server for access to some legacy data).
super!
MariaDB/MySQL, and a little of PostgreSQL. But I love using these databases with Prisma ORM
Amazing
Now redis is paid one ? Plz confirm
It's not, unless you want to resell it as managed service
Yes
no
SingleStore database for all the AI/ML applications:) Try it for free and once you sign up, you will receive $600 worth free credits to play around.
amazing
Currently we use PostgreSQL and Redis.
great
I use MySQL(mainly) and Redis.
great!
MongoDB for smaller projects and MySQL for bigger ones.
Redis for caching only.
super
Microsoft SQL Server
nice
Supabase (So postgresql) and SurrealDB
amazing
MySQL, Postgres, and SQLite
great
We use IBM DB2 at work. It's reliable but lacks a lot of modern features
awesome!
I like SQLite for most of the daily tasks
great!
MySQL and firebase mostly.
awesome!
with golang i am using these depending on situation: mariadb , sqlite, bboltdb
nice
I use whatever's right for the job. Typically, though, I use MariaDB or PostgreSQL for structured data, and MongoDB or CosmosDB for unstructured data.
great
For simple cases I use sqlite, which is easy to maintain. There is an API for NODE.JS or PHP.
Super
PostgreSQL
nice
PostgreSQL
nice!
PostgreSQL
amazing!
Oracle hentzer Google Amazon DOD.MI
nice!
Supabase hands down
awesome
I use Gauss DB in work
amazing
amazing
Elasticsearch and MongoDB
nice!
PostgeSQL
MySQL