Hey guys, we're looking for MySQL ops folks.
Skills required:
1. Ability to understand the instructions in this mail 2. You gotta rock* at mysql administration (sorry, if you pop, hip hop, rap or disco, you're not good enough) 3. Experience on FreeBSD is a major plus, linux or other Unix sufficient
You'll have to move to Bangalore (or stay there if that's where you already are).
Send your resume to me as an attachment in plain text or html format. Include significant differences between MyISAM, InnoDB and MaxDB in your email. Do not copy-paste from a website.
*rock: you must be really really good. Know the MySQL administrators docs inside out, be able to work with MyISAM as well as InnoDB and recommend when to use which. Be able to backup a db with minimum downtime (If you can do it in zero downtime then we want to talk to you).
Philip
PS: In case you were wondering, we're a Media company who have recently opened an office in Hollywood ;)
On Friday 11 Feb 2005 2:18 am, Philip Tellis wrote:
PS: In case you were wondering, we're a Media company who have recently opened an office in Hollywood ;)
if there is a vacancy in the Hollywood office, i may be available even if it means messing with mysql (yuck) - btw, if you do not have historical reasons for using mysql, you could save quite a few bucks by using postgresql as the level of expertise required would be much less.
On Fri, 2005-02-11 at 11:25, Kenneth Gonsalves wrote:
if there is a vacancy in the Hollywood office, i may be available even if it means messing with mysql (yuck) - btw, if you do not have historical reasons for using mysql, you could save quite a few bucks by using postgresql as the level of expertise required would be much less.
i think it would be difficult to explain to the various MySQL developers on the roll of said company the reason for shifting to pgSQL :)
-gabin
On Friday 11 Feb 2005 11:32 am, Gabin Kattukaran wrote:
On Fri, 2005-02-11 at 11:25, Kenneth Gonsalves wrote:
if there is a vacancy in the Hollywood office, i may be available even if it means messing with mysql (yuck) - btw, if you do not have historical reasons for using mysql, you could save quite a few bucks by using postgresql as the level of expertise required would be much less.
i think it would be difficult to explain to the various MySQL developers on the roll of said company the reason for shifting to pgSQL :)
tahts what i meant by historical reasons - if you look at the job specs, 90% of it is underrstanding the peculiarities of mysql and only 10% is sql expertise
On Fri, 2005-02-11 at 13:28, Kenneth Gonsalves wrote:
On Friday 11 Feb 2005 11:32 am, Gabin Kattukaran wrote:
i think it would be difficult to explain to the various MySQL developers on the roll of said company the reason for shifting to pgSQL :)
tahts what i meant by historical reasons - if you look at the job specs, 90% of it is underrstanding the peculiarities of mysql and only 10% is sql expertise
let me rephrase that. i didn't mean people who use MySQL. i was talking about people who make MySQL.
-gabin
On Friday 11 Feb 2005 2:20 pm, Gabin Kattukaran wrote:
tahts what i meant by historical reasons - if you look at the job specs, 90% of it is underrstanding the peculiarities of mysql and only 10% is sql expertise
let me rephrase that. i didn't mean people who use MySQL. i was talking about people who make MySQL.
they wont listen, they are quite happy with their product
Sometime on Feb 11, Kenneth Gonsalves assembled some asciibets to say:
tahts what i meant by historical reasons - if you look at the job specs, 90% of it is underrstanding the peculiarities of mysql and only 10% is sql expertise
No no no, we don't want SQL programmers. We want MySQL administrators. The kind of people who get paged if the server goes down.
On Saturday 12 Feb 2005 1:51 am, Philip Tellis wrote:
No no no, we don't want SQL programmers. We want MySQL administrators.
classic description of mysql - i'm going to print it out and frame it!
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
On Saturday 12 Feb 2005 1:51 am, Philip Tellis wrote:
No no no, we don't want SQL programmers. We want MySQL administrators.
classic description of mysql - i'm going to print it out and frame it!
manje kai? We already have programmers. Programmers don't do ops work. We need ops folks. IAC, no one writes SQL programs. One writes code in C++.
On Saturday 12 Feb 2005 5:07 pm, Philip Tellis wrote:
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
On Saturday 12 Feb 2005 1:51 am, Philip Tellis wrote:
No no no, we don't want SQL programmers. We want MySQL administrators.
classic description of mysql - i'm going to print it out and frame it!
manje kai? We already have programmers. Programmers don't do ops work. We need ops folks. IAC, no one writes SQL programs. One writes code in C++.
well, the difference between msyql and sql standard rdbms's is precisely that in mysql you control the database by writing external code whereas in standard sql the database does the work and the coding is within the database - and the database does most of the work. I am involved in a project where we are shifting from mysql to postgresql, and we have already eliminated hundreds of lines of code. In my humble opinion, a database driven application should have two levels only - ui and database. The business logic should be coded in the database. So you have a ui guy and an sql guy. Mysql forces you to employ two more guys - a c++ guy and a mysql admin guy. Here i must admit that i dont practice what i preach - i am flawed as i learnt sql using mysql and unfortunately most of my older projects are polluted by that background - but not any more.
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
well, the difference between msyql and sql standard rdbms's is precisely that in mysql you control the database by writing external code whereas in standard sql the database does the work and the coding is within the database
Oh, ok, you're talking about stored procedures and PL/SQL. I agree with you there that most database logic can be thrown into stored procedures. I do not however agree that you can do everything in SQL and just do UI at the next level (PHP/Perl/Python/whatever).
There is quite a bit of logic that needs to be done at a middle level, which is where C++ comes in.
Philip
On Saturday 12 Feb 2005 7:10 pm, Philip Tellis wrote:
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
well, the difference between msyql and sql standard rdbms's is precisely that in mysql you control the database by writing external code whereas in standard sql the database does the work and the coding is within the database
Oh, ok, you're talking about stored procedures and PL/SQL. I agree with you there that most database logic can be thrown into stored procedures. I do not however agree that you can do everything in SQL and just do UI at the next level (PHP/Perl/Python/whatever).
There is quite a bit of logic that needs to be done at a middle level, which is where C++ comes in.
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
What happens when the DB server goes down? What happens when replication mysteriously stops? What happens when a slave goes down during replication?
On Sunday 13 Feb 2005 12:03 am, Philip Tellis wrote:
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
What happens when the DB server goes down? What happens when replication mysteriously stops? What happens when a slave goes down during replication?
no idea - never happened to me on postgres, but i think any reasonably competent SQL guy could fix it
On Sunday 13 Feb 2005 12:21 pm, Philip Tellis wrote:
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
no idea - never happened to me on postgres, but i think any reasonably
what kind of loads have you looked at :)
i'm very small potatoes (maybe a wheelbarrow) - but wouldnt crashes under heavy load be more a sysadmin thingie? I know i started this thread more for mysql bashing, but i have a project in the offing with pretty heavy load and you have set me thinking - maybe i would need a db op. But i personally feel that i can get away with a sysadmin and spend my money on sql guys.
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
pretty heavy load and you have set me thinking - maybe i would need a db op. But i personally feel that i can get away with a sysadmin and
You can if your sysadmins don't have other work. Depends on whether you have to admin < 3 servers or > 30000 servers.
Sometime on Sun, Feb 13, 2005 at 02:42:19PM +0530, Philip Tellis said:
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
pretty heavy load and you have set me thinking - maybe i would need a db op. But i personally feel that i can get away with a sysadmin and
You can if your sysadmins don't have other work. Depends on whether you have to admin < 3 servers or > 30000 servers.
You mean to say Yahoo!
Anurag
On 12/02/05 19:34 +0530, Kenneth Gonsalves wrote: <snip>
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
The appropriate term is DBA (aka database administrator). Parallel roles are:
webmaster -- website hostmaster -- DNS postmaster -- email sysadmin -- base OS and some hardware.
Devdas Bhagat
On Wednesday 23 Feb 2005 9:48 pm, Devdas Bhagat wrote:
On 12/02/05 19:34 +0530, Kenneth Gonsalves wrote:
<snip>
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
The appropriate term is DBA (aka database administrator).
does the dba enter into the database or maintains it from outside?
On 24/02/05 09:18 +0530, Kenneth Gonsalves wrote:
On Wednesday 23 Feb 2005 9:48 pm, Devdas Bhagat wrote:
On 12/02/05 19:34 +0530, Kenneth Gonsalves wrote:
<snip>
ok, you need a C++ guy to do some some stuff - i agree. But what is the need for a db-op?
The appropriate term is DBA (aka database administrator).
does the dba enter into the database or maintains it from outside?
Both. A DBA is responsible for the database server. The DBA is also supposed to help with the design of a database structure and to write stored procedures as needed, amongst other things.
Devdas Bhagat
Sometime Today, Kenneth Gonsalves assembled some asciibets to say:
On Friday 11 Feb 2005 2:18 am, Philip Tellis wrote:
PS: In case you were wondering, we're a Media company who have recently opened an office in Hollywood ;)
if there is a vacancy in the Hollywood office, i may be available even
Not that I know of. I know only of vacancies in the Bangalore office.
if it means messing with mysql (yuck) - btw, if you do not have historical reasons for using mysql, you could save quite a few bucks
we have historical reasons.
-
Anurag -
Devdas Bhagat -
Gabin Kattukaran -
Kenneth Gonsalves -
Philip Tellis