EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

System Architecture · Esenyurt

System Architecture for Esenyurt businesses

A business that produces a new record every day sees its page count grow whether anyone touches it or not. If the person who would write those pages is also the one standing at the counter or in front of a class, a hand-edited summary page carries its own staleness date. Software architecture consulting in Esenyurt starts from the decision underneath: which value is stored and which is computed. On Günlük Hava Durumu the summary was never written as text at all: it is computed from the day records in the archive, and it renews itself as the archive grows.

Get a quote Tell us about your project

System Architecture — Esenyurt

Esenyurt's fabric leans on small businesses, multi-branch operations and private education, where one name can stand in several buildings. Producing content in that shape is not a desk of its own but extra weight on whoever already runs the work. The closest work to that condition is Günlük Hava Durumu. Where it does not overlap comes first: written for weather and climate data, it never held branch management, course enrolment, collections or stock, and we have nothing to show on warehousing or wholesale dispatch. What travels is a single architectural decision: which value is stored and which is computed. Laravel prints the pages, day records live in MySQL, and React carries movement in the interface.

  • The summary is not a separate data source but a read over the archive, recomputed the moment a new day lands in it.
  • The record keeps three states apart: the forecast on air is overwritten, the day that passes is written once and never edited, and the summary is derived from both.
  • Every date and location breakdown publishes at a permanent address of its own, so a deeper archive never forces the page structure to be rebuilt.

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.

What we build

System Architecture

  • 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

Günlük Hava Durumu — the summary is a read over the archive, never hand-edited

Three content types form one chain. The forecast on air refreshes, and the value shown is overwritten by the next update; once that date passes, the same record is handed to the archive and never edited again. The climate summary is no fourth source: it is computed from those archived day records and renews itself as the archive grows. Every day of every location publishes at a permanent address of its own, so a deepening archive never forces the page structure to be redrawn. Laravel prints the pages, day records live in MySQL, React carries movement in the interface.

Read the case study →

Working with Esenyurt 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

  • Would writing the summary by hand not give us more control?

    It would, once. A hand-written summary describes the day it was written, and the text falls behind the moment the archive grows. A computed one refreshes as soon as a new record lands, and nobody has a task in their calendar.

  • Does opening a page every day not bloat the site?

    Bloat happens when the pages are empty. Here each address carries one day's measured record, so content is produced rather than copied. The structure stays fixed too: a new day is a new record on the same template, not a new template.

  • Our branches publish separately. Does this shape fit us?

    The breakdown does not have to be date and location; what matters is which axis earns a permanent address. Once that axis is chosen, the record is written once, and the only thing ever overwritten is what has not settled yet.

  • What happens when a past record has to be corrected?

    Correction is a separate decision. An archive record is written once by design, so a correction is built as an explicit action rather than a quiet overwrite. Which values are fixed and which move is something we write down before any code.

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