Skip to content
Piar Concept
Piar Concept

Frequently asked questions

What does Clean Architecture bring to a project?

Clean Architecture separates business rules from the interface, database and external services. We apply it to limit how much technical changes affect the behaviour a business needs to preserve.

For example, approving an order may depend on credit limits, permissions and availability. These rules should be understandable and testable without opening a screen or connecting to an ERP. The screen requests the operation, while adapters connect the use case to the systems it needs.

This makes software with complex rules easier to maintain and evolve. We adapt the separation to the project: a small application does not need as many layers as a platform spanning multiple business areas and integrations.

More questions

What does Piar Concept do?When does custom software make sense?What does software architecture contribute to a business?Can you integrate ERP, CRM and other APIs?Which internal processes can be automated?Can you work on existing software?How do you approach applied AI?Do you collaborate with UX studios and consultancies?How much does a project cost and how long does it take?What do you need to assess a new project?What is the Piar Turbo Template?How do we adapt the template to each business?Why use a monorepo for multiple applications?How do we organise software around business areas?How do we keep an integration from shaping the entire system?What is a BFF and when does it make sense?How do we verify business rules and integrations?How does this architecture translate into real projects?How do we prepare an MVP to evolve?
Reading guide · Markdown
What does Clean Architecture bring to a project?