SE Radio 631: Abhay Paroha on Cloud Migration for Oil and Gas Operations

Topics covered
Popular Clips
Questions from this episode
- Asked by 2 people
Episode Highlights
Design Insights
In the realm of microservice design, shares his approach to defining the scope and evolution of services. Initially, his team focused on data ingestion, evolving from a proof of concept to more complex domains like mapping and API creation. This progression allowed clients to build dashboards and workflows, enhancing the functionality of oil well forecasting and advisory services 1. However, the journey wasn't without challenges. Abhay recalls a significant learning experience when their on-prem software failed, highlighting the importance of proactive monitoring and cloud readiness 2.
Delivering features is not only the important part, the other part is operating as well.
---
These insights underscore the need for a robust cloud strategy and continuous learning in microservice development.
State Management
State management in microservices is crucial, particularly when using Kubernetes. explains the role of stateful sets in maintaining persistent storage and unique identification for pods, which is essential for applications like databases and message queues 3. The choice of programming language also plays a role in state management. Abhay's team transitioned from Java to Scala, leveraging Akka for its actor-based framework, which supports scalable and fault-tolerant applications 4.
Akka provides a streaming and one important point in Akka streaming it basically handle the asynchronous data ingestion.
---
This framework's integration with Kubernetes enhances the system's ability to manage state effectively.
Efficient Scaling
Scaling microservices efficiently is a key focus, with detailing the use of Kubernetes and Keda for auto-scaling. Initially, manual scaling was employed, but the team shifted to auto-scaling using custom metrics, allowing them to handle large data volumes from oil wells 5. This approach minimized latency and optimized resource usage, crucial for both ingestion and consumption processes.
We tried to achieve the auto scalability first we tried the manual scalability, then auto scalability.
---
Keda, as a Kubernetes event-driven auto-scaler, played a pivotal role in adapting to fluctuating data streams, ensuring efficient scaling and cost management.
Related Episodes


SE Radio 586: Nikhil Shetty on Virtual Private Cloud
Answers 383 questions

SE Radio 653: Asanka Abeysinghe on Cell-Based Architecture
Answers 383 questions

SE Radio 571: Jeroen Mulder on Multi-Cloud Governance
Answers 383 questions

SE-Radio-Episode-259:-John-Purrier-on-OpenStack
Answers 383 questions

SE-Radio Episode 247: Andrew Phillips on DevOps
Answers 383 questions

SE Radio 636: Sriram Panyam on SaaS Control Planes
Answers 383 questions

Episode 519: Kumar Ramaiyer on Building a SaaS
Answers 383 questions

SE-Radio Episode 320: Nate Taggart on Serverless Paradigm
Answers 383 questions

SE-Radio Episode 314: Scott Piper on Cloud Security
Answers 383 questions

SE Radio 645: Vinay Tripathi on BGP Optimization
Answers 383 questions

SE-Radio Episode 313: Conor Delanbanque on Hiring and Retaining DevOps
Answers 383 questions

SE-Radio Episode 312: Sachin Gadre on the Internet of Things
Answers 383 questions

SE Radio 591: Yechezkel Rabinovich on Kubernetes Observability
Answers 383 questions

SE-Radio Episode 268: Kief Morris on Infrastructure as Code
Answers 383 questions

SE Radio 579: Arun Gupta on Open Source Strategy and Community
Answers 383 questions













