The software architecture is very attractive for many developers. But an architect and architectural processes are perceived as an excess for many small companies.
But the nature abhors a vacuum and the architecture develops spontaneously. Sometimes it is bad, heavy and can interfere with the project development.
In this track we will discuss:
- Architectural methodologies and their practical application
- Architecture enhancement and introduction of architectural processes
- Practical benefits of having architects; when his presence is beneficial and when it is not. The architecture for startups.
- Teaching architecture. Do we have schools for architects? Is it possible to teach architecture to students?
We invite practitioners and theorists to submit their reports and to take part in hot disputes. We will be glad to consider all opinions, and positive or negative experiences of architectural solutions.
Related submissions
- PTP support with FPGA. Fullstack (hardware/software) development
- In-Stream Processing blueprint: building cloud ready, enterprise grade reliable and scalable, 100% open source service
- About SOLID principles: mathematical proof and software constructions that violate SOLID
- Fast Online Access to Massive Offline Data at LinkedIn
- The evolution of computing system’s remote control ideology from PICMG/IPMI to RedFish/OData
- Streaming matching of events
- Process and Case Management in software: from support As Is to Business Development
- Virtualthreading: New computers meta-architecture for direct fine-grained hardware multiprogramming
- YoctoDB @ Yandex.Classifieds
- Reasons and example of why open source projects are a next step in collaboration of universities and IT companies.
- How does hh.ru serve 90 mln pictures and keeps drives spinning
- Solving a Rubik’s cube: how to recover the architec-ture description of distributed enterprise system
- Design Thinking for Software Developers