You are here
Drupal continues to rack up successes among large developer communities, with x.commerce joining Twitter, which made the move last month. X.commerce is a new division of PayPal that serves as an open, central meeting place for over 700,000 developers for eBay, PayPal, Magento, and other eBay properties.
These communities join those of Brightcove, Symantec, DivX -- and, of course, Drupal. All told, that's millions of developers relying on Drupal-run sites for coding tips, product info, and idea exchange.
x.commerce's communities were formerly run on Jive, a proprietary package. Through Acquia, eBay engaged VML to create the site, with additional consulting by Cyrve (now part of Acquia) to migrate data. Acquia provided a Technical Account Manager (TAM), who helped coordinate resources to put the site into production and will be on call as it grows.
Like many developer sites, x.commerce centers around its documentation and its communities. The latter are a model of social networking at its best, in the service of a question-and-answer format. Developers help each other by responding directly to questions, either publicly or through private email; vote on questions (and answers) to highlight those of importance; promote conversations through other social sites such as Facebook; and bookmark discussions to form personal collections. The results are evident in the enormous level of activity within the forums (which, by the way, are built on Organic Groups).
This project is an excellent example of how open-source software drives innovation. Under Jive, eBay wasn't able to develop features that it needed. If eBay needed to do something that wasn't in Jive's roadmap, that was just too bad. Drupal, of course, allows them to create whatever they need, or developers outside the company to do it. That jibes well with x.commerce's ethos of open development, as is demonstrated by the extensive APIs it provides for eBay and PayPal, and the freedom the company allows its developers. I believe that their openness is a key factor to their success -- there are over 4,500 apps on Magento alone -- and that their move to Drupal will allow them to grow at the speed of their community.
A number of concerns have been voiced from the community about the substantial growth Acquia has achieved since its inception, the number of key contributors who are now employed by Acquia, and the subsequent influence that this allows Acquia to have on the project.
While some of these concerns have validity, I also think there is also a fair share of FUD (fear, uncertainty and doubt) being spread. So, let's clear up a few points.
In terms of growth, Acquia currently employs about 150 people. However, fewer than half of Acquia's employees work directly with Drupal; the majority of Acquians work in sales, marketing, hosting operations, finance, HR, etc. In a way, this makes us smaller than Phase2, Node One, Forum One, Propeople, Capgemini, and dozens of other shops in terms of Drupal staff. We have a different mix than most other Drupal shops.
In terms of influence, Acquia employs fewer than 10% of the contributors to Drupal core. Admittedly, on a "per Drupalist" basis, Acquia probably contributes significantly more code and magnitudes more dollars to the Drupal community than any other organization. We are investing in expanding the Drupal community through major learning initiatives. We sponsor more DrupalCamps, where new people are introduced to Drupal, than anyone. We sponsor more interns than perhaps the rest of the community combined, where high school and university students learn how to build a career in Drupal. Not to mention we contribute a lot of code.
I like to believe that is a great thing for Drupal and that not doing so would be a big loss for all of us.
It certainly helps to have venture capital money when making investments in the community, but it is not a magic bullet either. It is not free money. I've explicitly chosen to give up part of my equity in Acquia in exchange for money so that I can invest it back into the Drupal community to help Drupal advance.
I understand that my involvement with Acquia is tricky because its well-being is intertwined with Drupal's. But I help drive the decision-making process at Acquia, and I set those directions with the best interests of Drupal in mind at all times. Making Drupal successful and Drupal's well-being is my primary concern, regardless of the "hat" that I wear. We want Drupal to power as many sites as possible, both small and large. We want lots of Drupal entrepreneurs to thrive in a growing ecosystem. If you look at Acquia's actions, you'll see tons of contributions here. We sponsor DrupalCamps and DrupalCons, and pay employees to improve Drupal modules and themes.
Recently, our acquisitions of Cyrve and GVS have been a topic of debate. I'd like to point out that acquisitions are a two-way street: they don't happen unless both parties are really excited about it. Contributors come to Acquia for different reasons. Sometimes they would rather hand things like business development, sales, and support off to someone more set up for that, so they can stay focused on doing things they really enjoy. Others thrive more in a larger team of smart people working on interesting things, rather than toiling away on their own. Still others have put in huge amounts of their own personal time over a sustained period to help improve Drupal, often at great personal sacrifice, and are looking for an arrangement that makes this commitment to the project more sustainable. Painting these contributors as "bad guys", or the company who allows them to pursue a career that they love as "bad guys", is not healthy for our community, or the individuals involved.
The clear solution to the influence concern is to grow our community, particularly our contributor community. If more individuals and Drupal shops are contributing in a bigger way, this mitigates the risks of any organization, Acquia or otherwise, from exerting too much influence on the overall project.
So as a community, we need to re-frame this question. We need to be asking ourselves: (1) What can we do to grow the community? (2) Why aren't more people who depend on Drupal contributing to it? and (3) How can we encourage Drupal shops to contribute back?
As followers of this blog, you might have read that Acquia acquired two Drupal companies; security specialist Growing Venture Solutions and migration expert Cyrve. We wanted to do these acquisitions because they create a win-win-win situation; it is beneficial for the Drupal community, our partners and our customers. I personally championed and led those acquisitions so I want to take a moment to explain why.
How do these acquisitions affect Drupal?
I believe these acquisitions benefit Drupal by expanding its reach. Migration from legacy systems (like Vignette, RedDot and Interwoven) and from expensive enterprise solutions (like Jive Software, Adobe CQ5 and Sitecore) represents some of Drupal's biggest opportunities -- if not the biggest. My hope is that by acquiring and expanding Cyrve, we'll be able to bring more projects into Drupal. That leads to more site building work, more contributed module patches, and more people talking about their Drupal successes.
Similarly, Acquia's involvement in GVS gives it the resources it needs to pursue new security initiatives that will make Drupal more attractive to everybody. As always, we'll continue to return many developments to the community.
How do these acquisitions affect Acquia's customers?
Acquia's customer base has been growing rapidly, both in number and size. We plan to use these acquisitions to provide our customers with more product options and more experts. We will:
- Offer automated, self-service security tools as part of the Acquia Network.
- Integrate the services of both companies into our Professional Services group. We'll be expanding our security and migration teams, both by training existing consultants and by bringing new employees into the fold.
- Incorporate their curricula into our existing materials so we can help train many more experts on Drupal security and Drupal migrations.
All of these are good for Acquia's customers. But they're also good for the Drupal community at large: we need more migrations and security experts in the community.
How do these acquisitions affect Acquia's partners?
Many of our partners build Drupal websites, but few have in-house security or migration expertise. With Cyrve and GVS, we can all approach joint customers with more-complete offerings. This enables our partners to go after bigger projects.
In short, I believe these acquisitions are beneficial for Drupal, our partners and our customers. However, some people have expressed concerns that, with these acquisitions, Acquia is sucking up a lot of the Drupal talent. Because that concern is not limited to these acquisitions, I've decided to address that in a separate blog post: Does Acquia suck up all the Drupal talent?.
I'm thrilled to announce that Acquia has received $15 million in its fourth round of funding -- that is about twice as much as any of our earlier rounds (series A, series B, series C). Our previous investors affirmed their confidence by participating in this round; they were joined by Tenaya Capital, which has roots in both the San Francisco Bay Area and our home turf of Boston. Tenaya brings more than money: Tenaya's Brian Paul will join our Board of Directors as well.
This is an incredibly exciting time to be at Acquia. Since the series C last November, our staff size has almost doubled, from 70 to 130. We're bursting out of our office space and will be moving to a bigger, 35,000 square feet office soon. We needed all those people to service our thousand-plus enterprise customers, and to plan for the future with new initiatives, such as Dev Cloud and the newly revised Acquia Network. We broke revenue records in Q1 and Q2 this year, following an extremely successful 2010.
Fundraising rounds usually occur either when a company is doing very well, or when it's doing very badly. When it's doing well, investors want to get in on the action to score big. When it's doing badly, current investors hope to turn it around to avoid losing everything they'd already put into it. By all measures, Acquia is doing very well, and this round of funding only confirms that. This is what is called a "growth round", with the money directed toward two objectives:
- Increase sales and marketing, particularly outside the U.S.. It's clear that there are tremendous opportunities for enterprise Drupal outside of the U.S., as our partners prove every day. We'll start by focusing on Western Europe, but are already planning expansion into Asia.
- Acquire talent and products that complement Acquia's own. These "acquia-sitions" (as we jokingly call them) will continue to beef up our staff, expand our product offerings, and respond to requests we've gotten over our three and a half years in business.
Acquia's growth is a testament to the growth of Drupal; we'll continue to give back to the Drupal community in everything what we do. Acquia wouldn't have made it this far without our customers, our partners, our employees and our friends. Thank you!
If you're a regular visitor to the Acquia website, you were probably surprised at what you saw the last time you stopped by. Aside from our new company logo, the whole site has a very different look, navigation, and main message points from a few days ago. This is the result of a project that has kept our marketing teams busy for the last few months.
Although this design represents the most profound website changes in the company's history, it's not the first time we've done this. Here is what our initial website looked like in 2008:
Acquia.com in March 2008
... and in 2009:
Acquia.com in July 2009
... and until this week:
Finally, here it is today:
Aside from obvious visual changes, we've tried to explain Acquia's products and services better. The experiences of the last three and a half years have shown us what people want from us, what we do well, and how to best match the two. I don't think we could have made our site so clear a year ago, and can only imagine what refinements future revisions will bring.
This is a big deal for Drupal -- it's not every day that one of the hottest technology start-ups switches one of its sites to Drupal. At Acquia, we have been working with Twitter on this site but couldn't talk about it for the longest time. I'm glad we finally can because it's a great use case for Drupal.
Twitter has 750,000 developers who have created nearly a million apps, making 13 billion API calls per day. Those are some astonishing figures! A population that big requires a lot, as we in the Drupal community know.
Fortunately, Drupal handles big communities well. Developer communities have been quick to recognize that and have adopted Drupal at a remarkable rate. Among them are the Brightcove developer community, Symantec Connect's developer community, DivX's developer community, and many more. Drupal's own website, Drupal.org, has more than a million registered users and is one of the largest developer communities in the world. Needless to say, drupal.org runs on Drupal.
Twitter is a curious case. On its face Twitter only has to do one thing -- deliver short messages in one-to-many mode. But its published APIs (and enormous popularity) have led developers to create a lot of interesting things. That's also why Drupal sites can publish to Twitter, and vice versa, via the Twitter module.
In the end, that is what good developer communities are all about. Developers are like molecules, vibrating with intensity and vigor. Their individual movements can seem random. But together in the right environment, they can form waves -- or snowflakes. Nurturing a community in which both are possible is the challenge every software project faces; I'd like to think that Twitter, through Drupal, is creating the right environment.
Anyone who runs a high-availability Drupal site knows about Varnish, the open-source HTTP reverse-proxy server. Varnish intercepts requests before they hit the web server and delivers relevant information that it finds in its cache, resulting in lower loads and radically faster pages.
Because we love Varnish, Acquia is organizing and sponsoring two Varnish release parties. One is in Boston, at the Cambridge Brewing Company from 6:30 to 8:30pm; a second is in Portland at the Lucky Labrador Brewing Company starting at 6:00pm. Both are on Thursday, June 16th. See the Varnish 3.0 party page for parties at locations near you.
It's a great opportunity to meet fellow web geeks and have some good (free!) beer. I'll be at the Boston party, and look forward to seeing the local Varnish users!
Further details are on Varnish's web site. See you this Thursday!