We changed our name from IT Central Station: Here's why


55 Points
4 Years

User Activity

Over 4 years ago
Before jump into an Open Source Database, you need to understand that any bug or feature is attached to the workforce behind it. It could be a company/companies or a huge community. Been said, you need to practice patience and learn how to feed the cycle to improve it too…

About me

Please allow me to introduce myself, I'm a man of wealth and taste. I've been around for a long, long years (specifically from 2006 since I started to *work* on IT, but enrolled in several communities prior that). And I was 'round when Open Source, had its moment of doubt and pain.

I've worked with a very heterogeneous set of technologies and companies, from boutique services to large consulting firms, telecommunications companies for training and consulting.

Mostly focused on data and its process, from pipelines, workers, queues and databases/datastores.

Code fixing in several languages is something that I do on a daily basis (Python, Perl, Go, R, Bash and other shells).

Although I've played with Windows in the past, I consider that at least 98% of the servers run Linux, Unix BSD or Solaris.

Postgres and MySQL/MariaDB (several engine experience, as Aria, InnoDB, Rocks, Federated and MyISAM) are my most known database systems. However, I've hands on others DB/DS experience in Oracle, Vertica, MongoDB, Redis, Greenplum, among others.

Good AWS experience.

In a second tier of technologies, I like/use-not-so-frequently some other technologies as Elasticsearch, Sphinx, rabbitmq, zeromq, ansible, cassandra and others.

Some of the customers I worked in: Zendesk, Sendgrid, Microsoft, Pinterest, Box, NatGeo, Mozilla Foundation among others.