Live data from Hacker News

Ask HN: Easiest way to build a CRUD app?

news.ycombinator.com

61–70 of 239 posts

Re: Ask HN: Easiest way to build a CRUD app?

#61

.NET, razor pages, sqlite, entity framework. Its hard to build anything non-trivial with a gui without involving a few languages these days. You can package your .NET server as completely self contained and run it on anything, just need a web browser. Edit: python might get you close with a simple html framework.

[deleted]

Re: Ask HN: Easiest way to build a CRUD app?

#62
You can't really have crud without "external dependencies" because you need to store state somewhere.

I'd say, figure out your storage layer (sql, mongo, files etc) then pick the right tech. Django and Rails will let you very easily bootstrap simple crud apps with very little code.

If you need CRUD API i'd personally go with Go and some db that i'm familiar with (pg). You can achieve tons with Go without any external deps.

Re: Ask HN: Easiest way to build a CRUD app?

#64

"Easiest way to build a CRUD app". Using the CRUD-app-building framework in which you are competent . Beyond toy apps there are no shortcuts without that competence but there are plenty of prospective frameworks to develop it in, as evidenced by the other comments.

> Using the CRUD-app-building framework in which you are competent.

That's assuming people already know one. If they don't, which would you recommand?

Re: Ask HN: Easiest way to build a CRUD app?

#65
I'm reading this as a CRUD GUI app. Definitely Ruby on Rails coupled with Avo (shameless plug).

It literally takes you less than an hour to create a realistic usable CRUD app (that would take you at least a few days in the traditional way) without learning anything new. Generate a DSL (a Resource) and add one line per field.

Avo knows how to read and display in a rich way, handle creating/updating records using your already in place validations, add associations in a giffy and one-liner file uploads. If the provided fileds are not enough you can create your own. The Rails developer can forget about building a front-ned for their admin panel/back-office area.

When you need to break out from the CRUD, Avo makes it easy using regular Rails code and erb templates.

Maintenance you say? There's no real maintenance here. You don't generate any templates for your CRUD interface, but write declarative code with plenty of options to create the best experience for your users. Avo is beautifully packaged away and will not pollute your app with business files (only configuration files). Everything is abstracted away in the background so you get easy-updates by running one simple `gem update avo` command.

Large teams will move in a uniform way building the same UI all throughout the app.

https://github.com/avo-hq/avo

https://avo.cool

Re: Ask HN: Easiest way to build a CRUD app?

#67

I would consider Django and just using its Admin framework for building your UI, you can achieve so much very quickly with almost no code. I believe it’s a brilliant tool for building internal CRUD type db apps. Knowing how to use the admin framework well is basically a developer super power. You won’t need any external libraries, it has brilliant docs and important tools like database migrations are built in.

Just want to add to what I said earlier, on the DB side which could be an external dependency, it doesn’t need to be. Django works super well with SQLite, again no external libs (it’s in the Python standard lib), and you should be able to handle a lot of traffic from a single sever with it.

I have in the past used Djangos built in “in memory” cache with a global invalidation on all db writes for simple apps like this that have a low write rate.

Re: Ask HN: Easiest way to build a CRUD app?

#68
I used to use Django for this kind of thing, but I have found that Flask connected to your fully managed database of choice like AWS with dynamodb (nosql db gets rid of even worrying about schemas) is the simplest way to quickly get up and running and do almost everything in Python with very little learning of various settings and details of specific frameworks since it is so minimal. This is how I tend to prototype then if there's anything promising I'll move to a better stack of tech based on the needs of the user (ex: is the end result going to be better as an iphone app, are there particular scaling needs that I need to worry about, etc.).
Post reply on HN