What to read on architecture design?
The current project at work has grown enormously and continues to grow.
It so happened that most were created by people who are no longer in the project. And the quality of the code of many components is often terrible. But it all works, users use all of this, and therefore Russian
“This is all good for nothing. It's easier to write everything again ”- not applicable.
The project is built on a bunch of tomcat, struts c java-server working with postgres. With the web part (tomcat) everything seems to be fine. In the server porridge - where the functionality itself to work with the database.
There is usually not enough time for a great refactoring and thinking about the architecture.
At the same time, new decisions / changes are made regularly and the iterative correction of the structure is quite applicable.
But somehow I'm not sure that the changes being made improve the situation. Rather, they do not worsen.
There is not enough experience in developing the right architectural solutions in the use of templates.
')
Therefore, I want to read something on the topic and give it to my colleagues.
Not that I fell off the moon. What kind of experience there is. And the books reread a lot.
But perhaps Habra-people will advise something most practical from your point of view, without a dry theory.
(in Russian, in paper form, on the topic: architecture, design patterns, refactoring, development of corporate applications) - something closest to the practice of developing a large, rapidly expanding system.
already have (read) on the topic or close:
- Refactoring. Fowler
- Perfect code. Steve mcconnell
- Architecture of corporate software applications. Fowler (good book)
- Any other identical books like “Developing corporate applications using UML, J2EE” from
Grady Bucha, etc.
It is interesting not something common from the RUP-type cycle of development processes, and specifically about the architecture
and deployment patterns, for example, specific commercial projects.
Thanks in advance for the comments.
It so happened that most were created by people who are no longer in the project. And the quality of the code of many components is often terrible. But it all works, users use all of this, and therefore Russian
“This is all good for nothing. It's easier to write everything again ”- not applicable.
The project is built on a bunch of tomcat, struts c java-server working with postgres. With the web part (tomcat) everything seems to be fine. In the server porridge - where the functionality itself to work with the database.
There is usually not enough time for a great refactoring and thinking about the architecture.
At the same time, new decisions / changes are made regularly and the iterative correction of the structure is quite applicable.
But somehow I'm not sure that the changes being made improve the situation. Rather, they do not worsen.
There is not enough experience in developing the right architectural solutions in the use of templates.
')
Therefore, I want to read something on the topic and give it to my colleagues.
Not that I fell off the moon. What kind of experience there is. And the books reread a lot.
But perhaps Habra-people will advise something most practical from your point of view, without a dry theory.
(in Russian, in paper form, on the topic: architecture, design patterns, refactoring, development of corporate applications) - something closest to the practice of developing a large, rapidly expanding system.
already have (read) on the topic or close:
- Refactoring. Fowler
- Perfect code. Steve mcconnell
- Architecture of corporate software applications. Fowler (good book)
- Any other identical books like “Developing corporate applications using UML, J2EE” from
Grady Bucha, etc.
It is interesting not something common from the RUP-type cycle of development processes, and specifically about the architecture
and deployment patterns, for example, specific commercial projects.
Thanks in advance for the comments.
Source: https://habr.com/ru/post/16485/
All Articles