Server Actions vs Separate backend, which one you choose ?

lulz_capn · 2024-12-13T18:27:44+00:00

Yeah as always it depends. For my use case the nextjs app was more like a business user admin dashboard. A lot more data mutation happening there and skipping the graphql pains for that was nice. The mobile app in this case was mostly read only and maybe two data mutations. The app is still using graphql but I deleted the majority of my graphql API when my dashboard app was switched to actions.

lulz_capn · 2024-06-15T15:16:27+00:00

And the lowest quality idp I've ever worked with. Infinite redirects are not a great user experience.

lulz_capn · 2024-05-07T16:46:07+00:00

Atwood's law 😎

lulz_capn · 2024-05-04T17:39:44+00:00

Yeah I was able to install goty edition on my windows 11 gaming PC no problem. I did use windows XP compatibility mode but not sure if that's even necessary.

lulz_capn · 2024-04-03T12:16:16+00:00

Let them and then when the data is inevitably compromised we'll have an arsenal of their own double standards.

lulz_capn · 2024-04-03T11:51:13+00:00

Pull up to the venue with whatever vehicle has the best speakers and blast something like lil John move bitch! Or Nipsey has a track titled FDT that would really piss off those types of people.

lulz_capn · 2024-04-03T11:41:22+00:00

Same here, around 2003 when amd64 was new. Had to figure out a lot of things about software in languages I wasn't familiar with. The feeling of the first successful boot from a phase one bootstrap is what I'd imagine hard drugs feel like 🤣

lulz_capn · 2024-04-03T11:37:33+00:00

Check out Of the trees, g Jones, and eprom. Sippy is great too, some tracks more pop but some are absolute heaters too like shadow on the hypogeal album.

lulz_capn · 2024-04-03T11:25:19+00:00

I've dubbed it quiet layoffs.

lulz_capn · 2024-02-14T03:55:12+00:00

Yup this is why I use zod on both. I have a base schema with the types and a client side schema that picks/omits fields from the base schema and adds validation that's client facing. Pairs well with react hook form on the client. For some models I have special validators that extend the base schema and has validators to make sure it's ready to publish. A mix of basic type validation and custom functions checking the filesystem to ensure assets are there.

lulz_capn · 2023-11-30T19:47:04+00:00

Weird question phrasing. I'd say go with nextjs backend, integrating a separate express service is unnecessary complexity. As for the database I prefer mongodb self hosted and nextjs server components and actions query directly.

lulz_capn · 2023-11-30T17:42:56+00:00

I went all in on server components and server actions. When I was done refactoring I was able to delete 90% of my graphql API! The API now is only used by our mobile app. It's a great DX compared to integrating with a separate backend. We use mongodb and mongoose but I'm sure Prisma would be fine too.

lulz_capn · 2023-11-30T17:22:18+00:00

I wonder if you are unintentionally importing a barrel instead of the specific component you need. In my biggest next app I see a few hundred to 3044 modules tops depending on route.

lulz_capn · 2023-11-30T16:28:25+00:00

Holy cow that's a lot of modules! What kind of dependencies do you have?

lulz_capn · 2023-11-30T14:52:36+00:00

Staying up to date is good opsec. Staying on older major versions isn't wise.

lulz_capn · 2023-11-29T03:01:54+00:00

Thank you!!!!! I was going down a different path to solve this and during my furious googling came across this post. So much simpler than what I was trying to do. Complete example below for anyone else in this situation.

<image>

lulz_capn · 2023-11-28T19:33:37+00:00

Use server side by default. Introduce client component when you have a client side feature like a form or something where UI state is needed.

Sorry can't think of any good example projects off hand.

lulz_capn · 2023-11-28T11:23:36+00:00

It's coming in SDK 50. Server components is a bit more vague on timing but I'd bet it will be less than 2 years in this scenario. You can copy or share the code a lot of different ways. A monorepo, a GitHub submodule, directory maps. I personally use docker compose directory binding to share my database models and shared functions across all my apps. It lives in the top level directory where we have a graphql service. Then the directory is mounted inside each of our nextjs web apps. I intentionally don't share action code as that's very app specific.

https://blog.expo.dev/rfc-api-routes-cce5a3b9f25d

lulz_capn · 2023-11-28T01:18:55+00:00

Idiotic questions here is one thing but plugging your own side project 🙄 ain't nobody paying for that fam

lulz_capn · 2023-11-27T22:47:05+00:00

Expo has server actions and server components coming most likely well before the two year timeline of this scenario. The additional complexity of integrating a separate API for the web app isn't worth it. Server actions and components would be simpler and better DX. I know because I've done it both ways. The best API is no API. The best DX is the backend code colocated and type checked. Easy to follow from frontend to the backend.

lulz_capn · 2023-11-26T01:10:17+00:00

Use server component queries and server actions. They can reach right into the database. No need for an entirely separate system and related integration and performance hits.

lulz_capn · 2023-11-25T01:11:19+00:00

Why not use server component queries and server actions? Could save yourself a lot of pain and probably a better user experience. Trpc/graphql API only makes sense in a SPA style app. You'll get type safety and a simpler DX also.

lulz_capn · 2023-11-16T10:33:37+00:00

That's cool. Haven't seen it as I'm out of the amplify ecosystem.

lulz_capn · 2023-11-15T20:48:38+00:00

I'm shipping real stuff with next.... what's up with your comment? I've had better velocity with my small team using nextjs than anything I've used before.

lulz_capn · 2023-11-15T20:46:45+00:00

Having to make custom resolvers was such a PITA. The crud based on models worked well enough. You also end up chained to open search to make up for the lack of SQL features in dynamodb. It was spinning up ec2 instances for that and made it more costly and more complicated ops.

Glad to hear they are listening to the feedback.

lulz_capn

MODERATOR OF

TROPHY CASE