Technology Category
- Infrastructure as a Service (IaaS) - Cloud Databases
- Platform as a Service (PaaS) - Application Development Platforms
Applicable Industries
- Construction & Infrastructure
- Telecommunications
Applicable Functions
- Maintenance
Use Cases
- Construction Management
- Speech Recognition
Services
- Cloud Planning, Design & Implementation Services
- System Integration
About The Customer
Plivo is a modern global telecommunications platform that serves more than one billion API requests per month across over 190 countries. Founded in 2011, the company provides enterprise-grade reliability for businesses that depend on voice and messaging to engage more effectively with their customers. Plivo is a leading cloud-based communications platform (CPaaS), which helps businesses engage and communicate with their customers. Their services are critical for businesses, as they require low-latency reads and writes for their Voice API platform. Plivo's use cases include rate limiting calls within a given time period, queuing call status, and maintaining call queues by region.
The Challenge
Plivo, a global telecommunications platform, was facing a challenge with its streaming microservices architecture. The architecture was supporting a large volume of small, high-frequency data writes. However, if an Amazon ElastiCache region were to fail, it could not keep up with the volume and maintain data consistency across regions. This posed a significant risk to Plivo's operations, as it could potentially disrupt their services and negatively impact their customers. The engineers at Plivo realized that they needed to build a custom failover to address this issue. They also needed a solution that could meet the performance requirements of their Voice API platform, which required low-latency reads and writes.
The Solution
After conducting tests, Plivo chose Redis Cloud as it could handle the requirements of their Voice API platform. The migration to the managed solution from the company behind open source Redis required almost no code changes, making the transition smooth and efficient. The initial migration was completed in minutes, and the complete move was finalized within a month. The use of Active-Active, an exclusive Redis Enterprise capability, allowed Plivo to optimize their service across regions and make the most effective use of their infrastructure. This solution also provided Plivo with a geo-distributed database, which ensured uptime and scalability through Active-Active Redis. The migration process was carefully planned and executed, with a rollback plan in place in case of any issues.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
IoT System for Tunnel Construction
The Zenitaka Corporation ('Zenitaka') has two major business areas: its architectural business focuses on structures such as government buildings, office buildings, and commercial facilities, while its civil engineering business is targeted at structures such as tunnels, bridges and dams. Within these areas, there presented two issues that have always persisted in regard to the construction of mountain tunnels. These issues are 'improving safety" and "reducing energy consumption". Mountain tunnels construction requires a massive amount of electricity. This is because there are many kinds of electrical equipment being used day and night, including construction machinery, construction lighting, and ventilating fan. Despite this, the amount of power consumption is generally not tightly managed. In many cases, the exact amount of power consumption is only ascertained when the bill from the power company becomes available. Sometimes, corporations install demand-monitoring equipment to help curb the maximum power demanded. However, even in these cases, the devices only allow the total volume of power consumption to be ascertained, or they may issue warnings to prevent the contracted volume of power from being exceeded. In order to tackle the issue of reducing power consumption, it was first necessary to obtain an accurate breakdown of how much power was being used in each particular area. In other words, we needed to be able to visualize the amount of power being consumed. Safety, was also not being managed very rigorously. Even now, tunnel construction sites often use a 'name label' system for managing entry into the work site. Specifically, red labels with white reverse sides that bear the workers' names on both sides are displayed at the tunnel work site entrance. The workers themselves then flip the name label to the appropriate side when entering or exiting from the work site to indicate whether or not they are working inside the tunnel at any given time. If a worker forgets to flip his or her name label when entering or exiting from the tunnel, management cannot be performed effectively. In order to tackle the challenges mentioned above, Zenitaka decided to build a system that could improve the safety of tunnel construction as well as reduce the amount of power consumed. In other words, this new system would facilitate a clear picture of which workers were working in each location at the mountain tunnel construction site, as well as which processes were being carried out at those respective locations at any given time. The system would maintain the safety of all workers while also carefully controlling the electrical equipment to reduce unnecessary power consumption. Having decided on the concept, our next concern was whether there existed any kind of robust hardware that would not break down at the construction work site, that could move freely in response to changes in the working environment, and that could accurately detect workers and vehicles using radio frequency identification (RFID). Given that this system would involve many components that were new to Zenitaka, we decided to enlist the cooperation of E.I.Sol Co., Ltd. ('E.I.Sol') as our joint development partner, as they had provided us with a highly practical proposal.
Case Study
Splunk Partnership Ties Together Big Data & IoT Services
Splunk was faced with the need to meet emerging customer demands for interfacing IoT projects to its suite of services. The company required an IoT partner that would be able to easily and quickly integrate with its Splunk Enterprise platform, rather than allocating development resources and time to building out an IoT interface and application platform.
Case Study
Bridge monitoring in Hamburg Port
Kattwyk Bridge is used for both rail and road transport, and it has played an important role in the Port of Hamburg since 1973. However, the increasing pressure from traffic requires a monitoring solution. The goal of the project is to assess in real-time the bridge's status and dynamic responses to traffic and lift processes.
Case Study
Bellas Landscaping
Leading landscaping firm serving central Illinois streamlines operations with Samsara’s real-time fleet tracking solution: • 30+ vehicle fleet includes International Terrastar dump trucks and flatbeds, medium- and light-duty pickups from Ford and Chevrolet. Winter fleet includes of snow plows and salters.