We already do the calculation in a spreadsheet. What changes?

Where the calculation lives changes. A result in a file is carried into the sale by hand, and it loses its input at that moment. When the calculation is a layer of the system, the choice enters the record together with what produced it, so a figure questioned months later needs no hunting.

Our range is broad, more like hardware than a single family. Does this fit?

Fit is decided by whether a selection can be reduced to a rule, not by how many lines you carry. If the rule can be written, the calculation moves into a layer. If it cannot, the real job is making the catalogue easier to search, and we would call that a different piece of work.

Electric heaters look nothing like our trade.

They do not, and we write it that way. Resterm makes heaters, and the software was built onto its own product structure. What carries across is not the product but the direction of the input: the user enters the condition rather than the answer, and the software produces the answer.

Should you not come to the shop and see it?

We keep no office and do not work on site; everything runs remotely. What we need is not a room but a rule: which input produces which result, and in which case no selection can be made. Once those are written down, the calculation layer gets built.

System Architecture · Fatih

System Architecture for Fatih businesses

The person behind the counter finds the product from what a customer describes, not from a code: the volume, the ceiling height, where the door opens. While that knowledge sits in one head it is a physical bottleneck. Goods on the shelf do not help; the sale waits on the calculation. Software architecture consulting in Fatih asks where that knowledge should sit. Calculator Resterm moves it into a layer of the system. The input becomes a heating requirement, and the output is not advice on a screen but a selection that drops into a basket.

Get a quote Tell us about your project

System Architecture — Fatih

Fatih's fabric leans on the wholesale food and hardware trade around Tahtakale on the historic peninsula, and on guesthouses and hotels. If your line count runs high, or demand changes with the room itself, what finds the right product is not a catalogue but what one person knows. The closest work to that condition is Calculator Resterm. Where it does not overlap comes first: written for electric heater manufacturing, it holds no purchasing and no production planning, and we have nothing to show for a wholesaler's ledger or a hotel's front desk flow. What travels is where the calculation is placed. The stack is narrow: Laravel carries the calculation and the records, MySQL holds project and customer rows, Vue the interface.

The input is the requirement itself rather than a product code, so the engineering calculation stands as a layer of the system and searching a catalogue drops out.
The result does not stop at the screen: the chosen heater falls into a basket, the basket attaches to a project, and the project to its customer.
The software was not made by bolting a catalogue onto a general quoting tool; the manufacturer's own product structure became the ground of the data model.

Why Algoriel

The parts read one source

At Tahlil.com the site, the admin panel and the mobile app read the same information instead of behaving as three systems.
Where each job is solved comes first

Which layer handles which job is decided before code, because work that has to move later is expensive to move.
The summary recomputes itself

As the Günlük Hava Durumu archive grows, the climate summary recomputes from it; nobody maintains a monthly table by hand.
One rule for file layout

On the KGM SsangYong site, where a file is written and under what name now follows one rule the upload code obeys.

Where the data divides

When several institutions share one system, each enters through its own domain and student, guardian and payment records stay inside that institution's boundary. This arrangement is what the term multi-tenant describes.
What a record attaches to

Whether service history is written against a person, an address or a device is settled before the schema exists. Reversing that later means re-attaching everything already recorded.
Permission held in the data model

A teacher, a guardian and an institution administrator reach the same timetable record at their own level of access. Permission is part of how the record is defined, not a view switched off on a screen.
Splitting the read path

Which screens are served from a held copy and which go to the database is settled before the first record exists. On Vipkurum a frequently opened screen comes from the copy, and only a read with no copy reaches the database.
Interfaces on a single system

Tahlil.com hangs three interfaces off one system: the patient site, the physician panel and the mobile app read the same record, and no second data model is written per interface.
Storage laid out on day one

The naming and folder scheme files will live under is fixed at the start; a layout imposed afterwards turns into a migration.

Work like this

System Architecture · Case study

Calculator Resterm — the calculation is a layer, its result lands in the record

A user enters a heating requirement, not a product code, and the software runs the engineering calculation and picks the heater. The choice does not stop at the screen: it drops into a basket, the basket attaches to a project, the project to its customer. Nothing is retyped between technical selection and commercial line, so a quotation still reads back to its input months later. We built it onto Resterm's own product structure, not a catalogue fitted to a generic quoting tool. Laravel carries the calculation, MySQL the project and customer rows, Vue the screen.

Read the case study →

Working with Fatih teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

The first release ships as a working piece; extras follow later.
Every client we know of is in Turkey.
Decisions stay in writing; progress shows in working screens.

Frequently asked

We already do the calculation in a spreadsheet. What changes?

Where the calculation lives changes. A result in a file is carried into the sale by hand, and it loses its input at that moment. When the calculation is a layer of the system, the choice enters the record together with what produced it, so a figure questioned months later needs no hunting.
Our range is broad, more like hardware than a single family. Does this fit?

Fit is decided by whether a selection can be reduced to a rule, not by how many lines you carry. If the rule can be written, the calculation moves into a layer. If it cannot, the real job is making the catalogue easier to search, and we would call that a different piece of work.
Electric heaters look nothing like our trade.

They do not, and we write it that way. Resterm makes heaters, and the software was built onto its own product structure. What carries across is not the product but the direction of the input: the user enters the condition rather than the answer, and the software produces the answer.
Should you not come to the shop and see it?

We keep no office and do not work on site; everything runs remotely. What we need is not a room but a rule: which input produces which result, and in which case no selection can be made. Once those are written down, the calculation layer gets built.

System Architecture in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Let us settle where your data divides before any code is written.

Get a quote or open the service

System Architecture for Fatih businesses

System Architecture — Fatih

Why Algoriel

The parts read one source

Where each job is solved comes first

The summary recomputes itself

One rule for file layout

What we build

Where the data divides

What a record attaches to

Permission held in the data model

Splitting the read path

Interfaces on a single system

Storage laid out on day one

Work like this

Calculator Resterm — the calculation is a layer, its result lands in the record

Working with Fatih teams, remotely

Frequently asked

We already do the calculation in a spreadsheet. What changes?

Our range is broad, more like hardware than a single family. Does this fit?

Electric heaters look nothing like our trade.

Should you not come to the shop and see it?

System Architecture in other cities

Ankara

Istanbul

Izmir

Let us settle where your data divides before any code is written.

System Architecture for Fatih businesses

System Architecture — Fatih

Why Algoriel

The parts read one source

Where each job is solved comes first

The summary recomputes itself

One rule for file layout

What we build

Where the data divides

What a record attaches to

Permission held in the data model

Splitting the read path

Interfaces on a single system

Storage laid out on day one

Work like this

Calculator Resterm — the calculation is a layer, its result lands in the record

Working with Fatih teams, remotely

Frequently asked

We already do the calculation in a spreadsheet. What changes?

Our range is broad, more like hardware than a single family. Does this fit?

Electric heaters look nothing like our trade.

Should you not come to the shop and see it?

System Architecture in other cities

Ankara →

Istanbul →

Izmir →

Let us settle where your data divides before any code is written.

Ankara

Istanbul

Izmir