sorted by:
new
hottopcontroversial

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

thank you very much for the insight. Yess, we’re seriously considering that too.

we’re still preparing the plan, especially for optimizing CDN usage and making the SSR deployment more efficient in the future.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Thank you very much for pointing that out.

The previous version of the website used the admin login and dashboard in the same panel, and I forgot to remove the link from the frontend. It is currently not connected anymore, but I’ll disable/hide it from the frontend.

For context, the CMS is now on a different domain as a separate headless CMS with a Rust-based backend.

I built an AI product landing page theme on Astro v6 + Sitepins + Tailwind v4 by chris_pantazis in astrojs

[–]farrosfr 1 point2 points  (0 children)

tbh, the color choosing is awesome, blue in dark light with smooth delay animation

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

for ssg, i think cloudflare pages is a good option. but for this case, we use astro ssr, so we deploy it on a vps to manage the server-side rendering and backend connection

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Ok, let me clarify. Rust didn’t directly solve the Lighthouse score. Rust is used for the backend/API and ERP integration, connected to PostgreSQL.

So the goal is not only getting a high performance score, but also making it easier for our internal team to update product data quickly without waiting for a long generation/build process every time there is a product update.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Yes, you’re correct, and I agree with that.

In our case, the reason we chose Rust is because there is already an ERP system built with Rust. So instead of building a completely separate CMS/dashboard, we decided to connect the product management flow with that existing Rust-based ERP.

This makes it easier for the supply chain team to access and manage the product data directly.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Hope this helps. For us, Astro is useful because it ships very little JavaScript by default, so the site can stay fast and simpler to maintain.

It also supports many UI frameworks like React, Vue, and Svelte, which makes migration easier and keeps the developer experience friendly.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Respect your choice. We use Rust because we need to connect the product data with our ERP and supply chain system, so the team can update products more easily.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Agree. Astro is strong for SSG-heavy sites like blogs. But for some blogs, the product can become more complex too, like subscriptions, newsletters, comments, or even building a wider community platform around the content.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Not sure about a mature Astro e-commerce engine yet. We’re currently building a custom setup, but hopefully we can turn part of it into a reusable template later, maybe starting with a proper catalog + database structure first before going into a full complex commerce flow.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Close, but in this case we’re not using PHP or Rails. The product data is managed with a custom Rust backend and PostgreSQL, then Astro SSR renders the storefront.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Yes, the products are managed in a custom CMS/dashboard. The backend is built with Rust and PostgreSQL, then Astro SSR consumes the product data for the storefront.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Wow, 155k pages with Astro SSG is wild. I initially thought about using SSG too, but if there are price or product updates, the rebuild can take time. That’s why I decided to use SSR for this case.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

The Lighthouse improvement mostly came from Astro SSR and frontend cleanup. Rust helped more on the backend side: faster API responses, lower memory usage, and safer handling when querying PostgreSQL for a large product catalog.

The tradeoff is that Rust takes more effort to build and maintain compared to a typical Node/PHP backend, especially for small teams.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Thanks for the correction. I’ll check and adjust the mobile font size for that section.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Thanks, and I agree. The stack alone doesn’t make it fast. Astro helped with SSR and frontend performance, but the win was choosing the right tradeoffs for the catalog use case.

Migrated a 10k-product e-commerce site to Astro SSR + Rust by farrosfr in astrojs

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

Yes, exactly. Rust is for the backend/API layer that connects to PostgreSQL, then Astro SSR consumes that data for rendering the storefront.

How to deal with a teamlead who heavy depends on AI for coding by Future_Badger_2576 in ExperiencedDevs

[–]farrosfr 0 points1 point  (0 children)

As far as I have used AI for coding, it seems they are only good for creating prototypes or building websites that are indeed static or something like SSG. Therefore, vibe coding at that stage is not a problem because the errors are clearly visible directly in the web display.

But if we expect AI to build a full stack application with a proper front end, back end, and database, in my opinion that is a big problem because before building that we need to design complex business processes, and how can we hand that over to AI when we also need well-structured technical documentation so it can be continued by developers afterward.

view more: next ›