![]() To ensure that the Meter could scale, we needed business logic consolidated within the service itself, instead of spread out across our apps and website Our Android app had its own metering service separate from the main service. It was obvious that we were years behind the type of architecture we develop at The Times today. The only saving grace was that the XML-based metering rules were versatile enough to meet our current business logic needs. When we cleared the cobwebs, what we found was a complex NGINX configuration that fronted a parsing engine in C and an architecture that couldn’t autoscale, all deployed to Amazon Web Services (AWS). The original creators were long gone, and it was built at a time when the industry doubted whether a subscription-based digital news service would even work. What we had on our hands was an eight-year-old application that had been in maintenance mode for most of its life. We combed through old documentation for the Meter, talked to people who had been involved throughout the years and determined what improvements it needed to continue to meet our business objectives. If they can be avoided, then it’s probably best to avoid them. ![]() To be clear, we don’t take rewrites lightly. ![]() To up the stakes, we had to ensure there was zero interruption to the business while also writing it to scale for future needs. In early 2018, we decided it needed to be rewritten. ![]() It also handles over 30 million user requests daily and it is the gatekeeper for how we acquire new subscribers. The Meter Service has been around since we first launched our paywall in 2011 and it determines if our readers can access the hundreds of articles we publish every day. An example of the inline messaging that appear in Times articles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |