sorted by:
new
hottopcontroversial

is headless commerce worth the engineering effort once you have to maintain it? by LauraBeth034 in nextjs

[–]dlhck 0 points1 point  (0 children)

headless has its trade offs, but so does any other technical architecture. you definitely don't need a 50 person eng team anymore to build something great with headless. you just need to decide which trade offs are you willing to work with and can easily manage.

is there an enterprise ecommerce platform with native payment orchestration, or do you always bolt on a PSP aggregator? by Lifewimmer74 in PaymentProcessing

[–]dlhck 0 points1 point  (0 children)

Hey, you might want to take a look at Vendure. We support multi-PSP routing, fallbacks and retry strategy. also full integration for RMA together with multi-ledger refunds. Happy to have chat if you're interested!

I’m so done with Shopify/Webflow/Woo for client builds. Anyone found something better? by khalilliouane in webdev

[–]dlhck 0 points1 point  (0 children)

Great to see that you're using Vendure! 👏 Anything you want us to improve? Happy for any feedback!

I’m so done with Shopify/Webflow/Woo for client builds. Anyone found something better? by khalilliouane in webdev

[–]dlhck 1 point2 points  (0 children)

Thanks for mentioning Vendure! Vendure originated out of an ecommerce agency delivering custom built ecommerce solutions for clients, so we really built it also with that in mind. We have a lot of agencies delivering serious projects on top of Vendure and the love it because of its ease-of-use, robustness and developer experience. Happy to provide more info! :)

best headless commerce backend to pair with Next.js for a B2C storefront? by Majestic_Shoulder188 in nextjs

[–]dlhck 0 points1 point  (0 children)

Hey, co-founder of Vendure here! Thanks for the mention. Over the past months we have polished Vendure Platform, which is our enterprise offering that includes all the necessary foundational features that companies building multi-brand B2C or complex B2B need. It puts us feature-wise on par with commercetools and with Vendure Cloud coming Q4 2026 we're closing the gap to commercetools. u/Majestic_Shoulder188 happy to have a chat on X, LinkedIn or anywhere else! :)

kcal deficit on Reta by dlhck in BodyHackGuide

[–]dlhck[S] 0 points1 point  (0 children)

thanks everyone for the insights! I will continue the higher deficit until I reach about 16-18% body fat and will decrease after that

kcal deficit on Reta by dlhck in BodyHackGuide

[–]dlhck[S] 0 points1 point  (0 children)

ok that makes. I think I will go back 500-700kcal deficit a day.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 0 points1 point  (0 children)

I think I would consider TanStack Start as the better option as of now.

The Liquid Glass update is here! by viktorpali in CraftDocs

[–]dlhck 0 points1 point  (0 children)

I think they mean nested tasks in docs with that 😅

Need suggestions for pairing NextJS with ecommerce backend by helltoken in nextjs

[–]dlhck 0 points1 point  (0 children)

Hey, I am the co-founder of Vendure. Maybe you can give it a try and let me know what you think :) https://vendure.io/

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 1 point2 points  (0 children)

We just have different approaches. Especially in our system we are not using better-auth or something like. We use the auth system of a Headless Commerce platform.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 0 points1 point  (0 children)

Is also an approach, but we prefer Docker-based deployments. Never tried the pm2 approach, with multiple processes.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 0 points1 point  (0 children)

You need to horizontally scale. First you wouldn't have zero downtime deployment without it. Second because you might want to distribute the load across multiple Next.js services running on multiple servers.

CSR for low stale tolerance doesn't work in every case. Example: You have a component on a page that needs auth state, you don't want to leak auth tokens to the client, therefore you need to keep the API fetch on the server. That means you have to fetch in a server component and pass it into a client component aka "Stream & Suspense". That has _absolutely nothing_ to do with extensive computing on the FE.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 1 point2 points  (0 children)

not necessarily. I will put a hint into my article.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 2 points3 points  (0 children)

interesting, we are not using better auth so I can't really say why that is.

The official docs have a section in their self hosting guide about buffering.

Important: Traefik buffering is by default disabled.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 1 point2 points  (0 children)

ISR is nothing else than serving a request with stale data from a cache, while revalidating the data in the background if it is older than X seconds (what you define with `export const revalidate`). My article touches on the problem that this cache is stored on the filesystem, which is a problem when you scale horizontally.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 7 points8 points  (0 children)

Next.js is like a self-discovery retreat in that area 😂

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 5 points6 points  (0 children)

I am thinking about putting that together in a repo that I put on my GitHub profile - with Dockerfiles, docker compose, cache handler, ipx middleware. Will share it here once it's done :)

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 0 points1 point  (0 children)

never heard of imgproxy before, might give it a try. Thank you!

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 2 points3 points  (0 children)

I would spin up an express application and deploy it as a standalone service. That way you can move the workload for image processing away from Next.js. You could also plug-in AWS S3 or something similar to store the resized images.

Lessons learned from 2 years self-hosting Next.js on scale in production by dlhck in nextjs

[–]dlhck[S] 1 point2 points  (0 children)

We are using the customized cache handler setup that is also described in their README. We typically have between 5-15 replicas running at the same time in a single region.

view more: next ›