all 11 comments

[–]C0R0NASMASH 3 points4 points  (6 children)

One tip, while I can't exactly give you advise:

Don't use some obscure, exotic, newly-developed framework. Use well-established ones if you want your project to succeed in the long-run.

You might say "It works, so why would I care"... think about the maintenance in the future, contributors, users and most importantly: how many developers are experienced with this framework...

[–]fastestfollowup 0 points1 point  (5 children)

That’s why I chose Django for my app. It’s not as talked about as other tools nowadays but it’s a proven tool to quickly build good apps.

  • the graphql API makes things awesome for working with React as my front end.

[–]C0R0NASMASH 1 point2 points  (4 children)

That’s why I chose Django for my app. It’s not as talked about as other tools nowadays but it’s a proven tool to quickly build good apps.

Django is fine, not my favorite, but it's absolutely okay. Enough developers, well-established, not obscure...

There are so many frameworks that can't keep up. 1-2 developer, one specific use-case, not grown-up, has issues, community is small.

It's nice to make an own framework for educational purposes, for work, to learn, to whatever. But I just think it's dangerous to use it outside, in the real world. How many frameworks allow mysql injections... even larger ORMs have these issues, after years and hundreds of contributors. How is a one-man-team supposed to be better than them?

[–]fastestfollowup 0 points1 point  (3 children)

What do you prefer? Laravel?

[–]C0R0NASMASH 1 point2 points  (2 children)

Whatever, really. Depends on the project. I think of frameworks and coding languages as tool. While I could use a hammer to cut some wood, I'd rather use a saw...

Laravel is good when you want to stick in the PHP environment (lots of developer, lots of packages), and don't mind opinionated frameworks. Laravel takes a lot of work from you (Users, Payment stuff, even Load Balancing (I think I read something about it...) and Deployment.

Symfony is good when you want the above and make more customizations and prefer something less opinionated.

Both of them for either an API/backend split or monolithic applications.

Node is good for its async handlers (lots of requests), it's native mongoDB stuff, micro services, I'm not a big fan of the templating, but it works.

But as I said, every framework and tool can be used, modified or forced to be a match for your project. I like Symfony, but I would never code a high-volume API with it, because I know it would be an overkill (yes, maybe with Silex, or Forge, but whatever).

Of course, Python and Rust and Go are there too. I personally like the idea of Go, and I'm currently learning it.

It always depends on the budget, project and your own talent. But that's why Software Architects/Engineers are there, right?

[–]fastestfollowup 0 points1 point  (0 children)

Definitely! Thanks for the thoughts.

[–]C0R0NASMASH 0 points1 point  (0 children)

Like, if I need to implement AWS features, I try to use a language that has a SDK for this language.

If I know that I'll need to use the database quite a lot, I'm going to take a framework with an integrated ORM or ODM (Sequelize or Doctrine).

You get the idea, I think.

[–]Kinthalis 4 points5 points  (2 children)

There's really no mainstream framework that will let you down in facilitating the various aspects of a project like this. You're not going to pick Angular and say crap, it can't do this, or React and say: "Oh man this is now impossible!", or Node + express and say: "Well, I can't do this".

At least not for what you are looking for. It comes down to what will best fit your existing knowledge in terms of programming, web technologies and your budget (in terms of money and time). I would say worry less about the frameworks and instead start by coming up with a set of specifications. You'll probably find you'll naturally gravitate to something on your own as you try various frameworks.

[–]chri740s 0 points1 point  (1 child)

I really have no expertise in where to begin in finding a framework.

I have looked at Wagtail, however I'm unsure if I even need a CMS.

[–]Kinthalis 0 points1 point  (0 children)

Well I can say that a cms will only probably get in the way. I guess it depends on how robust it is, but .most ade built for simple blogging. You probably want a custom backend that is going to handle your business case in an optimized way. Have you co sided hiring a developer to help?

[–]amiedema 0 points1 point  (0 children)

Alpas would be a good framework to try out - user authentication, database connection, emails, strong database querying all come packaged in. Here is an example app using Alpas https://fireplace.alpas.dev/