Skip to content
markdown guide

Since you asked explicitly "Your ideal stack" as opposed to "the ideal stack," I can answer, as without context there is no ideal stack.

Yep, I agree!

My frontends are not "React Frontends" but "Frontends that use React as the View Layer," which in my mind is a subtle difference with huge implications.

This is an interesting approach, especially in the context of not letting your framework really control the way you want to build something. I like that.

Postgres - It allows me to combine several types of storage techniques in one system, especially allowing me to tackle problems using both JSON storage and Relational storage in the same query. As a bonus, it's fast, scales well, and is well supported.

Couldn't agree more on all of these points. When I start building features I fear might be out of reach for Postgres, it always reminds me just how powerful it is.

Any preferred method of deploying all of this?


I don't think I have an ideal stack.

I'm still rooting for boring technologies even if it seems everyone goes on the other direction.

I mean a monolithic app with server side rendered templates with some JS on top :)

Among the new kids on the frontend block I'm keeping an eye on Stimulus and StencilJS.

I'm also interested in seeing how Phoenix LiveView plays out and if any other community goes in that direction.

I'm not following the infrastructure world much TBH and I'm on the PaaS or serverless side :D

I really like PostgreSQL which is my favorite relational DB hands down, even if it's forever years old it's not boring at all ;-)

I wish I could play with CockroachDB in that space.

Classic DEV Post from Jan 24

What was your win this week?

Got to all your meetings on time? Started a new project? Fixed a tricky bug?

Lee Jarvis profile image
Software Developer, primarily Ruby and Elixir is where software developers stay in the loop and avoid career stagnation.

Sign up (for free)