What structure do you recommend for quick protection of web application development?

I need to choose a structure for a new project, which I will start from scratch. Application performance requirements are very low. This is necessary for rapid development and ensuring good development practices. The final application should be easy to deploy and well migrate database migrations.

The application will handle most of the time simple CRUD operations for a specific domain. It must be very safe. In the long run, I will need to confirm its safety. I have experience programming in PHP and now I work as a Java developer.

A language is not important for a structure if it meets the requirements set forth above.

+4
source share
7 answers

Starting with php and recently switching to rails, I have to say that rails certainly apply “best practices”. The nickname for rails is not an accident. It follows the rigorous Model-View-Controller paradigm that makes it easy to do the right thing. There are already many things that you probably always planned to do, but never came as an easy way to switch between production / development / testing environments, each of which has its own characteristics (i.e., during testing and development, emails do not send, but register). The migration infrastructure simplifies the deployment of modified models (database structures).

None of these ideas can be reproduced in other frameworks, and I assume that many of them have already done so. But overall there is a level of completeness and attention to detail that I have not seen before. Ruby, a language you need to get used to, but it's pretty elegant compared to php.

As far as security is concerned, perhaps your job is basically. Sanitizing input etc. Rails has built-in mechanisms to help you with this, but I believe that any other structure also exists.

+7
source

Django is the way to go. You can even post your killer app here!

+8
source

I suggest ASP.NET with MVC . Use NHibernate / ActiveRecord Lock to access data. This would mean a Windows server that has many temptations in authentication / authorization schemes.

+3
source

For PHP, I used Zend Framework, CodeIgnitor and CakePHP (only to support an existing CakePHP project).

Zend was huge. It had a lot of functionality, and I liked how you do not need to follow the MVC pattern (good for existing projects, but probably not for you). However, I would recommend it only for large projects. If he is small, Zend is overkill.

CodeIgnitor was a good, very similar Rails. I have not used it for a long time, since the project was transferred to another team, although together with the CakePHP project.

+2
source

@Matt Winkelmann: I like Rails, but there is no support for this on shared hosting, but the community behind this is growing. I do not think he is ready for prime time, but he is approaching very quickly.

+1
source

A friend also recommended choosing a ruby ​​on rails. I think it will be so. As for the server configuration, I have complete freedom, so I can satisfy any infrastructure requirements.

@Alexander I posted SO before posting a question. The question about php structures was too specific for me.

Thanks for the quick answers.

+1
source

If you want to stick with Java, I recommend taking a look at Tapestry .

To get an overview of all the Java options in the world, there is a fairly general overview of the two main camps and different options from one of the JSF guys (Kito Mann) at about 8:40 in Java Posse episode 203 .

0
source

Source: https://habr.com/ru/post/1276545/


All Articles