October 21, 2013
Irish-based utility meter management company, Temetra, has developed a first-of-its-kind wireless meter reading system that lowers the overall price of utilities by providing customers with highly accurate readings. To support this system, Temetra needed a scalable and reliable solution to access and store the growing volumes of critical data created by readings, which – for the average household – can number up to 400 each year. After reviewing Cassandra and Hadoop, Temetra chose Basho’s open source distributed database, Riak, to optimize efficiency and deliver a nimble and affordable service to customers.
Simplifying the Data Collection Process
Temetra offers a comprehensive data collection infrastructure that provides homes and businesses in the UK, Ireland, and Australia with intelligent metering for utility usage. This means that instead of manually checking meters periodically throughout each year, Temetra works from a wireless network that automatically collects and analyses usage data. This is done by simply driving past the meter whereas traditionally, meter readers had to visually copy the data index by hand. This new method allows the company to better predict usage and deliver more accurate results and pricing – saving Temetra time and the customer money.
The wireless system can collect 300-400 reads per year for the average household, as opposed to the normal rate of two reads. As many as 35,000 reads per year are now collected by fixed networks for larger consumers such as hotels and hospitals. This approach has been fundamental to Temetra’s competitive differentiation; however, with such a high volume of data, Temetra faced the challenge of finding a simple, scalable solution to store and access its data easily. “We needed a reliable solution that would allow us to support more and more meters on a fixed networks,” said Paul Barry, Temetra’s Managing Director. “Our relational SQL database just could not cope with the quickly rising levels of revenue critical data.”
Billions of Data Points
Temetra has thousands of users and millions of meters that create billions of data points. The massive influx of data that was being generated quickly became difficult to manage with the company’s legacy SQL database. When considering how this structured database could be overhauled, Temetra conducted evaluations with Cassandra and Hadoop but ultimately chose Riak due to its high availability, relatively self-maintaining and easy to deploy infrastructure. It is essential that the data collected from the meters is always available as it is relied on to determine correct billing for Temetra’s customers. This point was stressed by Barry with his statement, “As a small company managing a lot of revenue critical data, it is really important for us to have a reliable and easily accessible database. For example, during our development and testing phase, a Riak node went down for a day and it was only through monitoring that we spotted it. The ability to lose a node and not affect our service in any way is a huge advantage for us.”
The move from a relational database to the non-relational Riak was a big step for Temetra. The shift required an adjustment to treat the database as a low maintenance, high performance, and high availability key value store. For Temetra, the biggest change was denormalizing the data or, in other words, allowing for several copies to be stored. Riak provided the best performance by allowing the company to store data in different ways. For example, data comes in from meters as a single data point that needs to be loaded and turned into compute data. In Riak, Temetra is able to store the meter data in multiple ways, allowing it to come out pre-calculated in the quick and ready form of consumption data. Once they were comfortable with Riak’s replication technology, Temetra was able to load its data from the legacy file store and use Riak as a limitless data store across its multiple sites.
The Benefits of Riak
As a growing company with 3.5 million meters currently collecting revenue critical data, Riak’s ability to easily support additional nodes is a key benefit for the company as it continues to scale up. With Riak, Temetra can continue to expand without huge amounts of additional costs and hardware and is able to bring another server online within 20 minutes, allowing the business to prepare for big, new customers very quickly. This flexibility reflects and underpins Temetra’s own fast growing innovative nature.
Another benefit is the pricing. Temetra’s competitors operate in SQL mode and are unable to scale as easily or as quickly. Working with Riak has allowed Temetra to break away from those limitations which is reflected in the pricing for customers, giving the company a significant competitive edge. Additionally, Riak was very easy for Temetra to introduce. As a small company, Temetra doesn’t want a large administration staff dedicated to looking after the IT infrastructure; therefore, Riak’s relatively self-maintaining nature, alongside Basho’s expert support, was a definite advantage.
“Most of our competitors still operate in SQL mode,” noted Barry. “By working with a distributed database that, from a flexibility and resiliency perspective puts us more in line with the way Google or Twitter work, we can disrupt the way that data is stored traditionally to scale faster and easier. This is reflected in our prices and our ability to rapidly introduce new functionality. I think our customers definitely see that benefit.”
October 14, 2013
Kivra is a Swedish company that provides secure digital mailboxes, allowing users to securely receive, upload, and store all postal mail. Their mailboxes help users organize bills and notifications while eliminating the environmental footprint created from paper mail.
At a Riak Meetup in Dublin earlier this year, Kivra CTO, Bip Thelin, spoke about how they currently use Riak. Originally, Kivra tried to build their platform on a SQL database. However, they quickly outgrew this system and decided to move their infrastructure to Erlang and Riak because of its scalability and resiliency. You can watch Bip’s full presentation below to learn more about why they chose to switch to Riak, how they built six Riak clusters, and some of the lessons they’ve learned.
Bip’s slides can also be viewed here:
For more companies that have switched from SQL to Riak, check out our Users Page.