You are here
In my Acquia 2010 retrospective, I promised to write a bit more about Acquia's product strategy. This blog post provides a high level view of the vision that we've been working towards for the last 3 years, and explains how Acquia can help simplify your web strategy.
The web: it's currently a mess
Ten years ago, the average organization had one website. Since then, doing business through the web has become more complex and have introduced a diverse set of needs. If you're like most organizations the number of sites you have is large and continues to grow at a rapid clip.
For most organizations, one tool could not historically get the job done, so they kept multiple tools in their toolbox – whether they intended to or not. The situation can be quite a mess, and is unfortunately a common scenario in many enterprises.
Each site has unique needs
Most of these sites are vastly different in terms of scale, functionality, complexity and longevity. Some sites are under continuous development while other sites are only around for a couple of weeks or months. Some of the websites are owned by the company's IT department and hosted internally, while other websites may be owned by their marketing department and hosted externally. As a result, the level of investment and the time to market requirements are usually very different.
Standardize on Drupal to save costs
CIOs – facing cost-cutting pressures and the need to streamline their resources – are now addressing the reality of running twenty different content management systems on twenty different stack configurations as an expensive, unnecessary burden for the organization. They have always known that there were cost savings to be made if they standardize on a single platform, but have never felt the confidence in a single platform to suit all of their needs across their organization.
Drupal has the required features to accomplish this today. This is more than a vision – it is reality. Every day, more organizations are standardizing on Drupal.
By standardizing on Drupal, organizations can reduce training costs, reduce maintenance costs, streamline security, and optimize internal resources – all without sacrificing quality or requirements. Standardizing on Drupal certainly doesn't mean every single system needs to be Drupal. Even going from 20 different systems to 10 or to 5 different systems still translates to dramatic cost savings. It goes without saying that you need to be smart about what makes sense to standardize on Drupal, and what not to standardize on Drupal. With our vast community of contributors, Drupal continues to become better and better and the feasibility for an organization to standardize on Drupal continues to improve over time.
Drupal distributions help adoption
Drupal Commons is a Drupal distribution for social business software; it provides organizations a complete solution for forming collaborative communities. Similarly, Open Publish is a Drupal distribution optimized for news publishing. Acquia sees expansion of distributions as critically important to the future growth of Drupal. With that, we are acting as a software publishers for these and other distributions developed by partners within the Drupal community; supporting the marketing, promotion, support, and ongoing development of distributions to extend the capability of the companies who have incubated these incredible products.
Add the Acquia Network for support and cloud services
To help organizations adopt and standardize on Drupal, we created the Acquia Network to provide a suite of Drupal support, knowledge, and web development and maintenance tools to help build, manage and extend Drupal websites.
The Acquia Network is your connection to a team of Drupal experts, available 24x7, and backed by Acquia's engineering and professional services team. As an Acquia Network subscriber, you can submit help tickets, search our knowledge base and contribute in our subscriber forums.
The Acquia Network also provides you access to a number of cloud-based services. Services like heartbeat monitoring, software update management, and soon to be released integration with New Relic provide visibility into your site's performance and help with site management. Other services, like Acquia Search and Mollom, extend the functional capabilities of your sites.
We are in the middle of a massive redesign of the Acquia Network and many of the services you use through the Acquia Network today (including the Acquia Library, a broad collection of tips, tricks, how-to's, and resources for Drupal developers and site owners). Through the Acquia Network you will soon have the ability to easily access a growing list of third-party services, with many available at no additional charge. We already offer many third-party services (e.g. Mollom for spam filtering, New Relic for application profiling, etc), but we'll soon be opening up the Acquia Network as a ‘service delivery platform' and marketplace for additional services. In the works for release over the next few months are mobile design tools from Mobify, analytics, video services, marketing tools, and more.
Interested in adding your service to the Acquia Network? In the future, we will roll out APIs and infrastructure (e.g. billing) to enable other organizations to deliver their cloud-services to any Drupal site through the Acquia Network.
Add Acquia Hosting, a Drupal Platform-as-a-Service
For large websites that require custom code, high availability, on-demand elasticity or release management tools (i.e. staging and production workflows), we recommend Acquia Hosting, our Drupal-platform-as-a-service (Drupal PaaS).
Acquia Hosting is an extension of the Acquia Network, so if you need help scaling your site or debugging a problem, Acquia Client Advisors are always available to help. Through the Acquia Network, we also provide a number of Acquia Hosting specific e-services, including backups, database rollbacks, staging environments, version control for code management, and more.
Going forward you can expect even more developer tools and self-service tools to be added to Acquia Hosting, as well as more critical features for large scale sites, including improved security and code workflow options.
Add Drupal Gardens for rapid micro-site development
All sites are different. Not all your organization's website need the scale, functionality, complexity or longevity of your most important websites. A lot of times you have smaller sites that you may want to roll-out quickly, preferably without having to involve IT.
For that, we built Drupal Gardens, a Drupal-as-a-service platform that makes building Drupal websites as simple as point and click. Built on Drupal 7, Drupal Gardens brings the freedom and innovation you expect from open source without having to worry about installing, hosting or upgrading your Drupal site.
Our mission for Drupal Gardens is to allow site builders to go from design to online in minutes instead of days or weeks. To help, we provide an ever-growing library of site templates and themes to start from. We believe it will be the best platform for your smaller sites that complement your primary web properties.
For organizations that need to manage tens, if not hundreds, of small websites, we're building ‘Enterprise Drupal Gardens'. It provides site provisioning, site management, single sign-on, multi-site dashboards and organization wide templates and themes to maintain consistent branding.
Host your own sites, if you prefer
One of the biggest advantages of using Open Source software is that there are no limits to how you use the software. Some organizations prefer to host some of their own sites. The Acquia Network is able to plug in into your site, regardless of where it is hosted.
No lock in with "Open SaaS"
Almost all Software as a Service (SaaS) providers employ a proprietary model – they might allow you to export your data, but they usually don't allow you to export the underlying code. Users of Drupal Gardens are able to export their Drupal Gardens site – the code, the theme and data – and move of the platform to any Drupal hosting environment. By doing so, we provide people an easy on-ramp but we allow them to grow beyond the capabilities of Drupal Gardens without locking them in.
We call this "Open SaaS" or Software as a Service done right based on Open Source principles – it offers a much more secure and low-cost alternative to proprietary counterparts.
I've highlighted some of our key products and services in this blog post and will bring you a more detailed white paper focusing on Acquia's vision. Stay tuned!
To celebrate Drupal's tenth anniversary and the release of Drupal 7, I have decided to go on a Drupal tour, to celebrate, educate and spread the word on all things Drupal. I'm kicking-off my Drupal tour with a trip to Australia.
It's important for me to meet with other community leaders around the globe and promote Drupal. While down under I will be meeting with Drupalistas and non-Drupalistas, Acquia customers and partners, press and analysts. My goal is three-fold: (1) to promote Drupal, (2) to gain insight from users and prospects on the choices they make when it comes to choosing a web platform and building websites, and (3) to figure out how to further improve Drupal.
If you would like to meet to discuss Drupal, community building, web platforms, photography or anything else please let me know! I am currently in Brisbane (a little tired from the flight), I look forward to meeting you Down Under.
Here is where I will be and when:
- 22-23 January – Brisbane: I'll be at Drupal Downunder.
- 24-25 January – Melbourne: there is a Drupal meet-up scheduled on January 24th at 6pm in the Belgian Beer Café Eureka.
- 26-27 January – Sydney: there is a Drupal meet-up scheduled on January 27th at 6pm in the The Lord Nelson Brewery Hotel.
For more details, keep an eye on the Drupal.org Australia group, my Twitter account and this blog. To schedule time with me please contact Laurie Vertuccio and Matt Ackley; they help manage my schedule while I am traveling. Looking forward to meet!
Yesterday I shared my 2010 retrospective on Drupal along with some predictions for the new year. Today, I want to recap Acquia's accomplishments in 2010, just like I did last year with my 2009 Acquia retrospective.
It doesn't always feel like it, but Acquia is still a very young company; 2010 was only Acquia's second full year in business (i.e. revenue-bearing year), but for a young company 2010 has been nothing short of remarkable. Our business grew by more than 400% and we went from 35 to 80 full-time employees. Drupal Gardens grew from 0 to 30,000 sites, we added over 100 large hosting customers to Acquia Hosting, and our subscription business has over 600 customers. Our client advisors solved more than 6,000 support tickets, and our hosting team now manages 500+ servers, up from 100 servers at the beginning of the year. Together with our partners, we hosted more than 40 webinars in 2010. 2010 is also the year were we started to see some great successes in our partner program. Throughout the year, we got coverage in the New York Times, the Boston Globe, Forbes, Techcrunch, Mashable and more.
We beat our wildest expectations. Acquia is now one of the fastest growing start-ups in Boston. As a reward for exceeding our stretch goals, we're flying the entire company to Puerto Rico to celebrate. At the beginning of 2010, people doubted we'd even be able to get off of the ground, but by all accounts we're now soaring.
For me, a startup is a search for a scalable, repeatable business model. 2010 is the year where we arrived at several scalable, repeatable business models and as a result things started to really accelerate. In the summer of 2010 I moved to Boston so I could spend more face-to-face time with the team. By the fall of 2010 it was time to put the pedal to the metal and so we decided to raise additional capital. Much of the new capital will be used to help grow Drupal, to extend and improve our product offerings, and to grow our sales and marketing engine. In early 2011, Acquia will also expand to Europe.
I'm also particularly proud of Acquia's contributions to Drupal. We organized many code sprints, dedicated several of our best developers to Drupal 7, organized 4 free Drupal Business Summits to help promote Drupal in the enterprise, helped with the drupal.org redesign work, helped with the Drupal 7 upgrade and UX improvements of several contributed modules such as Media module and Webform module, created an open source social business software solution (Drupal Commons), and much more. The list goes on and on. Since Acquia's interests are so aligned with Drupal's, in everything we do, we try to raise the tide for the Drupal community at large. I'm proud of this because it is not trivial for a small company our size and stage.
Building a company is hard work and never without challenges. Fortunately, we have different challenges now than we had at the beginning of the 2010. When the first Acquia Network subscription renewals kicked in at the beginning of the year, renewal rates were below expectations. Today, our renewal rates are exceeding our expectations. Early in 2010, the rate of change of Drupal 7 APIs and number of critical bugs slowed down our progress on Drupal Gardens considerably. Today, Drupal 7 is almost ready to be released.
Going into 2011, there are two things impacting Acquia's future that still concern me; (1) the scarcity of great Drupal talent and (2) Drupal's growth. The demand for Drupal experts continues to be much larger than the supply -- it limits the adoption of Drupal by our customers, the growth of our partners, as well as our own ability to hire Drupal talent. Fortunately, it is not unusual in a fast growing segment and the community is launching many training initiatives to combat this scarcity. Together with our partners, we delivered 30+ training classes worldwide in 2010. It is still something that warrants further attention. Regarding Drupal's growth, it's great that we power 1% of the web, but considering the overall growth of web sites, we have to dramatically increase the number of sites being built just to even keep a 1% share, and we shouldn't settle for even that.
In general, I'm very optimistic about Acquia's future in 2011. In fact, I'm much more optimistic about 2011 than I was about 2010. The wind is blowing in the right direction. Cloud computing and Software as a Service (SaaS) continues to be on the rise. According to IDC, cloud computing will be a $55 billion USD market by 2014. I believe cloud computing and SaaS could be two of the most important changes in the history of computing -- it fundamentally changes how both small and large organizations operate. If they do, we made the right decisions three years ago. I expect that by the end of 2011, Drupal Gardens (SaaS) and Acquia Hosting (PaaS) will take off big time. Open Source adoption continues to become more mainstream too. For example, at the current rate, Red Hat will be a $1 billion USD revenue company in 2011, a milestone that very few software companies ever reach, and certainly one no open source company has yet to accomplish. It's good news for all of us in the Open Source business.
In all, 2010 was a great year for Acquia and Drupal, and 2011 promises to be even better. In the next week or so, I'll provide more insight into Acquia's product strategy and the vision we've been working towards since Acquia's founding three years ago. If you're interested in our plans for 2011, keep an eye out for that blog post. That said, expect us to invest heavily in Acquia Hosting (e.g. additional self-service tools, friction-less release management and lifecycle management capabilities, etc), the Acquia Network (e.g. visual refresh, new services, marketplace for third-party services, etc) and Drupal Gardens (e.g. Views, partner tools, etc).
Needless to say, Acquia wouldn't have made it this far without our customers, our partners and our friends. We wouldn't be much of a company without you. Thank you for 2010!
At Acquia, we spent a lot of time improving the Webform module, one of the top 10 most popular Drupal modules, as well as the Form Builder module, a companion module that provides an improved user interface for the Webform module. The Webform module and the Form Builder module allow people to create custom forms such as contact forms, online surveys and more.
Both modules are maintained by Nate 'quicksketch' Haug, one of the top Drupal contributors. Like anything Nate does, the modules are amazingly powerful and have great code quality. We wanted to add support for creating custom forms to Drupal Gardens and believed that the Webform and Form Builder modules were the right way to go. No need to reinvent the wheel.
Before making Webform and Form Builder available as part of Drupal Gardens, we wanted to try and see if we could make Webforms easier to use, without making it less powerful. We spent about 200 hours to explore various different design and interaction models. We used both paper prototypes and working prototypes to conduct usability tests, and used these to drive further optimizations. After we felt good about the direction, we ran it by quicksketch. With quicksketch's guidance, we helped upgrade both modules from Drupal 6 to Drupal 7, and implemented the new user interface on top of that. The new drag-and-drop interface puts some things in different locations on the page and has a number of different interaction patterns compared to the old user interface. To do so, we wrote a couple of modules that add our user interface on top of the Webform and Form Builder modules. It is layered like a stack: Webform → Form Builder → Alternate UI.
Fast forward 25 person-weeks, and we've now rolled out our improved user interface as part of the latest Drupal Gardens release. To see how it looks, take a look at the video below or create a free Drupal Gardens website if you prefer.
We're contributing everything back to the community -- some things we've already contributed back, other things we're in the process to. We're also helping to back port some changes to Drupal 6, even though we don't need them for Drupal Gardens. With these contributions, everyone in the community can benefit.
The new user interface is an incredible achievement that a lot of people deserve recognition for, including quicksketch who spent many years of getting Webform and Form Builder modules to where we were able to use them as a starting point.
I'm pretty excited about this user interface, and would love your feedback and suggestions. What do you think?
Update on January 10th, 2011: the Webform Alternate UI module is now available on drupal.org. This module provides an alternate user interface for the Webform module, allowing you to create and edit forms from within an easy-to-use form building tool.
I recently had the pleasure of serving as a thesis advisor on a work by Marc Seeger, who was completing a portion of his requirements for a Master of Science in Computer Science and Media at Stuttgart Media University. Marc's thesis was titled "Building blocks of a scalable web crawler".
Marc undertook a project for Acquia that I had originally started in 2006; a Drupal site crawler to catalog, as best as possible, the current distribution of Drupal sites across the web. That is a task for which there is no easy answer as Drupal can be downloaded and used free (in all senses of the word). The best way to find out how many Drupal sites exist, is to develop a crawler that crawls the entire web and that counts all the Drupal sites one by one.
With Marc's help, I was able to resurrect my crawler project. Marc spent 6 months working with me; 3 months were spent in Germany where Marc lives, and 3 months were spent in Boston where Acquia is based.
During that time, Marc explored suitable architectures for building out, collecting and managing website data on the order of many millions of domains. He examined different backend storage systems (Riak, Cassandra, MongoDB, Redis, CouchDB, Tokyo Cabinet, MySQL, Postgres, ...), contemplated the methods of collecting the data while simultaneously allowing search and access. As part of his work, Marc explored a variety of different database technologies, database schemas and configurations, and experimented with various configurations of Amazon's Elastic Cloud hardware (EC2). Issues common to any large deployment were investigated and analyzed in detail, including HTTP persistent connections, data locking and concurrency control, caching, and performant solutions for large-scale searches. HTTP redirects, DNS issues -- his thesis covers it all, at least in terms of how each of these items impacted the search for an acceptable algorithm.
The crawler has been up and running for a number of months now, and investigated about 100 million domain names. Now we crawled about 100 million domain names, I plan to start publishing the results.
Marc's work is available in PDF from his blog post, and it's a good read, even if I'm slightly biased. Thanks for the great work, Marc! Time to look for a couple new thesis projects, and thesis students that want to work with me for a few months. Ideas welcome!
During the past month, I've been trying New Relic on my personal blog. New Relic is a performance management tool. It can help to monitor, debug and optimize a site. It includes features like slow page request analysis, slow database query analysis, error tracking, scalability analysis, performance alerts, weekly e-mail reports, up-time monitoring and even very specialized features like Apache Solr profiling. It's a bundle of developer goodies that can be used on live production websites.
I'm a bit of a profiling geek. In my previous life, I spent a lot of time working on production profiling and performance optimization of Java applications. So when New Relic recently announced that they're working on support for PHP applications, I wanted to give it a try.
We began testing New Relic when the PHP version was still in beta. We believe it can make for a great service to add to Acquia Hosting and the Acquia Network. My site is hosted on Acquia Hosting which is why I have been testing it on my site. So far the testing has been good. We've helped New Relic fix a number of bugs during the beta test period, and in return New Relic has helped us to discover a performance problem in one of our deployment scripts on Acquia Hosting. Proof that New Relic is useful!
Now that we are past internal testing, I am excited to say that we will soon be bundling New Relic into the Acquia Network. Every Acquia customer will soon get access to a premium version of New Relic's monitoring tools at no additional charge -- whether you are hosting with us or not. Expect more detail from us soon on how to access New Relic as a subscriber.
New Relic requires a small 'agent' to be installed on your web server. The agent hooks into the PHP interpreter and sends the relevant information to a back-end for analysis and visualization. Because it hooks into the PHP interpreter, it can provide that deep, code-level visibility that is useful when debugging a performance problem. The New Relic agent also adds extra Drupal specific instrumentation -- and will probably add more over time.
I've only used it on my personal site, which currently runs on a regular Drupal 6. However, I'm quite keen to unleash it on a Drupal 7 installation to see what we can learn. In the mean time, I'm including some screenshots of what my personal blog looks like according to New Relic. If you're interested in improving the performance of your site and are a profiling geek like me, you should give New Relic a try.
New Relic uses <a href="http://en.wikipedia.org/wiki/Apdex">Apdex</a>, an industry standard for measuring the satisfaction of a user of an application or service.
New Relic conveniently separates database performance from PHP performance. On a busy system, that makes it easy to pinpoint bottlenecks.
New Relic tries to annotate performance problems to 'controllers' rather than to specific URLs. Thus, it automatically extracts 'Drupal page callbacks'. This is nice because when an application has thousands of unique URLs (<code>/article/11/19/why-mysql-is-cool</code> and <code>/article/11/19/postgres-is-cool</code> and so on) that are all handled by the same controller (e.g. <code>node_page_view()</code>).
This graph shows that most of my database time is spent reading and writing to the <code>accesslog</code> MySQL table. By disabling the access log feature in Drupal, I could reduce my database load roughly in half.
Things are heating up in the Drupal world as both CommerceGuys and SubHub raised venture capital money. We're still waiting for an official announcement, but word on the street is that CommerceGuys raised around 1 million euros to develop a number of e-commerce products and services for Drupal. SubHub raised more than 1.2 million euros to date to develop SubHubLite, a hosted service for Drupal 7 comparable to Drupal Gardens and Buzzr. In addition to CommerceGuys and SubHub, I know of at least two other Drupal companies that are in the process of raising money from investors ...
Selling a product has more upside potential than selling consulting and professional services which you can only bill by the hour. However, it is difficult to bootstrap a product based business without a major investment of funds -- usually from outside investors. I've seen many try and fail. In almost all cases, it failed because the company was under-capitalized. It takes a lot of resources to create a successful and defensible product. Furthermore, people tend to forget about sales and marketing. It's not enough to build your product -- you have to bring it to market as well. That is not trivial either.
I don't have a rich uncle, so I would not have been able to co-found Acquia without venture capital financing. We decided that we wanted to focus on being a support and software product company with a strong partner eco-system. Starting Acquia wasn't the easiest route for me, but looking back at the past three years of Acquia, I believe that I made the right decision. Based on how much Acquia has contributed to Drupal and what it has enabled me to do, I like to believe it would have been a loss if I had taken a more conventional route -- or had I decided to continue to work on Drupal as a hobby project.
It's refreshing to see that more and more Drupal companies aspire to become successful product companies and that they are seeking venture capital. I always admired the Ruby on Rails community for its seemingly entrepreneurial attitude. I'm glad to see more of it in the Drupal community as well. There is a good deal of fear surrounding venture capitalists but if Drupal is going to grow, we should expect to see more venture-backed companies building Drupal products. Venture capital financing can be good, especially if these companies give back to Drupal and if they build products and services that make our life easier. We all benefit from that.