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 · Tuzla

System Architecture for Tuzla businesses

An hour is set aside, and then nobody comes to it. In Tuzla's shipyard and heavy industry pattern the reason need not be carelessness: inside an enclosed steel volume a phone finds no signal, nobody steps out before the shift ends, and word arrives once the hour has already passed. That is where the question starts at the desk: does late word count as calling off, or as not turning up? A business that settles this in conversation answers the same situation two ways. Pilatesco settles it in the record.

Get a quote Tell us about your project

System Architecture — Tuzla

Shipyard work and heavy manufacturing here cut a day into shifts rather than hours, and an hour given up is not filled again the same day. The condition closest to that in our portfolio is Pilatesco. The gap is worth naming: Pilatesco was written for a sports and fitness business, and production planning or shift timekeeping for a yard is not work we can point to. What we take from it is not the studio but where the balance hangs and how states are written into a rule. Laravel runs the process and MySQL holds packages, bookings and customers; the remaining pieces of the stack join the same install only when a problem asks for them.

  • What is left of a package sits on the customer's own record rather than a ledger kept beside it, and the hour set aside takes one right off it as it enters the record.
  • Word given in time, nobody turning up at all, and a session completed do not reach the same place in the balance, and which of them gives the right back was written into the rule beforehand.
  • Money arrives once while use spreads across later weeks, and because both are read off one record, no second ledger waits to be reconciled at month end.

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

Pilatesco — the balance sits on the customer record, the rule decides its states

A booking and membership system for pilates studios. How many people a slot opens to is decided by the instructor, the equipment and the hour together. A customer buys a package; what remains travels on their own record, and an hour entering the record takes one right off it. Word given in time, an absence with no word, and a completed session each land differently on that balance, and which of them gives the right back was fixed in the rule beforehand. Money arrives at the sale while use spreads over later weeks. Laravel and MySQL carry it, and the scope is one business.

Read the case study →

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

  • What happens when word that a slot is being dropped arrives after the hour has passed?

    Whatever the rule says. The name of the state sits on the record: word given in time and an absence with no word do not land in the same place on the balance. Because the line was drawn beforehand, late word is not argued over at the desk.

  • Could we not hold capacity as a single headcount?

    You could, and it would fill the wrong hour. On Pilatesco a slot's capacity comes from the instructor, the equipment and the hour together, and if one of the three is not free the slot never opens at all.

  • We are not a sports business. What does this say to us?

    Pilatesco was written for sports and fitness, and we say so plainly. What carries across is not the studio but the shape of the record: a right sits in a balance and a state moves it by rule. Call the balance an entitlement instead of a class credit and the chain holds.

  • How do you set these rules without coming to the site?

    We keep no office and work fully remotely. What we build first is not a visit but a list of rules: which state does what to the balance, and whose record each thing hangs on.

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