BBC Design & Engineering
medium.com/bbc-design-engineering · Company blog · on HN since 2017
The BBC's design and engineering teams write about moving BBC Online to the cloud, serverless, nanoservices, HTTP/2, and PWAs.
What HN saysHN commenters call its progressive web apps post a great write-up and link its serverless update, with one noting nanoservices no longer get mentioned.
41HN people shared it
6linked it in comments
41stories submitted
598story points
4 years agolast shared
2017people per year2026
Most-shared posts
- 1Moving BBC Online to the Cloud4 people · 120 points · first shared 2020 · 65 comments on HN
- 2Powering BBC Online with nanoservices3 people · 16 points · first shared 2017 · discussion on HN
- 3HTTP/2 is easy, just turn it on…3 people · 7 points · first shared 2017 · 1 comments on HN
- 4BBC Online – A Year with Serverless3 people · 6 points · first shared 2022 · discussion on HN
- 5How We Grow Junior Developers at the BBC2 people · 307 points · first shared 2017 · 159 comments on HN
- 6Shipping Progressive Web Apps everywhere2 people · 52 points · first shared 2020 · 8 comments on HN
- 7Looks Good To Me: Making code reviews better for remote-first teams2 people · 5 points · first shared 2021 · discussion on HN
- 8BBC Newsround, Nanoservices and Serverless2 people · 5 points · first shared 2018 · discussion on HN
- 9How the BBC World migrated 31M weekly readers to an isomorphic react app2 people · 5 points · first shared 2020 · discussion on HN
- 10Refactor Organisation – to build the technology right2 people · 4 points · first shared 2022 · discussion on HN
- 11Native Lazy Loading Has Arrived – BBC Design and Engineering – Medium2 people · 3 points · first shared 2019 · discussion on HN
- 12BBC News on HTTPS2 people · 2 points · first shared 2018 · discussion on HN
- 13A brief insight into the complexities of creating a new capability at the BBC1 people · 28 points · first shared 2021 · 8 comments on HN
- 14Secure HTTP for BBC Online: A 2017 Update1 people · 6 points · first shared 2017 · discussion on HN
- 15How We Deliver BBC Web Pages to the Internet1 people · 5 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
yesimahuman · 2021-10-30
Not a direct answer to your question but this was a great write up from the BBC (they use Capacitor): https://medium.com/bbc-design-engineering/shipping-progressive-web-app…
thamer · 2022-04-06
An engineering blog from the BBC published an update a few days ago on their migration to a serverless architecture, titled "BBC Online – A year with serverless": https://medium.com/bbc-design-engineering/bbc-online-a-year-with-serve…
They report 3.3B function invocations for 2.3B requests served, a total of 61,000 hours of execution time and 1,500 concurrent executions at peak.
Using calculator.aws, simply entering the number of requests at 67ms each (61k hours/3.3B invocations) with 128 MB of memory each computes a cost of only $1,107.
Then of course there's bandwidth, databases, file storage, and a lot more… but 3.3B lambda executions for $1.1k is really cheap. Not to mention that a client like the BBC would benefit from negotiated pricing with significant discounts. Even without discounts, serverless is often pretty cheap.
ldite · 2020-11-03
I notice that the previous post from the same author, dated 2017, was titled "Powering BBC Online with nanoservices" [0]. Nary a mention of nanoservices now. If I were a cynic, I would say they are going out of fashion.
[0] https://medium.com/bbc-design-engineering/powering-bbc-online-with-nan…
Keres · 2018-08-16
Not surprised at all, especially since the news site has only recently made the switch to https https://medium.com/bbc-design-engineering/bbc-news-on-https-182b45ef60…
niklasrde · 2018-02-13
With some exceptions, we found: https://medium.com/bbc-design-engineering/http-2-is-easy-just-turn-it-…
DRW_ · 2017-09-24
It's under the 'BBC Design & Engineering' page on Medium which has several managers from the department listed as editors:
https://medium.com/bbc-design-engineering/about
It has also been shared internally on a few slack BBC teams that I'm in, so it's all good.