If there is no front-end — how do you feel about it?

The absence of a frontend can be justified in certain cases, for example, if the system is intended only for internal use via API, or if the frontend is implemented separately by another team or service.

However, from a systems analyst's perspective, it is important to understand that the lack of a frontend changes the requirements for the API, documentation, and user interaction. It is necessary to provide convenient and understandable interfaces for integration, as well as to consider how users will interact with the system through other channels.

If there is no frontend, more attention should be paid to:

• Quality API documentation
• Testing and stability of the backend
• Monitoring and logging

Overall, the approach depends on the project context and goals, but the absence of a frontend requires more thorough development of the backend and communication with service consumers.