DEV Community: Gorakhnath Yadav

Open-Source Payments: Modular, Flexible, and Built for You

Gorakhnath Yadav — Tue, 11 Mar 2025 06:57:19 +0000

Imagine a Linux-like foundation for payments. A unified and open-source intelligence that transforms payment agility into a competitive advantage.

Introducing Hyperswitch, a modular, open-source, and interoperable full-stack payments platform engineered to put control back in your hands.

Why Hyperswitch?

Enterprises can build, augment, or customize their payment stack with modular solutions. Whether it's enabling alternate payment methods, streamlining operations across multiple providers and acquirers, or optimizing payment routing—Hyperswitch provides the flexibility businesses need.

With advanced analytics on processing costs, seamless authentication, token storage, and reconciliation, it simplifies and secures global payments.

Backed by a Global Engineering Force

Hyperswitch is powered by 1,000+ payment engineers globally, enabling infrastructure that processes up to 175 million transactions a day with 99.999% availability.

Engineered with robust system design principles, its open-source architecture ensures transparency, security, and enterprise-grade reliability with PCI compliance, tokenization, and security certifications.

Freedom from Closed-Loop Systems

With Hyperswitch, merchants gain rapid integration capabilities and freedom from vendor lock-ins. The open-source model allows for risk-free due diligence, eliminating the need for lengthy and costly RFP cycles.

Merchants can deploy Hyperswitch in local or cloud environments or leverage Juspay’s hosted sandboxes for seamless experimentation.

Take Control of your Payments

Whether you aim to optimize costs, expand into new markets, or reduce vendor reliance, Hyperswitch empowers you to build what you want, how you want.

🔗 Learn more about open-source payments and Juspay Hyperswitch.

Transitioning from Kubernetes to EC2 for Enhanced Kafka Performance

Gorakhnath Yadav — Thu, 06 Feb 2025 14:07:56 +0000

Scaling distributed systems is never just about performance, it's also about cost and operational efficiency. While Kubernetes provided us with a solid foundation for container orchestration, we hit unexpected roadblocks when running Kafka clusters at scale.

Costs were rising due to inefficiencies in resource allocation.
Auto-scaling wasn’t handling our stateful workload well.
Kafka node management with Strimzi led to operational complexity.

After months of firefighting, we decided to move from Kubernetes to EC2, a transition that improved performance, simplified operations, and cut costs by 28%.

Here’s the story of that journey, what worked, and the lessons we learned.

Why Kubernetes wasn’t working for us?

1. Resource Allocation Inefficiencies

Kubernetes dynamically manages resources, but in our case, it led to hidden inefficiencies.

For example, when allocating 2 CPU cores and 8GB RAM, we observed that the actual provisioned resources were often slightly lower (1.8 CPU cores, 7.5GB RAM). This discrepancy may seem trivial, but at scale, it resulted in significant wasted resources and unexpected cost overruns.

Imagine paying for a full tank of fuel, but your car only gets 90% of it. Over time, those missing liters add up.

2. Auto-Scaling Challenges for Stateless Applications

Kubernetes’ auto-scaling mechanism works well for stateless applications, but Kafka isn’t stateless. When resources ran out, Kubernetes would restart our Kafka application instead of efficiently scaling it.

This resulted in:

15-second delays in message processing.
Increased latency during scaling events.
Operational headaches managing stateful workloads.

3. Kafka Node Management with Strimzi

Initially, we relied on Strimzi for managing Kafka clusters. However, it had major drawbacks:

New Kafka nodes often failed to integrate properly.
Manual intervention was required for every scaling event.
Overall Kafka performance was unpredictable.

Managing our Kafka clusters felt like playing whack-a-mole every time we solved one issue, another would pop up.

Decided to move to EC2

After evaluating various alternatives, we decided to move Kafka from Kubernetes to EC2. This gave us more control over resource allocation, auto-scaling, and cluster management.

Here’s what changed:

1. Replacing Strimzi with a Custom Kafka Controller

Instead of relying on third-party tools, we built an in-house Kafka Controller tailored to our needs.

Seamless integration of new Kafka nodes
Automated scaling based on real-time workload analysis
Better cluster management with minimal manual intervention

Result? Kafka nodes were now automatically recognized and integrated instantly.

2. Precise Resource Allocation

Unlike Kubernetes, where we had limited control over resource provisioning, EC2 allowed us to:

Allocate exactly the CPU and memory we needed.
Avoid wasted resources and over-provisioning costs.

Example: Previously, we paid $180/month per instance on Kubernetes. After transitioning to EC2, this dropped to $130/month, saving 28% on infrastructure costs.

3. Streamlined Kafka Node Support

With EC2, we could now:

Scale up Kafka nodes seamlessly without restarts.
Perform vertical scaling (switching to more powerful machines) with zero downtime.
Ensure predictable performance under peak loads.

Last month, we moved from a T-class instance to a C-class instance in EC2 without downtime. If we had been on Kubernetes, this would have required:

Creating a new node group.
Rebalancing partitions manually.
Managing potential downtime.

Instead, on EC2, it was a simple instance upgrade with zero complexity, zero downtime.

The Impact: Cost Savings & efficiency gains

Key lessons & Takeaways

Not all workloads are ideal for Kubernetes – It’s great for general-purpose container orchestration but not always the best for stateful applications like Kafka.
Custom solutions can be worth it – Building an in-house Kafka Controller gave us better control and reliability.
Cost inefficiencies add up – Even small inefficiencies in resource allocation can result in thousands of dollars lost at scale.
EC2 provides better flexibility – We gained granular control over scaling and performance with EC2.

Conclusion

If you’re running Kafka on Kubernetes and experiencing similar issues, EC2 might be a better fit.

Who should consider moving? Teams struggling with stateful workloads on Kubernetes.
Who should stick with Kubernetes? Those managing stateless, highly dynamic applications.

Every infrastructure decision should be guided by workload needs, not just industry trends. Kubernetes is powerful, but for Kafka, EC2 provided the right balance of cost, performance, and operational efficiency for us.

Hacktoberfest 2024: Maintainer POV

Gorakhnath Yadav — Thu, 31 Oct 2024 06:25:09 +0000

As October comes to an end, I’ve been reflecting on my experience during Hacktoberfest this year. This time, I participated as a maintainer for our project at @hyperswitch , which deepened my appreciation for the importance of community in open source.

My Role: As a DevRel, I was looking after issue creation, guiding people to resources, managing the assignment of issues, and coordinating among the contributors and the internal team for queries and reviews.

How It Went:📈

We kicked off with a good start; as we created issues in the last weeks of September, contributors were already discussing and working on them.
As soon as we started, we had a lot of people coming in and asking for assignments of issues so they could work on it. By October 3rd, we had 48 issues assigned, 18 PRs raised.
Tried to make issues beginner-friendly, given the complexity of digital payments.
Saw participation from all skill levels, from first-time contributors to seasoned Hacktoberfest participants.

Learnings for us:🤔

Hacktoberfest allowed me to view our project from a fresh perspective, as contributors noticed details I might overlook.
Questions from contributors helped identify areas in our documentation needing clarification, which we’ll be updating soon.
Also updating guidelines to address common queries raised by contributors.
Participation seemed lower this year, and I wonder if this trend affected other projects as well. I'd love to hear your thoughts on this.

Community is WOW!❤️

Hacktoberfest also highlighted the diversity of the open-source community. As we had people from each level of skills and expertise, each contributor brought unique insights. Some were experienced developers who tackled issues with ease, while others were just starting out but were eager to learn and help. Working with such a diverse group reminded me that open source thrives on this variety of skills and perspectives.

Being a maintainer also reinforced the responsibility that comes with this role. Open source is not just about code—it’s about creating a space where everyone feels welcome to contribute. It’s essential to be approachable, give helpful feedback, and appreciate the time each person spends on their contribution.

Road Ahead:🛣️

This Hacktoberfest was full of learning, connection, and growth for our community. My experience as a maintainer at Hyperswitch provided insights I hadn’t expected and reminded me why open source is about much more than just coding. I’m excited to continue supporting this community and watching it grow.

Here’s to Hacktoberfest 2024🥂 and to all the contributors who bring life to open source!🚀

🚀 Hyperswitch Plugin Development Hackathon: Build, Compete, and Win Big! 🚀

Gorakhnath Yadav — Wed, 09 Oct 2024 10:48:02 +0000

Hey developers! 🔥

We’re excited to announce the Hyperswitch's Plugin Development Hackathon, running from October 9th to October 31st, 2024. It’s your chance to develop plugins for Hyperswitch, collaborate with fellow developers, and win big rewards!

What’s the Hackathon About?

You'll be building plugins for platforms like MedusaJS, CommerceTools, or Prestashop, helping to extend Hyperswitch’s payment orchestration platform. Participate individually or as a team (up to 4 members) and tackle real-world payment challenges while competing for awesome prizes!

Key Dates:

Registration Deadline: October 14th, 2024
Approach Submission: October 14th, 2024 (EOD IST)
Final Submission: October 31st, 2024
Demo Day: First week of November 2024 (TBA)

How to Participate:

Sign Up: Register before October 14th to get started.
Submit Your Approach: Outline the core features, integration with Hyperswitch’s API, and edge case handling by October 14th.
Get Shortlisted: The Hyperswitch team will review your submission and notify shortlisted teams.
Develop Your Plugin: If selected, you’ll have two weeks to complete your plugin.
Demo Day: Showcase your plugin in early November, dates to be announced!

Prizes:

MedusaJS Plugin: $2000
CommerceTools Plugin: $2000
Prestashop Plugin: $2000

Ready to showcase your skills? Register today and start building your plugin! Let’s code, collaborate, and win together. 💻

Good luck to all participants! 🎉

Star Us on GitHub
Follow us on twitter

Hacktoberfest 2024 with Hyperswitch

Gorakhnath Yadav — Fri, 27 Sep 2024 09:07:40 +0000

Join the Celebration of Open Source!

Hyperswitch is excited to participate in Hacktoberfest 2024! Join us in building a robust payment infrastructure that serves billions of people worldwide. Contribute to our open-source projects and earn exciting rewards.

How to Get Involved

1. Explore Hyperswitch Repository:

Visit our GitHub page.
Star and watch the repositories to stay updated with new issues.

2. Find Issues to Work On:

Look for issues tagged with "hacktoberfest".
If you have ideas for improvements, feel free to create new issues, and inform us using community channels.

3. Make Your Contribution:

Comment on the issue you want to work on: "I would like to work on this. Can you assign it to me?"
Ensure you follow up within 3-4 days to show you are actively working on it.
Submit your pull request (PR) and link it to the issue. Tag a maintainer for review.

4. Get Support:

Our maintainers are here to guide you. Join our Community for support and to connect with fellow contributors.

5. Earn Swag:

Get one PR merged to earn exclusive Hyperswitch swag.
Get 3 or more PRs merged to receive a special swag kit from Hyperswitch.

Why Contribute?

Learning Opportunities: Enhance your skills by working on real-world projects.
Networking: Connect with a global community of developers.
Rewards: Earn cool swag for your contributions.

Join the Hyperswitch Community

Star Us on GitHub

Happy Contributing!🎉

Dive Into the World of Payments - Join Payment Meetup Group’s First Session!

Gorakhnath Yadav — Mon, 09 Sep 2024 03:29:40 +0000

Have you ever wondered what happens behind the scenes when you click "Pay Now"?

If you're a developer, payment enthusiast, or just curious about how digital payments via card works, we have an exciting session lined up just for you!

At Payments Meetup Group, we’re diving deep into the mechanisms that power online transactions via cards, and we want to bring you along for the journey. Our upcoming session, led by Samraat Bansal, Engineering Tech Lead at Hyperswitch, will explore every detail from data encryption and transmission to how various players like issuing banks, card networks, and merchants handle your card payment.

Why You Should Join:

In-depth Insights: Understand the flow of transactions and how card payments are processed securely.
Learn from Experts: Samraat Bansal brings hands-on experience from leading Hyperswitch’s tech innovations.
Engage with Community: This is a perfect opportunity to network with fellow developers and digital payment enthusiasts.

Session Highlights:

What happens when you enter your card details and click "Pay Now"?
The critical role of encryption and transmission in ensuring transaction security.
How various stakeholders like banks and merchants collaborate to approve or decline your transaction.
Behind-the-scenes interactions between card networks, acquiring banks, and issuing banks.

When and how to join?

Date & Time: 11th Sept, 2024, 07:30 PM (GMT +2)
Where: Online (Link to register)

Don’t miss out on this deep dive into the fascinating world of digital payments. Whether you’re a seasoned developer or new to the world of digital finance, this session is tailored to give you valuable insights and practical knowledge.

RSVP Now and be part of this insightful conversation!

Securing Digital Transactions: How Hyperswitch makes Payment Protection a Priority

Gorakhnath Yadav — Thu, 01 Aug 2024 09:26:44 +0000

Security is not a product, but a process - Bruce Schneier

In today's digital landscape, data security is paramount, especially when it comes to online payments. At Hyperswitch, we've built our platform with security as a fundamental principle. Let's explore the robust measures we've implemented to ensure a safe and secure payments infrastructure.

Our Top Priority: Customer Security

When a customer makes a payment through Hyperswitch, their card information is immediately encrypted at the source. We use the SSL/TLS 1.2 protocol for transmission, adhering to PCI standards for handling card data.
For customers who opt to store their card details, we've developed a secure Card Vault. This system employs multiple layers of protection:

SSL/TLS 1.2 encryption
JWE + JWS for secure data transmission
Double encryption for stored data
A two-key custodian system for enhanced security

Additionally, all customer Personally Identifiable Information (PII) is TLS encrypted in transit and AES encrypted at rest.

Keeping Your Business Secure

For our merchant, we know that not everyone needs to be in on all the secrets. That's why we've built up an access control system that's more discerning. API credentials? We treat those with more care than a rare vintage car, wrapping them in layers of AES encryption. Also, we mask the sensitive merchant details in the dashboard.

Hyperswitch's Approach to Security

At Hyperswitch, we're not just building a payment system; we're crafting a digital fortress. Our multi-tenant system comes with unique data encryption keys for each business, creating a security layer that's both impressive and effective.
We've also enlisted Rust as our companion, using its robust type system to keep sensitive information under wraps. It's like having a very diligent, slightly obsessive assistant who never lets a secret slip.

Serious Security with a Smile

In the end, we're not just developing an application; we're creating a secure future for digital transactions. Our goal is to allow businesses to focus on their core competencies while we ensure the protection of their customers' financial information.
With Hyperswitch, security isn't just a feature—it's a cornerstone of our service. We're dedicated to maintaining the highest standards of data protection, giving both merchants and customers peace of mind in their digital transactions.

Want to contribute? Check out some of our good first issues here.
Try Hyperswitch. Get your API keys here. Happy reading!

Scaling to 125 Million Transactions per Day: Juspay's Engineering Principles

Gorakhnath Yadav — Wed, 19 Jun 2024 14:32:56 +0000

At Juspay, we process 125 million transactions per day, with peak traffic reaching 5,000 transactions per second, all while maintaining 99.99% uptime. Handling such enormous volumes demands a robust, reliable, and scalable system. In this post, we'll walk you through our core engineering principles and how they've shaped our engineering decisions and systems.
When designing systems at this scale, several challenges naturally arise:

Reliability vs Scale: Generally, as you scale, you tend to exhaust resources, which can affect system availability.
Reliability vs Agility: Frequent releases and system changes can impact system reliability.
Scale vs Cost-Effectiveness: Scaling requires more resources, leading to higher costs.

Core Engineering Pillars

We've been able to strike the right balance between these challenges by anchoring our tech stack on four pillars:

Build zero downtime stacks: Solve reliability by building redundancy at each layer to achieve almost 100% uptime.
Horizontally scalable systems: Solve scalability by building systems that can scale horizontally by removing bottlenecks.
Build agile systems for frequent bug-free releases.
Build performant systems for low latency, high throughput transaction processing.

Adopting Haskell Programming Language

To achieve our goals, we've made a critical investment: adopting the Haskell programming language. Haskell, a functional programming language, offers performance akin to C, which is closer to the machine and processes transactions much faster. With Haskell, we've reduced our transaction processing time to less than 100 milliseconds.

Here's an example of a Haskell function that adds two numbers:

-- Define the add function
add :: Int -> Int -> Int
add x y = x + y

-- Main function to test the add function
main :: IO ()
main = do
    let sum = add 3 5
    putStrLn ("The sum of 3 and 5 is " ++ show sum)

This function showcases Haskell's concise and readable syntax.

Additionally, Haskell's readability, like English, enables non-technical folks to read the code easily, verify business logic, and sign off on features during development itself. As a strong-typed language, Haskell enforces a set of rules to ensure consistency of results, helping us preempt failures and achieve zero technical declines.

Cache-based Shock Absorber

To handle scale and remove database bottlenecks, we introduced a horizontally scalable caching layer where real-time transactions are served from this cache layer and later drained to the database.

Scaling up and down the cache layer is relatively easy and cost-effective compared to scaling databases.

Rapid Deployment and Release Frameworks

With rapid development comes the challenge of frequent production releases. To achieve agility through frequent releases without compromising reliability, we've built internal tools for automated releases with minimal manual effort. These tools monitor the performance of the release by benchmarking error codes against the previous stable version of the codebase:

ART (Automated Regression Tester): A system that records production payloads and runs them in the UAT system against a new deployment to identify bugs early.
Autopilot: A tool that creates a new deployment and performs traffic staggering from 1% onwards.
A/B testing framework: A system that monitors and benchmarks the new deployment's performance against the previous stable version. Based on this benchmark, the system automatically decides to scale up the traffic or abort the deployment.

Hyperswitch: An Open-Source Payments Switch

We're carrying these learnings forward to our latest product, Hyperswitch, an open-source payments switch. Every line of code powering our stack is available for you to see. With Hyperswitch, our vision is to ensure every business has access to world-class payment infrastructure.

Conclusion

Through these investments, we've built reliable, agile, and scalable systems, enabling our engineers to solve exciting new problems and fostering a culture of systems thinking within the company. We encourage developers to engage with the open-source Hyperswitch project and explore the principles and technologies we've adopted to handle massive scale and high-volume transaction processing.