backend : ratpack + java + kotlin + ebean (sql orm) + postgresql
frontend : VueJS
Ask HN: What stack would you use to build a CRUD web app in 2018?
21–30 of 184 posts
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#22http://www.hyperfiddle.net/ (Karl and I made this)
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#23Twenty years ago, a simple CRUD app would have been written in Visual Basic or Delphi. It would have needed one programming language, and one framework. The tool support would be good: everything would talk to everything else. Heck, you'd even have an IDE with autocomplete! Today, a typical web app requires no fewer than five different languages (JS, HTML, CSS, Python/Ruby/whatever on the server, SQL). And that's bef…
Anvil looks awesome.
I do really enjoy making apps with the modern web stack, but when I look at how many moving pieces are required to make something simple, I do start to wonder if it's all a bit pants-on-head crazy.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#24Great question. The funny thing is, 6 years ago, if you'd ask the same question (and I'm guess that's what you're coming from) the go-to answer on HN would've been Rails / Django something. Where both will allow you to build a basic crud app in 20 minutes.
Since then, everybody has gone heavily into various javascript stacks, and the norm has become to deal with 20 different packages to build (somewhat) the same thing. And the first hour will easily be spent researching different dependencies, trying to get them all to work how you'd want etc.
It's easy to see this as a horrible backwards progression, but the reality might be a bit nuanced.
The easiest way to get a basic crud app up and running these days is probably still some sort of rails/django stack. But today's requirements in terms of UX / dynamism (is that a word?) require you to end up building things differently, so even if you get up and running fast with a rails app, you'd end up having to build up a pretty hefty JS stack in the end, so you'd basically be delaying the inevitable.
So the answer really depends on what level of "good enough" you're going for.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#25If the application is going to be around longer than 5 years, roll your own MVC or ROA pattern in Java. Write your own DAO and database calls (stay away from ORMs). Keep 3rd party library use down to a minimum, limiting your vulnerability exposure and rewrites due to upgrades.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#26[deleted]
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#27Use what you know. In my case, probably ASP.NET Core and either SQL Server or PostreSQL.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#28The same as 4 years ago. Server side rendered templates with Rails or Flask using Postgres + Redis + background worker of choice. I'm starting to build some apps with Phoenix now, but it's not because I feel the above 2 are poor choices. I just like learning new things, especially when I see big wins of potentially using it. It's another tool in my tool belt, not an all-in replacement of the previous thing.
99% agree. I just don't feel like using Sidekiq or Celery anymore for short lived jobs when I can do it without any additional infrastructure using Elixir and Phoenix (same for websockets.) However anything else is easier with those older languages including deployment, especially for Rails (capistrano or mina.)
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#29Rails + Postgres
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#30I would go with PHP+mySQL/PostgreSQL maybe some Redis for good measure.
What PHP framework to use in 2018? Fat-Free Framework, of course.