drizzle-discuss team mailing list archive
Mailing list archive
Re: Drizzle for application developers?
Thank you very much for the very helpful feedback. It clarifies it very
well. (BTW, I have worked through the online version of the presentation
(which was very good, thanks!) I wish I could have been at your presentation
at Velocity though :) )
Your answer confirmed to me that we are still going to start using Drizzle
for our new project now. What we probably already would benefit from is
amongst others: thorough testing (I can gather from this discussion group
and elsewhere that testing is very important to drizzle developers), a
streamlined code-base (because you took out code that is not required for
the purposes of web applications and are you also refactoring and improving
existing code where required. ) and it is much easier to participate in the
community (and development). Also, as an "early adopter", we would already
benefit from learning and understanding how best to use and implement
On Fri, Jul 9, 2010 at 11:21 PM, Monty Taylor <mordred@xxxxxxxxxxxx> wrote:
> Thanks for coming, first of all.
> What I meant there (and obviously I need to rework this message) is that
> the ways in which we are _better_ than MySQL (or trying to be better) are
> focused on people building clouds. Things that would make building
> application on clouds (such as automagic sharding or the like) are still
> todo list items. So for your case, we're no worse than mysql, but we may not
> have added tons to make your life better yet.
> Does that clarify a bit? (Also, anyone feel free to disagree with me here)
> "Willem de Ru" <willemd@xxxxxxxxxxxxxx> wrote:
> >In Monty's presentation on Drizzle at the Velocity conference, he mentions
> >that "drizzle today" is for infrastructure providers and "drizzle
> >is for developers. I just want to get a sense of what this essentially
> >down to. We are SaaS application developers and we are keen to use drizzle
> >as our db back-end (even if drizzle is still in beta). Does Monty's
> >just mean that it would require a bit more effort/tweaking to set up on a
> >server than say mySQL, but that it is still viable to use. Or does it mean
> >we should rather wait another year or so before really seriously
> >drizzle as db.
> >Thanks for all the hard work and very interesting discussions here. It is
> >much appreciated!
> >Mailing list: https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss>
> >Post to : drizzle-discuss@xxxxxxxxxxxxxxxxxxx
> >Unsubscribe : https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss>
> >More help : https://help.launchpad.net/ListHelp
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.