Friday, 5 November 2010
A few weeks ago I visited the Future of Web Apps event in London. One of the most interesting sessions I attended was a talk on scalable architectures by Sandy Jen, the brains behind a popular service called Meebo (an instant messaging program) that was launched 5 years ago. In this blog post I wanted to recap on some of the key points in the session.
Sandy mentioned a few challenges that we need to cope with when building a website or web application. First of all, we need to make sure that the site is going to have the same user experience (UX) across all browsers and devices. Second, we need to take into consideration that the user might not have a stable Internet connection. Users also don't favour the idea of refreshing the page so utilising Ajax could provide a good investment from a UX point of view. Forcing users to download an external application to make our site enjoyable is also a thing of the past; therefore it is a good idea to avoid that approach. Finally we are still boxed in a browser: despite the browser's limitations, we still need to match our users' expectations.
Wednesday, 8 September 2010
This blog series discusses scalability from three distinct perspectives: people, processes and technology. If you haven't read the first and the second part of this series yet, we recommend you read them first before continuing with this post.
While scalability is an art more than a science, over time several sound architectural principles have emerged. Examples include designing for rollback or to be disabled, redundancy of all the components, embedded monitoring, asynchronous communication, stateless systems, etc. There isn't a perfect recipe that works for every project, but always keeping these concepts in mind and finding the right balance dramatically increases the chances of success.
Ga door met lezen van "Scalable Systems, Part 3: Technology"
Tuesday, 17 August 2010
This blog series discusses scalability from three distinct perspectives: people, processes and technology. If you haven't read the first part yet, we recommend you read it first before continuing with this post.
Processes are critical to scale. They cover and assist all the different stages of software development, from the early phases (planning, design), to implementation, to putting the software into production and maintaining it. Any activity is ultimately risky, and being able to understand the potential risks and gains is essential when growing your business.
When the user load is growing and adding more resources to the existing system is no longer enough, the first step usually consists of redesigning the system. As in every journey, it's good to know both the start and the destination first. So before starting any architecture or software redesign, you need to understand what the current state is. Calculating the headroom of your current system is a process that involves determining the current usage and the free capacity of each component, and measuring it against the expected growth. This will give you a better idea of the time remaining before service degradation or outages, as well as help identify the real bottlenecks of the current architecture.
Ga door met lezen van "Scalable Systems, Part 2: Processes"
Wednesday, 4 August 2010
In order to manage the success and popularity of a web site, it needs to be designed to cope with a growing number of users. Applications need to scale upwards to remain responsive during times of heavy load, and backwards to reduce TCO when costly resources are no longer needed. Our aim is to provide a timely and seamless user experience without needing to invest in a permanent platform ready for the biggest potential future traffic spike.
In this white paper, we will discuss horizontal scaling, or adding additional resources (typically servers) to an existing infrastructure and spreading the load of one or more of the subsystems out across them. Because of its "shared nothing" design philosophy, PHP excels at horizontal scaling. We'll only briefly cover vertical scaling (additional RAM, CPUs or hard disk space), as every system can benefit from having bigger servers to run on.
There are two main challenges to scaling applications horizontally:
1) Designing an application that can be scaled as and when the need arises. To do this requires some architectural planning of the system, using techniques such as:
- Breaking applications into a series of loosely-coupled subsystems tied together via APIs
- Horizontally scaling subsystems individually (as opposed to vertically scaling the entire application)
- Scaling the database by using techniques like replication, sharding or federation
2) Arriving at a system which can add and remove resources automatically.
Download this white paper to learn several strategies for horizontal scaling of PHP applications, as well as to understand the overhead required for each one. We'll also make some recommendations about the kinds of scenarios which render each strategy a useful platform choice.
Download now (free, but we ask you to leave your contact details)
Wednesday, 7 July 2010
In order to manage the success and popularity of a web site, it needs to be designed to cope with a growing number of users. A site designed to support 50 concurrent users can't serve thousands of simultaneous visitors without collapsing. Thus, the very success of a web site could also be the cause of its failure, if it is not able to sustain the sudden and exponential growth in number of users or requests.
A recent study by Computing & Double Take revealed that 83% of UK organisations admit downtime of several hours or more. Even if you manage to avoid a complete collapse, users will not stick around on a slow-loading site. The ability to grow (and shrink!) depending on need or availability thus becomes critical, directly affecting your revenue stream. A system that's able to cope with this changing demand is called scalable.
Tuesday, 16 February 2010
On March 2nd, we are organizing another PHP management seminar in The Netherlands. In one afternoon, we'll update IT managers, CIOs, CEOs, CTOs and (web) development managers on some of the latest developments in PHP development. Topics this year are:
- Service APIs; More and more applications are written using webservices, and in this session we'll show you why.
- Performance: As the internet presence of companies grows, performance is an area many people continue to struggle with.
- Cloud computing: In a few years time, we will all be working with clouds. Now is the time to prepare and learn what this means for your application development efforts.
- Make or Buy'; this eternal question deals with choosing between using off the shelf applications or building your own.
Monday, 21 December 2009
This weekend The Netherlands (and many other countries too, but for the purpose of example I'll stick to NL) experienced something that happens only every few years. We had up to 25 centimeters of snow, which is unusual for us, so it disrupts life significantly. On sunday, buses and trains were canceled, destinations became unreachable, and at Schiphol airport alone, over 700 people had to spent the night because it was impossible to get anywhere.
Snow continued to fall Sunday evening, so this morning most news outlets expected chaos in traffic. The Ibuildings Netherlands offices already advised all its staff to work from home on Monday, but not every company is able to tackle it that way, so the number one question for many people this morning was: "Will I be able to get to work?". The answer to the question should be simple: either trains and buses ride normally, they have delays, or they don't ride at all. Still, many of the Dutch public transport companies struggled to get that information across. Read on for an overview and an analysis, using the public transport companies of the Dutch major cities as an example of how important it is to do 'peak management'.
Ga door met lezen van "Disruptive events and information flow"
Thursday, 23 April 2009
About 2 months ago, Erik Snoeijs posted a story about the NU.nl backend, a project we did for the largest news site in The Netherlands.
Back then, we already planned to write a follow up post about the front-end technology. Where the back-end focuses on flexibility and ease of use for the Nu.nl editors, the front-end focuses completely on very high performance and getting the news out to the site's readers as quickly as possible.
Thursday, 12 February 2009
 It's long overdue seeing as the new site has been up for about two months now, but better late then never!
Somewhere in March of last year, we heard we might be doing the site NU.nl for ilse media. Readers not local to the Netherlands might not know it, but nu.nl is almost a concept in the Netherlands. It's the news site here, millions of people rely on it for their news throughout the day. So not very surprising we were all very excited about doing this.
Ga door met lezen van "NU.nl; the back-end"
Tuesday, 12 August 2008
Recently a colleague stated that in theory, caching could be considered 'evil'.
Now 'evil' is a very broad term which is used a lot in the IT community, but what does it really mean when we're talking about technical solutions?
I asked around, but couldn't find a clear cut definition, so I went searching...
Ga door met lezen van "The definition of evil"
|
Blog
