“So, I suppose MySQL’s main competitor is Oracle?” is a frequent question I get asked by the press. “Well, we don’t really compete heads-on with other databases. We co-exist! Just as an example: Over a third of respondents in an Oracle User Group survey said they also use MySQL”, I answer.

The reporter then continues “But everyone has a main competitor. Don’t you plan for people to migrate from Oracle to MySQL?”. I continue with “Not really. Migrations do happen, but not all that often. MySQL tends to be used in new applications.”

“But surely you must have some competitive atmosphere, or equivalent feelings towards Oracle.” The reporter never gives up. “Don’t you at least internally joke about your relationship with Oracle?”.

And that’s where I will now have a new answer for whichever reporter nexts goes down that line of reasoning.

So let me take that story from the beginning. My fourteen-year-old son has just started blogging about football, and his second blog entry is about an existential issue involving the moral values of loyalty and competition. After many years as a fan of Germany’s incumbent football team Bayern München, and after a not-so-great start of the season for the team, he went to a match with the local arch-rival TSV 1860. The 1860ers are not in the German First League, and they are somewhat of an underdog. And now he’s starting to question his loyalty towards Bayern München.

I shared his blog ponderings over email with the group of people formerly known as MySQL GmbH employees, one of whom saw a surprising analogy: Between Bayern München / TSV 1860 and Oracle / MySQL. It was so hilarious, that I dare share it, as a symbol of the type of stories we sometimes circulate internally. My son has two lists, “Why to stay with Bayern München” and “Why to switch to TSV 1860″. My colleague translates these football loyalty questions to database choice questions.

The blog is in German (as is my colleagues email), and instead of a complete but somewhat weird Google Translate conversion, I’ll here provide a slightly more polished translation (and the Oracle comments by my colleague in parenthesis):

These facts speak for continuing as a Bayern fan (… as an Oracle user):

1. I am still a member (I still use Oracle)
2. A sold-out stadium looks good (Oracle Datacenter looks good)
3. All my Bayern fan gadgets (all my Oracle fan gadgets)
4. The feeling of “Your hatred is our pride” (ditto)
5. German Premier League and Champions League, at least for the time being (ditto)
6. Some good players, such as Ribéry
7. I was always a Red [fan of Bayern], and “conversions” is bad form (I was always a fan of Oracle and …)

This speaks for a switch to TSV 1860 (… a switch to MySQL):

1. I’ll get tickets much easier (MySQL is lots easier to obtain)
2. My school is full of Lions [fans of 1860], I’d have fewer fights (there are so many MySQL Forums with helpful co-developers, even a MySQL Forum on Oracle)
3. The transfer policy of Bayern (the sales policy of Oracle)
4. The atmosphere in the stadium is somewhat better (the atmosphere at the MySQL user’s conference is clearly better)
5. Being an underdog feels good
6. More creative fans, including songs (there are creative MySQL songs, too!)
7. Sometimes when Bayern plays, you’re the only one who sings in your area of the stadium (plenty of MySQLers sing, even on YouTube!)
8. Frequently, Bayern fans are Bayern fans only “because they always win” (Frequently Oracle fans are Oracle fans and not Open Source fans, “because you’re not fired for buying Oracle”)

The conclusion, in database terms?

• MySQL co-exists with other databases, such as Oracle
• MySQL is often used for web apps in these coexistence scenarios
• MySQL focuses on applications that scale
• MySQL has a low TCO
• Oracle DBAs may want to add MySQL skills to their resume

Links, if you want to pursue the above thoughts:

• MySQL Resources for Oracle DBAs: http://www.mysql.com/news-and-events/oracle/
• MySQL TCO Savings Calculator: http://www.mysql.com/tcosavings/
• DBA Boot Camp: MySQL for the Oracle DBA: http://www.mysql.com/news-and-events/oracle/oracle_bootcamp/
• Oracle Users Indicate Increase in Use of Open Source: http://www.mysql.com/why-mysql/white-papers/mysql_wp_ioug.php
• MySQL Unlimited: Deploy an unlimited number of MySQL Enterprise Servers for the price of a single CPU of Oracle Enterprise Edition: http://www.mysql.com/products/enterprise/unlimited.html
• Lycos Europe Migrates to MySQL, Reduces TCO by 90%: http://www.mysql.com/why-mysql/case-studies/mysql-lycos-casestudy.pdf
• T-Systems Relies on MySQL: http://www.mysql.com/why-mysql/case-studies/mysql-tsystems-casestudy.pdf

Reminders work. At least on me. I try to Get Things Done (TM) efficiently, but slips do happen. And when they do, reminding me has a good chance to influence my priorities. I hope I’m not alone in this fallibility.

And therefore I want to remind you that you’ve still got two weeks to reply to our Call for Participation in the MySQL Conference and Expo in Santa Clara, California on 20-23 April 2009.

A few items to remember:

• We have plenty already, but we’re looking for more proposals. It does make our selection process harder (that’s when the Program Committee sits down and asks itself “what’s right for the conference and its participants”), but that’s a task that we are happy to work on.
• The theme of the conference is “Innovation Everywhere“, so put an emphasis on innovative proposals! Giuseppe has something to add on this.
• Look at Giuseppe Maxia’s suggestions on how to get your proposal accepted to the MySQL Conference 2009, or Baron Schwartz’s and Colin Charles’s respective suggestions from last year.
• This year, we will approve some sessions conditionally, meaning that the decisions we start making after the CfP has closed won’t necessarily be binary (accepted/rejected), so some of you may expect further contacts from us.

Looking forward to more proposals the upcoming two weeks. Why don’t you propose something innovative right now?

At the end of the Orlando meeting in January this year when the Sun acquisition was announced, I remember sitting next to MySQL’s co-founder David Axmark in the bus going to some evening event. “What do you want to do now, with so many opportunities opening up?” was my question to him, partly as his friend, partly as his colleague and partly as his line manager. David seemed very confident in the future of MySQL within Sun, but less sure about his own future role.

With that as a background, and knowing David since well over 20 years, I was not all that surprised to read his resignation letter, and in particular his reasoning for resigning:

I have thought about my role at Sun and decided that I am better off in smaller organisations. I HATE all the rules that I need to follow, and I also HATE breaking them. It would be far better for me to “retire” from employment and work with MySQL and Sun on a less formal basis.

Let me recap what David has done for MySQL. David is the reason MySQL is FOSS. Without David, MySQL wouldn’t be GPL (Monty originally planned a closed-source product). David is also the reason people associate MySQL primarily with Sweden and less so with Finland, since MySQL AB was founded in Uppsala to be close to David (and our third co-founder Allan Larsson).

(The above scene from Stockholm harbour shows the boats of database entrepreneurs David Axmark and Larry Ellison; after the acquisition of MySQL by Sun, David may afford an upgrade, even after his donation to the Software Freedom Law Center).

I wish David would have stayed longer at Sun, but I understand why he decided to resign and I respect his decision. I’m happy he’s fine with working as a consultant for Sun, doing speaking engagements and connecting us with his huge network. It’s very much appreciated.

We share so many fond memories together, starting from our first meeting sometimes in the 1980s at Monty’s place in Gamla Skomakarböle, in the outskirts of Helsinki. And then there was the memorable trip to MySQL’s first CeBIT appearance in 2001, just after I had agreed with Mårten and Monty to join MySQL. And hiking in Larry Stefonic’s bivvy sacks on a mountain in Washington. And countless other stories.

I’ve learnt so much from David, particularly as he’s been my predecessor, role model and esteemed colleague in plenty of respects over the time at MySQL AB. He has lead Engineering, before we started to recruit people with the title of “VP Engineering”. He’s lead Internal IT. He’s lead the Community efforts. He’s worked with the FSF. He’s managed and moderated his somewhat more, ehmm, hot-tempered co-founder Monty. He’s travelled the world, with a particular fondness for Asia. And he’s taken oodles of digital pictures. Not that I’ve followed David in all aspects, but it does seem I’ve copied him in the above respects, with sometimes a shorter, sometimes longer latency.

You won’t be surprised that I feel a deep gratitude for what David has done. In particular, I want to thank him for introducing me to all the wonderful people in the FOSS community. And I’m sure all Sun Dolphins will join me in the most important thank-you note:

Thanks David for having and pursuing the vision that made you found MySQL!

Lest we become overly sentimental, let me say that I am confident David will continue in his role as an overall FOSS ambassador. Nearly a quarter century working on FOSS as a pioneer gives David insights that few of us have, that Sun is happy to continue learning from, and that I’m sure David is happy to share with budding Open Source companies.

I’m just back home from Brazil, where I went last Sunday in order to launch MySQL’s presence in Brazil and meet with MySQL users, developers, Sun customers, the press as well as with numerou Sun colleagues. “Is this your first time in Brazil?” was a frequent question (as one could expect), and I was happy to respond that it wasn’t. In fact, I have particularly fond memories of my first visit to Brazil in 2001, as that was the trip when I decided to join MySQL AB.

They say Rio de Janeiro is one of the most beautiful cities on the planet. Whoever “they” are, they’re right. The cone in the middle is Pão de Açúcar (Sugarloaf Mountain, der Zuckerhut, Sockertoppen).

As a European, I again noted that Brazil frequently feels much more like home than the US does. In Brazil, they use the metric system, they measure temperature in Celsius, they write dates and times of day in a familiar way, they cheer for Formula 1 drivers and they play football. My Brazilian colleagues and I fought a bit over whether Finland or Brazil produces the better F1 drivers, but despite Finland nearly beating Germany (thanks Jonatan Johansson, Mika Väyrynen and Daniel Sjölund!) in the World Championship qualifications last month, I had to concede to the football superiority of the Brazilians. Nonetheless, it felt good to meet with colleagues to whom I could describe the ethical dilemma my son Alexander faced (and explained in his newly started German language football blog) when MySQL 5.1 user Corrado Pandiani from Inter Milan sent him gadgets that on the one hand are objectively speaking very cool (such as a poster signed by Zlatan Ibrahimovic, Luis Figo and Marco Materazzi), but on the other hand represent a team which a Bayern München fan like him has hard to identify with.

But back to MySQL. This week, I had the pleasure of not just attending the Sun Tech Days including its press events, but also visit many customers in both São Paulo, Brasília and Rio de Janeiro. It’s great to see the broad interest for MySQL. Yet, the interest for MySQL in Brazil didn’t surprise me. We know from the download statistics that .br is a top five country for downloads, and more concretely, MySQL had a sizable following in Brazil already in 2001. When Mårten Mickos (MySQL’s then newly appointed CEO), Michael “Monty” Widenius (co-founder) and a number of friends of ours visited the Rio Carnival wearing MySQL t-shirts, we were stopped on Copacabana beach and asked whether “we are also MySQL users“. What a feeling it was, to personally experience recognition for MySQL over seven years ago, in a country where none of us had been before!

Ah, as I am walking down Memory Lane, let me share a few other pics from 2001 (the ones from this week are still in Philip Antoniades’s camera):

Mårten and Monty looking at where to go in the Rio metro. As this was during the pre-Sakila-lithic era, Monty wore an old, dragon type “mySQL” T-shirt (yes, lower case m).

Helvécio Borges Filho from EAC  (to the right of me) hosted us in 2001, and over the years, we’ve met many times since at MySQL Users Conferences and elsewhere — such as last Tuesday at Sun Tech Days in São Paulo. Yesterday, Copacabana was quite a bit more rainy than above.

Cristo Redentor (Christ the Redeemer) at the Corcovado Mountain.

Monty evidently also wants to redeem (with Corcovado in the background). And I am always fond of teasing Monty for his taste for a particular artificial drink with a closed-source recipe.

As I’m sure you can tell, I was very impressed with Brazil both in 2001 and in 2008. I won’t wait seven years until my next visit!

Bom dia!

On Monday and Tuesday this week, a team of MySQLers (”Sun Dolphins”) and Sunnies (”Sun Classics”) launched the commercial presence of MySQL in Brazil.

This means we have now have ambitions well beyond the growth of the MySQL user base in Brazil, which already is in the top five countries of the world when it comes to downloads. In other words,

• we have a senior sales person assigned, with a sales goal for Brazil
• we are recruiting sales engineers for Brazil
• we are recruiting Support Engineers, who will deliver MySQL support in Portuguese
• we are recruiting Consultants, who will deliver MySQL professional services in Portuguese

During the Sun Tech Days in São Paulo, we had the opportunity to share these news with both a developer and a business audience, as well as with several representatives from the press. “We” included fellow MySQLers Del Ruiz and Philip Antoniades, as well as Sun Classic employees Rodolfo Fontoura (Country Manager of Sun Microsystems do Brasil), Eramir Fernandes Junior (heads the Sun Software Practice in Brazil) and Jim Parkinson (Sun VP for Developer, Tools and Services) and many others.

I’m happy to note that we got plenty of attention, both from the press and from the developer and business audience. I was also grateful to receive positive attention for my attempt at localising my presentation beyond English through speaking Portuguese for the first part of my speech (see below). Thanks Eramir for the translation, and thanks to the audience for enduring my oral mistreatment of your beautiful language!

Prezados usuários de MySQL, prezados clientes da Sun, prezados parceiros da Sun, senhoras e senhores, bom dia e bem vindos a este evento para lançar oficialmente a MySQL no Brasil, e celebrar a aquisição da MySQL AB pela Sun Microsystems, e ainda ajudar todos a entender melhor como vocês podem se beneficiar destas duas empresas estarem juntas agora.

Meu nome é Kaj Arnö, sou o vice-presidente de Relações com a Comunidade na MySQL. Eu vivo em Munique, Alemanha, mas eu não sou Alemão; Eu sou Finlandes, como o fundador e CEO da MySQL, e muitos outros colegas na MySQL. Na integração da MySQL com a Sun, também tenho a tarefa de Embaixador MySQL na Sun, o que significa que eu vivo de um escritório da Sun ao outro e explico o que é tudo isso sobre a MySQL.

Um dos temas de hoje é, como eu já disse, a aquisição da MySQL pela Sun. Muitos nos perguntam, como empregados da MySQL, o que pensamos sobre o assunto. Não é uma pena perder a nossa independência, e o sonho de um IPO? Minha resposta pessoal, e da grande maioria, é muito pelo contrário. Nós estamos felizes de chegar a varias novas oportunidades com os recursos da Sun. E, o que nossos novos colegas na Sun pensam? Eu já conversei com centenas deles, e não encontrei ainda um único indivíduo que não esteja entusiasmado com a aquisição.

Mesmo assim, o que vocês pensam é muito mais importante. E eu penso que a aquisição é boa notícia também para nossos clientes e usuários. A Sun é a maior desenvolvedora de software livre no mundo (Open Office, Open Solaris, Glassfish, NetBeans, Java) e pode nos dar mais recursos do que já tivemos até hoje.

Também é muito, muito importante destacar, que a aquisição significa mais possibilidades, e não menos. Na Sun, vamos continuar a suportar os mesmos sistemas operacionais que antes - Linux, Windows, OSX etc. Assim como os ambientes de desenvolvimento:PHP, Ruby, OBDC, .Net. Talvez veremos ainda mais possibilidades para Solaris e para Java, mas não com prejuízo para as outras plataformas.

Eu estou quase terminando, mas eu ainda quero dar uma resposta curta a uma pergunta freqüente: Por que a Sun comprou a MySQL? Minha resposta é: Porque os valores e a cultura de trabalho é a mesma na Sun e na MySQL, mas os clientes são com freqüência diferentes (exceto pela industria de telecomunicações). E isso significa que podemos juntos trabalhar bem, oferecendo produtos e serviços de uma companhia aos clientes da outra.

Tenho certeza que vocês já notaram, eu não falo Português. E como eu suspeito que a maioria não fala Sueco (minha língua materna) e não gostariam que minha apresentação levasse uma eternidade (o que pode acontecer se continuar assim), Vou ter que trocar para uma língua que é estrangeira tanto para vocês como para mim: Inglês. Minhas desculpas, e agradeço a atenção, até agora.

Links to the Brazilian press coverage of the MySQL launch:

• Decision Report: “Sun reforça operação com MySQL na AL e reafirma código aberto”
  http://www.decisionreport.com.br/publique/cgi/cgilua.exe/sys/start.htm?infoid=3257&sid=29

• B2B Magazine: “Sun Microsystems oficializa compra da MySQL”
  http://www.b2bmagazine.com.br/web/interna.asp?id_canais=4&id_subcanais=23&id_noticia=23181&pg=

• Info Online: “Sun monta equipe para MySQL no Brasil”
  http://info.abril.com.br/aberto/infonews/092008/29092008-22.shl

• Exame (Assinatura): “Sun inicia esforço para converter usuário do MySQL em cliente”
  http://portalexame.abril.com.br/agencias/reuters/reuters-tecnologia/detail/sun-inicia-esforco-converter-usuario-mysql-cliente-116796.shtm

• Convergência Digital: “MySQL é uma das prioridades de negócios da Sun no Brasil”
  http://www.convergenciadigital.com.br/cgi/cgilua.exe/sys/start.htm?infoid=16077&sid=5

• ti inside: “Sun diz que compra da EDS pela HP não vai impactar seus negócios”
  http://www.tiinside.com.br/News.aspx?ID=94116&C=265

• Reuters:
  http://tecnologia.terra.com.br/interna/0,,OI3220111-EI4795,00-Sun+inicia+esforco+para+converter+usuario+do+MySQL+em+cliente.html

• Computerworld: “Sun quer até 300 novos clientes em MySQL no Brasil até 2009″
  http://computerworld.uol.com.br/mercado/2008/09/29/sun-quer-ate-300-novos-clientes-em-mysql-no-brasil-ate-2009/
  

• Resellerweb: “Sun Brasil detalha planos após compra do MySQL”
  http://www.resellerweb.com.br/noticias/index.asp?cod=51734
  
  “Canal tem papel de peso nos planos da Sun com MySQL”
  http://www.resellerweb.com.br/noticias/index.asp?cod=51737

• IT Web: “Sun Brasil detalha planos após compra do MySQL”
  http://www.itweb.com.br/noticias/index.asp?cod=51736
  

Today is Good News Day. In addition to my note on Ivan Nikitin’s improved health, I have good news for our current and potential code contributors:

We have moved from having used MySQL AB’s own Contributor License Agreement (CLA) to now using the Sun’s Contributor Agreement (SCA), which is shorter and easier.

I’ve been asked about our contributor licensing on several occasions, such as back in July, at MySQL Camp in Bangalore, India, as Parvesh mentioned in his blog.

The MySQL Contributor License Agreement (CLA) was an agreement that we asked patch and feature contributors to sign in order to allow us to use their contributions in MySQL Server, which is licensed both under GPL and under our commercial license. The CLA required that the contributors transfer the copyright of their code to MySQL, while of course retaining a perpetual license to use their code in any way they wanted.

Some of our community members objected to having to transfer the copyright to MySQL. And we took it as our homework to double and triple check whether we really need that strong rights from a legal perspective, when Sun could do with the more light-weight SCA (Sun Contributor Agreement). I’m happy to note that this double-and-triple checking is completed, and we’re going to the simpler and clearer SCA. Moreover, the SCA guarantees that your contribution will always be made available as open source. Not that we ever had the intention of revoking that, but I’m sure the contributors will appreciate this guarantee in the SCA.

The whole MySQL Community Team and the MySQL Entineering Team hope that this news is greeted warmly by the greater contributor community. I encourage further feedback as to how we can continue to remove barriers to our community and best collaborate and encourage an “Architecture of Participation”.

You can find information about the Sun Contributor Agreement and general
information about the contributor process online at the Contribute section of the MySQL Forge
and take a look at the SCA on Sun’s website.

In addition, as a contributor, you can choose to digitally sign the SCA via the MySQL Forge’s online contribution system.

Do note that those who already have signed the CLA need to submit the SCA form, if they want their future contributions be covered by the SCA.

To be specific: For those contributors who previously signed the MySQL Contributor License Agreement, your contributions will continue to be governed under the CLA. If you wish to instead have your contributions covered under the new Sun Contributor Agreement (recommended) we encourage you to resubmit under the online SCA form and your contributions will then be covered under the SCA.

Thanks to Jay Pipes for driving this CLA-to-SCA process!

Links:

• Contributing to MySQL: http://forge.mysql.com/contribute/index.php
• Sun’s SCA: http://www.sun.com/software/opensource/contributor_agreement.jsp
• Signing the SCA: http://forge.mysql.com/contribute/cla.php?action=add

Good news: Ivan Nikitin is feeling better all the time. He has gone through insightful treatment in Heidelberg, and he is responding very well to it. The best part is that while the donations aren’t yet sufficient for a transplantation, it does look as if a transplantation may not even be necessary; the German doctors give Ivan’s body a chance to regenerate by itself, and it worked. And the generous donations from MySQLers, from classic Sun employees and also from the MySQL user community have made Ivan’s treatment in Heidelberg possible, something for which we are all very grateful.

Ivan Nikitin in Georg Richter’s lap (in Georg’s boat)

Ivan’s father Andrii allowed me to publicly quote his email to MySQL employees:

Hello MySQLers,

Ivan’s condition goes with most optimal scenario - doctors think he will not require transplantation because he provides positive answer to treatment from German doctors. Ivan’s state is better with every day since August, but to be sure doctors suggest that we should visit Heidelberg clinic for 5-6 weeks (hopefully not more).

Ivan is allowed to do whatever he wants so he enjoys running, shouting, singing, playing, (even swimming), etc. This is very unusual and happy time for us after 9 months in Kiev clinic with heavy medicine where he was allowed to go outside and see parents just couple times per week.

So we are very happy family now! I am sure this is because so many people think and care about us! Thanks everybody for donations and support! Many thanks to Georg who is helping us all the time and especially for arrangement of our arrival to Heidelberg!

Andrii, Alice, Ivan, Artem

A cropped version of the above, with just Georg and Ivan

I don’t yet have an update about the financials, i.e. how much money has been collected, and how much is needed by his treatment. I hope to fill you in on those things in my next Ivan blog entry.

But in the meantime, I’m very happy to share this good news!

Yesterday, I completed a most significant emotional step in the integration of MySQL into Sun. As about 75 % of MySQLers had already done prior to myself, I migrated my main mail account from MySQL’s mail server to Sun’s.

Yes, I am still reachable @mysql.com. And I was already earlier reachable on @Sun.COM, in addition to my private @arno.fi. But now Sun’s email server is the one I use for both sending and receiving email. So this minor administrative step raises questions for me whether my signature should primarily feature my @Sun.COM email address, or whether I should remain @mysql.com. Luckily (strangely? sadly?) Sun allows me to follow my own judgement on this one.

A reason for happiness is that I am reachable as “kaj” on both @mysql.com and @sun.com. This relieves me from the humiliation of constantly seeing a new, unfamiliar garbling of my last name. In Finland, we’re of course used to foreigners not knowing the final three letters of our alphabet, “åäö”. So I’ve been garbled to “Arno” on occasion in my adult life. Dropping the dots and rings is a more or less official misspelling custom of email addresses in Nordic countries, so while it still hurts my eyes, it’s something I’ve grown accustomed to. However, the Germans misspell differently. They garble me to “Arnoe”. While each country has its own customs, and I tell myself to be respectful of that, I still get frustrated every time my name is violated.

So please email me on a first-name basis. As firstname@mysql.com, as firstname@sun.com, or as firstname@lastname.countryofcitizenship.

Within minutes after Finland was just about to win 3:2 over Germany in the football world championship qualifications (but it ended 3:3), I got a bit of consolation for myself, my dual-citizenship son cheering for Finland, and my fellow countrymen using MySQL:

We have the next MySQL 5.1 Use Case article live, and it’s about FC Inter Milan. No Finns playing there (but stars such as Ibrahimovic, Materazzi, Luis Figo, and Adriano). And, from a MySQL perspective, the interesting point is that FC Inter Milan is using both MySQL 5.1 Partitioning and the Event Scheduler in an innovative way.

Thanks Corrado Pandiani for the story — let’s hope your good Use Case inspires others!

Links:

• FC Inter Milan Using MySQL 5.1 Partitioning and Event Scheduler: http://dev.mysql.com/tech-resources/articles/pandiani-use-case.html
• The MySQL 5.1 Use Case competition: http://dev.mysql.com/tech-resources/articles/mysql-5.1-use-case-competition.html
• FC Inter Milan: http://it.wikipedia.org/wiki/Inter
• Finland-Germany 3:3: http://svenska.yle.fi/nyheter/artikel.php?id=138742

Tomorrow, there’s a particularly interesting MySQL University session coming up: The OpenSolaris Web Stack.

This session is presented by key experts outside the Database Group, but inside Sun:

• Jyri Virkki, lead for OpenSolaris Web Stack community, Sun Microsystems
• Murthy Chintalapati, Web Stack development, Sr Engineering Manager, Sun Microsystems

For practical reasons, this session happens three hours later than normal. To decipher that into a timezone which may be familiar to you, this means 9:00 PST / 16:00 UTC / 17:00 GMT / 18:00 CET.

Abstract:

OpenSolaris Web Stack is an OpenSolaris project and community building an integrated stack of popular open source web tier infrastructure technologies such as Apache HTTP server, MySQL, memcached, PHP and Ruby On Rails optimized for Solaris platform. This session introduces OpenSolaris Web Stack, its status and future development including addition of newer technologies such as lighttpd, Varnish etc., as well as the ease of use features for developers and deployers. We will also be discussing an experimental web stack IPS package repository and it could be leveraged to build and make available popular end user applications such as Drupal.

You don’t have to register, but it certainly is appreciated if you do so, by filling in your name on the session Wiki page. That Wiki page also contains a section to post questions. Please use it!

Those planning to attend a MySQL University session for the very first time should probably read the instructions for attendees.

Finally, you may want to take a look at the complete list of upcoming University sessions.
Links:

• Session Page on Forge Wiki: http://forge.mysql.com/wiki/OpenSolaris_Web_Stack
• MySQL University home page: http://forge.mysql.com/wiki/MySQL_University
• Upcoming MySQL University Sessions: http://forge.mysql.com/wiki/MySQL_University#Upcoming_Sessions
• Instructions for MySQL University Attendees: http://forge.mysql.com/wiki/Instructions_for_Attendees
• OpenSolaris Project home page: http://opensolaris.org/os/project/webstack/