Software Architecture for Developers

Search results

"tag:"performance""


Title and summary Date/time
1
Jitter
On CTA we often talk about non-functional requirements and how this can drive the architecture of a system. Most of these cover issues of desired response time and capacity (latency, throughput, storage etc) but I believe that Jitter is a metric which is ...
06-Sep-2011
09:02:41
2
Stating the obvious
If you've watched A developer's guide to load testing, you will have seen the graph below already. It shows the results from load testing a website written in .NET with the Apache JMeter load testing tool. Along the bottom of the graph are the actions ...
16-Jun-2009
15:08:33
3
Using new technology will make it faster
I heard an interesting throwaway comment recently that I thought I'd share. To paraphrase... The system is being rewritten with new technology, so it won't be slower than what we have now. While it's true that new and updated technology *can* ...
15-May-2009
11:57:11
4
Discussion from the May 2008 user group
Although this happened a few months ago, we recorded the discussion that followed our London user group where Moudud Ahmed talked about building a high volume, low latency system in Java. Here are some of the topics that we talked about. Performance ...
30-Aug-2008
07:57:27
5
Who should own the non-functional tests?
This is a follow-up to a post entitled Performance tuning Java systems that I made last year, which talked about some performance testing that I was doing for a customer. Last week, I went back to the same customer to make some small tweaks to the test ...
07-Jul-2008
11:03:00
6
NFRs for system replacements
As software architects, we tend to write about non-functional requirements a lot; particularly about how they should be defined and challenged because of the influence they have. One of the reasons for talking about NFRs a lot is that, in the majority, ...
28-May-2008
11:35:00
7
Scalability Principles
At the simplest level, scalability is about doing more of something. This could be responding to more user requests, executing more work or handling more data. While designing software has its complexities, making that software capable of doing lots of ...
21-May-2008
14:12:25
8
London User Group - May 2008
Here are the details of the May London User Group. Title : Building a high volume, low latency system in Java Summary : This session will provide some insight into the architecture, design and development of a greenfield high volume, low latency ...
25-Apr-2008
14:30:52
9
Podcast #2 : QCon revisited
As promised the 2nd CTA podcast is a roundtable discussion between some of the CTA contributors - namely Simon Brown, Sam Dalton and Kevin Seal. In this podcast we discuss some of the themes emerging from the recent QCon conference held in London and our ...
25-Mar-2008
10:23:20
10
Performance tuning Java systems
One of my current projects involves me performance testing a third party Java system. In essence, it's a distributed/n-tier Java EE web application and we're hitting it with a high simulated load thanks to Apache JMeter. One of the things we found is ...
05-Nov-2007
12:23:34
11
Separating the non-functionals
I was recently involved in a discussion where we were talking about the best way to increase the scalability of a software system, which is essentially a Java EE web application. The most obvious way to do this is to horizontally scale-out the ...
02-Oct-2007
12:07:00
12
Scaling is much more than software
From Scaling is much more than software comes this great little snippet about one of the ways to solve problems with your architecture. What was the solution? Re-evaluating the business logic and requirements with the customer. Whenever I'm talking ...
24-Jan-2006
22:21:38