Ask HN: What stack would you use to build a CRUD web app in 2018?
31–40 of 184 posts
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#32The boring Java enterprise way, 2018 edition. Back end: Java 9 JVM, Spring Boot web service, Kotlin, plain SQL via JdbcTemplate working with Kotlin data classes, Liquibase for DDL and migrations, Spring caching with redis if need be, Postgres, deployment via docker to AWS Fargate Front end: Angular... but I’d like to try Vue. Nginx and docker to Fargate
I cannot wait for full ES6 support in vue - it will get massively better by then.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#33- Neo4j graph db instead of a relational db. Simple crud stuff is easy, and you can encode most business logic (if there is a need for anything beyond basic crud) as simple graph operations, avoiding the need for a bunch of other boilerplate that is found in frameworks that leverage ORMs.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#34Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#35Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#36Full stack Dart.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#37As an entrepreneur however, I would opt for Wordpress unless there's a clear, strong reason not to. I know it's a bit heretic here on HN, and I dislike PHP and working with Wordpress isn't fun at all. But they take the concept of "Batteries included" to the next level. It's like "Nuclear power included".
You want a simple and powerful admin backend? got it. Caching? check. Image optimization? Yup. Logins? of course. Payment/Shopping Cart/Even subscriptions - just get woocommerce. 5 minutes later you're charging credit cards or paypal. Not to mention how easy it is to create content pages, landing pages, blog posts... You know, the stuff that actually convinces people to even consider your shiny new app.
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#38Design frontend in web or mobile with poison of your choice
Re: Ask HN: What stack would you use to build a CRUD web app in 2018?
#39Twenty 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?
#40The 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.
100% agree - unless you're doing anything especially novel, or know you're getting 10's of millions of connections from day 1, with the ecosystem around it, I wouldn't hesitate choosing Rails + Postgres + Redis + Sidekiq.