Ifedayo_s

Built something for building composable backend components. You can bring in any backend component, define it and combine it with other backend components. I want to know what you think.

For most people, modularity is just a separation of concerns. In this, we talk about the ability to actually reuse components. I'll like to know what people think. It's a project I'm working on.

I built this tool, Ductape to make backend components reusable and environment-agnostic.

Called it Ductape cos most of people use Duct tape to join things together and it's what this does.

What I've tried to do is instead of hardcoding backend logic into each service, such as database operations, notifications, message queues, or third-party API calls, you define it once and move all environment or provider-specific details, such as credentials, endpoints, and retries, into a config.

Your services don’t need to know how the logic works. You can reuse the same component across projects and environments without duplicating code. And if you need to switch providers or move to a new environment, you update the config, not the code.

I don't know if anybody finds it useful or thinks it's special in anyway. I'd appreciate some feedback.

Thanks!

There's a use cases page.

https://www.ductape.app/use-cases

Can you explain what you mean by opinionated? We've tried to make this as flexible as possible

Thank you! I'll keep that in mind. In case you want to see a demo, for now you can check out this link here: https://vimeo.com/1082963222/e6d52b9b31

So say you have multiple services that often need to process payments. For example, you have a billing service, a subscription service, and a checkout service, each responsible for handling different parts of the payment flow. Typically, these services integrate directly with a payment provider such as Adyen, Stripe, or Braintree. You have to duplicate logic across these services.

They all have to handle authentication, retries, error handling, and webhook processing separately. You have to manually configure and update and test across envs.

So if you want to make a change, you'll have to go into each service and rework the integration logic.

With Ductape, instead of embedding provider-specific logic in every service, you write it once and configuration files handle the differences between environments and providers. So you can use same logic across your billing, subscription, and checkout services without duplication.

If you want to switch providers, you don’t touch the logic at all. You just update the configuration.

Pls can you try again? It should work now.

Initially we support just Postman and Swagger but we plan on expanding to new services as we grow. We also work on allowing people define their endpoints (although we think that might be even more stressful)

So what it does is it lets you write your integration logic (like payments, auth, or KYC) once and reuse it across all your backend services, environments, and providers without duplicating code.

For example instead of putting Braintree or stripe code in every service, you write one chargeCustomer() function in Ductape and call it from anywhere. If you want to switch to another provider, you just change a config file, not your code.

I will rework the website. Thank you so much for the feedback. It's should have used the link for the docs instead.

Oh thank you. The website was made much earlier. I had to get a frontend person to build it and I'm not really good at frontend design so I have to get another person to rework it. Thank you very much for this feedback.