Presentation: Digital Publishing for Scale: The Economist and Go

Track: 21st Century Languages

Location: Empire Complex, 7th fl.

Duration: 10:35am - 11:25am

Day of week: Friday

Level: Intermediate

Persona: Architect, Developer

Share this on:

What You’ll Learn

  • Learn about the pros and cons of leveraging Go as a development platform.

  • Hear about strategies for decomposition of a monolith into Go Microservices.

  • Understand how Go address concurrency and how it can benefit you.

Abstract

The Economist newspaper was first printed in 1843. Since then, readers consume news in rapidly evolving ways and technology has taken the forefront in delivering content and enabling the severe contest between intelligence, which presses forward, and an unworthy, timid ignorance obstructing our progress.

To meet these challenges, The Economist restructured its platforms for digital delivery by breaking down a monolithic CMS and adopting a distributed, microservices architecture. The Economist implemented Go to write services responsible for delivering content across products and platforms. Go has enable the team to quickly adapt to business needs and scale for growing demand, but it has not been without its own challenges. This talk will cover the struggles and victories in transitioning to Go and how Go has uniquely fit The Economist’s digital publishing goals.

Question: 

Would you describe your work at The Economist?

Answer: 

I am the lead engineer for the content platform team at The Economist. We deliver content to different products within The Economist (as well as to our external consumers). Our team is responsible for adding new features to the content platform thereby helping the business build new products.

Technically, it is a distributed platform, that is DevOps heavy. We use the Go language for coding applications. On the frontend, we have a Rest API but we also use GraphQL for some of the advanced queries. We use Elasticsearch for indexing and linking content.

Question: 

What is the motivation for your talk, Digital Publishing for Scale: The Economist and Go?

Answer: 

At The Economist we moved from a traditional monolith Drupal CMS architecture to a distributed system implemented using the Go programming language. I want to share this experience, and talk about some interesting use cases, where using Go helped us. I would also like to highlight the use cases where it was not a good fit.

Question: 

Who is the target audience for this talk?

Answer: 

It is mostly for developers who are interested in the Go programming language and have considered using it. I will talk about some of the well-known benefits of Go, together with some of the lesser known features, which we found useful.

I will also talk about the overall framework, and how we moved from a monolith to a distributed architecture. Architects may find this part of the talk interesting.

Question: 

What can a developer expect to take away from this talk?

Answer: 

The talk will be helpful for developers who are interested in Go but haven't work with it much before, as well as developers looking to breakdown systems into smaller, scalable components. I will show how many features of the language help developing scalable platforms, such as Go's built in concurrency support.

The talk will give both the pros and cons of using Go. So on the downside, I will demonstrate a scenario which was easier to implement in JavaScript as compared to Go.

Speaker: Kathryn Jonas

Lead Engineer @TheEconomist

My name is Jonas, I’m the Lead Engineer for the Content Platform at The Economist and a product of Midwestern comfort food, fantasy novels, and a love for complexity. After studying Political Theory, I found my passion in using technology to solve social problems. I’ve lead projects for organizations in Beijing, London, and New York, applying technology to diverse challenges such as mission impact evaluation, editorial transparency and trust, and online learning and collaboration. I thrive on engaging software architecture debates and working with animated, empowered teams (and coffee).

Find Kathryn Jonas at

Similar Talks

Site Reliability Engineer @Google
Developer Programs Engineer @Google
Staff Site Reliability Engineer (Google Cloud Customer Reliability Engineering)
Head Of Technology - Products @ThoughtWorks
Developer Advocate @Couchbase
Senior Director Platform Engineering @twilio
Software Engineer & Engineering Manager @Honeycombio
Developer Programs Engineer @Google

Tracks