Database hacker and free thinker. Open source user and developer

Worldwide
Joined May 2008
Giuseppe Maxia retweeted
Giuseppe Maxia ( @datacharmer ) created a tool that has helped people build reproducible database environments for years. At ProxySQL, we're continuing that work: maintaining the existing workflows, extending database support, and fixing the details that make a sandbox dependable. My latest dbdeployer post covers v2.4.2 and the progress since April, with examples you can try. If you use dbdeployer, I'd like to hear which database version and topology you rely on, and where you still hit friction. proxysql.com/blog/dbdeployer…
2
3
6
394
Giuseppe Maxia retweeted
Need a local MariaDB replication environment to reproduce a problem? Our dbdeployer update walks through downloading MariaDB 12.3.3, unpacking it, deploying a three-node replication sandbox, and running its replication test. It also covers Galera, PostgreSQL, and adding ProxySQL to supported topologies with --with-proxysql. Use a compatible host with the database runtime dependencies installed. The article includes prerequisites and links to the detailed guides. Try the examples with dbdeployer v2.4.2: proxysql.com/blog/dbdeployer… #dbdeployer #DatabaseTesting
4
4
165
Giuseppe Maxia retweeted
Test "today" filters around midnight, with the browser and server in different time zones. A date picker working at 2pm on your laptop is a very friendly test case :-)
1
1
4
336
Wooohoooo \o/ 3️⃣ PRs already merged into #dbdeployer - 💪 open source buff.ly/Su6Hv64
1
3
166
Giuseppe Maxia retweeted
dbdeployer v2.4.2 is out. A three-node MariaDB replication deployment reported at roughly 8 minutes now takes about 20 seconds after fixing an unnecessary readiness wait. Actual times depend on the environment. This release also fixes readiness checks for joining Galera/PXC nodes and expands MariaDB CI coverage. Our new blog goes beyond the release: MariaDB downloads, PostgreSQL improvements, cluster testing, and the work since April to make local database sandboxes more reliable. If you're using v2.4.0 or v2.4.1 for MariaDB, take a look: proxysql.com/blog/dbdeployer… #dbdeployer #MariaDB
1
2
2
121
Giuseppe Maxia retweeted
I've published an update on dbdeployer, including the v2.4.2 release and the work we've shipped since April. One fix is particularly noticeable: ordinary MariaDB nodes were waiting for Galera readiness even though they weren't part of a Galera cluster. Removing that wait brought a reported three-node replication deployment from roughly 8 minutes to 20 seconds. Your timing will vary. This is the kind of maintenance I care about: making a tool people already rely on easier to use, and catching the regressions that get in their way. There is also a lot to catch up on around PostgreSQL, MariaDB downloads, and cluster testing: proxysql.com/blog/dbdeployer…
2
3
198
Giuseppe Maxia retweeted
New interactive mini-book: Go concurrency distilled It gives a brief overview of many concurrency topics in Go, along with examples you can run in the browser. There's also a PDF version. The book is AI-free. antonz.org/go-concurrency-di…
12
85
6
657
35,775
Giuseppe Maxia retweeted
What is dbdeployer ? It’s a CLI tool for creating local database sandboxes in seconds. Run MySQL, MariaDB, or PostgreSQL instances, build replication topologies, test upgrades and failovers, then throw everything away and start again. Useful database experiments without production risk.
2
2
20
1,220
Giuseppe Maxia retweeted
The most visible PostgreSQL improvement in dbdeployer 2.4.0 is replication data-flow verification. The less visible work is just as important: binary layout, sharedir relocation, libpq5, ports, generated scripts, sandbox paths, and ProxySQL wiring. A database testing tool becomes useful when it handles the edges around the database process too. That is the direction we are continuing to take with the PostgreSQL provider. Docs: proxysql.github.io/dbdeploye…
1
1
3
231
Giuseppe Maxia retweeted
Some news: after 30+ years at other people's companies, I'm building my own. 808labs — independent media and analysis on early-stage startups, open source, and the people behind them. 808labs.io/
2
1
5
218
Giuseppe Maxia retweeted
After Percona Live, we turned the PostgreSQL + ProxySQL demo into something people can run locally. dbdeployer can now create PostgreSQL replication sandboxes with ProxySQL included. Primary + replicas + ProxySQL + helper scripts + pgbench + stats. Same workflow used on stage, now reproducible. proxysql.com/blog/dbdeployer… #PostgreSQL #ProxySQL #dbdeployer #PerconaLive
1
4
219
Giuseppe Maxia retweeted
Setting up booth at Percona Live #PerconaLive #ProxySQL – at Mountain View, CA
1
5
152
Giuseppe Maxia retweeted
OurSQL Foundation #PerconaLive
1
3
9
234
Replying to @datacharmer
😅 Supongo que lo ha mezclado con esto: xitter.cf/aventurasaber/status/2…
¡🗣️ Nueva sección de lengua con Álex Hererro! Hoy acompañado de Paco Álvarez, autor de ‘El español no nació ayer”. ▶️ Sección completa en: rtve.es/play/videos/la-avent… @delcastellano @planetadelibros @AlexvonKarma @la2_tve @rtveplay
1
1
78
Giuseppe Maxia retweeted
dbdeployer is BACK from the dead, and it’s even better with the ProxySQL team at the wheel No more crying in the server room trying to spin up test instances manually. This is great for every dev and DBA who lives in MariaDB/MySQL land. Thank you @lefred & @mariadb_org the sharing great news! mariadb.org/long-live-to-dbd…
We at the MariaDB Foundation are very happy that dbdeployer has risen from the ashes thanks to the ProxySQL team 🦭 🏗️ 🏕️ buff.ly/GxptWue
1
5
11
904
We at the MariaDB Foundation are very happy that dbdeployer has risen from the ashes thanks to the ProxySQL team 🦭 🏗️ 🏕️ buff.ly/GxptWue
1
1
4
1,067
Etimología de RECALCITRANTE 🫏 Ya a la venta «El español no nació ayer», un libro divulgativo sobre la evolución del español 🤓 Cómpralo en cualquier librería, NoNacioAyer.com o comenta NO NACIÓ AYER y te paso la información
5
2
26
1,192
Giuseppe Maxia retweeted
Having been part of the industry for 50 years, I can confidently report that none of this is true. Sure, writing code has a non-zero cost; this is true of any artifact. But you know what costs even more, Jonathan? Writing bad code; writing unnecessary code; writing more code than you really need simply because you think you might need it someday or you are too lazy or sloppy to clean up after yourself. Anything that costs nothing is often worth nothing as well, and results in significant unintended consequences.
For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews. This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system. LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it. If you're a Yes Engineer, the next decade is yours.
82
236
29
2,277
133,841
Giuseppe Maxia retweeted
Orchestrator is back. After being archived, it now has a new home at ProxySQL. For me, this is about more than maintenance: → topology intelligence + traffic routing → MySQL + PostgreSQL → modern HA, done right We’ve already started. Much more coming. 👉 github.com/ProxySQL/orchestr… Announcement: proxysql.com/blog/announcing… #proxysql #mysql #postgresql #highavailability #databases #failover #dba #opensource
1
7
18
1,023