> The vast majority of the BBC’s webpages are rendered on AWS, using React. React’s isomorphic nature allows us to render the pages server-side (for best performance) and then do some further updates client-side.
> Increasingly, the rendering happens on AWS Lambda. About 2,000 lambdas run every second to create the BBC website; a number that we expect to grow
I picked the first job that came up [1] and seems like at least one team is using Delphi with Oracle for the database. But the BBC isn't exactly small, so I'm not surprised there's a range.
I'm guessing the main part of the content (for example the news story) is rendered server side, the client-side adds any personalisation if the user is logged in etc and adds panels for 'related'/most liked/read more news stories etc.
This means the content can be both crawled for SEO and cached (there's cache hit and fastly headers in their responses)
That's the piece of information I miss in a lot of those stories. What happened X years later? We all love reading about strange projects, but it's not until someone sits down and writes a blog post about some old, custom system that you get the important insights (X was good, Y didn't work because reasons and nobody ever understood Z).
Sadly so. Still Perl around the organisation though in internal systems from that era which continue to work and still in daily use for producing news if nothing else.
https://www.bbc.co.uk/blogs/internet/entries/8673fe2a-e876-4...
https://static.files.bbci.co.uk/core/storybook/index.html?pa...
> The vast majority of the BBC’s webpages are rendered on AWS, using React. React’s isomorphic nature allows us to render the pages server-side (for best performance) and then do some further updates client-side.
> Increasingly, the rendering happens on AWS Lambda. About 2,000 lambdas run every second to create the BBC website; a number that we expect to grow