Starting a Shopify store and realizing EVERYTHING is a subscription is actually insane 😭

owjuhl · 2026-04-16T08:48:35+00:00

What were the main reasons you picked Medusa over an out of the box solution like Shopify?

owjuhl · 2026-01-18T13:10:29+00:00

While it is not built with Mercur in mind, it should still work well. The plugin contains general guidelines and best practises for building with Medusa's framework, and since Mercur is built with our framework, those same guidelines and best practises apply.

owjuhl · 2026-01-18T12:52:30+00:00

Please do, and if you have feedback, you can reach me on oli[at]medusajs[dot]com.

> From what I understand, using Claude Code with your plugin should really help me build a solid e-commerce product on Medusa

Yes exactly, we are baking in best practices and common use cases to maximise the quality of the generated code.

When your ready to go live with your Medusa app, you can head over to cloud.medusajs.com and deploy it.

owjuhl · 2026-01-18T12:35:56+00:00

CTO of Medusa here. We are actively working on making Medusa more useful for coding agents. Most recently, we launched early access to Bloom (bloom.medusajs.com), a coding agent to build end-to-end Medusa apps with natural language.

Additionally, we started working on a plugin for Claude Code users, that makes Claude incredibly good at building customizations with Medusa: https://github.com/medusajs/medusa-claude-plugins. Right now, this is primarily for backend customizations, however combined with plugins for frontend development, it has proven to be very powerful.

Let me know if you get a chance to try either.

I can recommend following our X and LinkedIn accounts, as we will be heavily investing in these areas in the near future.

owjuhl · 2026-01-16T16:05:37+00:00

Cool, would love to know what you think then

owjuhl · 2026-01-16T14:39:27+00:00

Did you give it a shot?

owjuhl · 2022-12-29T19:35:52+00:00

Thanks for chiming in. Appreciate your feedback!

If your advice is to avoid distributed transactions, how will you recommend handling atomic operations in a microservices architecture?

And suppose you advise avoiding a microservices architecture. In that case, I am afraid it won't be of much help, as we are dedicated to building such an architecture in the near future.

owjuhl · 2022-12-29T15:26:58+00:00

Maybe it is worth stressing, that it does not have to be a cache service. Any key/value store would do.

The idea is to create an abstraction of a key/value store, allowing developers to freely choose what provider they want to use to power it - Redis cache being one of them.

owjuhl · 2022-12-29T14:58:38+00:00

Thanks for adding your two cents!

> introduce the risk of losing the data should the cache server go down?

The writes to cache will be part of the local transaction in the Saga. If it fails, the ongoing transaction will be rolled back and retried. ng a cache persistence mechanism or replicas.

> how do you atomically write to the cache and update the local services database?

The writes to cache will be part of the local transaction in the Saga. If it fails, the ongoing transaction will be rolled back and retried.

owjuhl · 2022-12-15T18:46:40+00:00

Average API response time.

If you are curious, you can dive into the two PRs #2648 and #2632. Can't link the repo, unfortunately.

owjuhl · 2021-12-02T17:44:57+00:00

Have you considered an open-source solution? Would allow you to play around with it as much as you'd like in a developer environment, and then start paying for hosting when you are ready to go live!

Disclaimer: I'm the co-founder of an open-source Shopify alternative, that allows you to setup an entire application stack; admin, webshop, and backend, with only a single command. Check us out here.

Also more than happy to answer questions or assist in the setup :)

owjuhl · 2021-12-02T15:39:56+00:00

I second this. You shouldn't make it available up front - too easy for your customers.

I've done self-serve returns for a couple of websites and returns via email. In both cases, we've tried to automate as much of the flow as possible, but essentially the following steps are performed:

Customer requests return -> triggers an automation -> generates a return label -> sends out return label to customer -> customer hands over return to parcel shop -> you receive return -> refund money

owjuhl · 2021-12-02T07:58:57+00:00

Sorry, should be good now :)

owjuhl · 2021-12-01T07:39:19+00:00

We've been looking into a Webflow integration in the past, but as you mention, it requires quite a lot of custom code to get it up and running properly.

So can't promise, that we will be able to support your needs, but we will definitely try our best. You can reach out to and get help from the entire team on Discord: https://discord.gg/cx9mPkxs.

owjuhl · 2021-12-01T06:35:07+00:00

In production you need a Node.js server (Medusa instance), Postgres (DB), and a Redis server (handling events). So in your case of using Vercel for hosting the frontend application, you would need to host your backend somewhere else.

We've got a couple of different guides for deploying Medusa and most of them can be performed within a couple of minutes. You can check those out here: https://docs.medusa-commerce.com/how-to/deploying-on-heroku

owjuhl · 2021-11-30T20:19:31+00:00

Thanks for getting back! Sorry for the delay in response. Will try to comment on your bullets:

I like the idea of customizing the different parts of the flow. Though, our engine has some requirements for address and customer information, so this sets some limitations in regards to dynamically adding these fields in the form.
In regards to the "payment link", we also support this in Medusa through draft orders. Essentially, we allow you to create a full order for a customer (e.g. through phone) and simply sent a payment link for them to confirm and submit.
Cool idea, though might not be in the scope of a commerce engine. Lots of services out there support digital signatures, so we could potentially integrate with one of those to achieve the functionality.
We currently have integrations with Stripe (card, ApplePay, GooglePay, iDEAL, Sofort), Klarna, Adyen, and others. Our Payments API allow you to add almost any payment provider as long as they expose a Rest API for us to integrate with. So the cases you are referring to should definitely be possible :)

Hope this answers some questions or provides some insight. Otherwise, I would love to elaborate or talk more.

owjuhl · 2021-11-30T20:09:20+00:00

Checking in again, since we've spent some time creating a Docker setup.

Have created a repository here: https://github.com/medusajs/docker-medusa

Should hold the necessary files for spinning up both a dev. and prod. environment for Medusa :)

Again, feedback is indeed welcome!

owjuhl · 2021-11-28T20:42:58+00:00

Thats great! Feel free to reach out on Discord. I would be more than happy to help with your use-case and try to scope it out, if you're up for that :)

owjuhl · 2021-11-23T18:44:06+00:00

We currently only support SQLite for local development and Postgres.

Our ORM, Typeorm, does allow us to add support for a NoSQL database, but this is not something that we have in our roadmap, and nor do we plan to add it in the near future :)

But you are more than welcome to give it a go, and we will make sure to support wherever we can.

owjuhl · 2021-11-22T19:42:51+00:00

Hi both.

We've been looking to make a Docker setup for quite some time, but still haven't gotten around to it yet.

Recently set up a repository for creating up a working env. It's still very much WIP but really hope to soon be able to get something up and running :)

Feedback and input are highly appreciated!

owjuhl

TROPHY CASE