Web-Scale System Architecture

what are the lessons learned in building big systems? what if we gathered some system architects in a room to share their insights? that's the goal of this event - we have Jerome O'Flaherty of Brite:bill and Morgen Jorgensen of OpenJaw Technologies lined up to share their insights on the 11th of July in the Gibson Hotel at 6pm.

Organised by brite:bill and OpenJaw Technologies in association with Enterprise Ireland

Tickets

Additional Information

some of the challenges faced by the speakers:

Jerome says: "a typical Telco has maybe 3-4 'Bill runs' a month (of millions of bills) which typically finish during the night. To maximise the time allowed for customers to pay these bills, our customers require that we have them 'ingested' and they are ready for presentation before the following morning. Typically, we look after the notification of the bill availability which itself causes a spike in target to the Website. So, say 4 times a month we have a 'backend spike of activity for 3-4 hours to process something in the range of a millions, followed by a large spike in internet / mobile traffic later that same day (as people check out their bills). We provide our product as both a hosted solution (on AWS) and as an on site deployed solution which itself causes challenges with this 'spiky' nature of the business we are in, e.g. how to architect a product which uses the best of breed Amazon AWS tools/environment, while at the same time supports customers' own infrastructure."

Morgen says: "Many of our customers have large transaction volumes, and scalability is obviously an issue. One of my main challenges over the last few years has been to improve the scalability of the platform - with limited engineering resources and with a very large and complex code base (over one million lines of code). Our approach to scalability is thus quite different from what it would have been if we were building an internet scalable system from scratch. What I would like to share is our experiences in this process, and I think this will offer a different perspective than most presentations I've attended on scalability. It will be more on teaching an old dog new tricks, rather than building the optimal solution."