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

System Architecture for Kadikoy businesses

One name stands more than once on the shelf behind a counter: a single scent, separate bottles. The label belongs to the bottle, the name belongs to the product. Which of those two the record follows is the first architectural call. Kadikoy's fabric leans on clinics, studios and small retail that runs by appointment, and the call lands there too. On Kokudankokuya a scent stays one product record while each volume is a sellable unit of its own, priced and stocked at that level.

Get a quote Tell us about your project

System Architecture — Kadikoy

Along Bahariye in Kadikoy, appointment-run service businesses sit beside small retail. If you sell the same thing in more than one form, the architectural question is how those forms sit in the record. Where Kokudankokuya does not reach is worth stating: it was built for perfume retail, so a clinic's treatment plan or a studio's class schedule is not in it and we have nothing there to show. What travels is not the shopfront but how many axes the model carries. Alongside the category tree, scent family and note open a second way to browse, and one perfume can attach to several notes instead of sitting in a single branch. Adding no layer was a decision too: the catalogue's scale called for no search or cache tier, so the shop runs on Laravel and MySQL.

  • Identity and sellable unit are kept apart: the scent is one product record, each volume carries its own price and stock, and adding a volume opens no new product.
  • A second browsing axis sits beside the category tree, so a shopper who does not know the brand can start from a scent family or a note and arrive at the product.
  • One perfume attaches to several notes, so the same item surfaces from different search intents; Laravel runs the process and MySQL holds the records.

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

Kokudankokuya — one product record per scent, volume as the sellable unit

A perfume retail store where the record's shape was settled first. A scent stays one product record and volumes are separate sellable units: price and stock sit at volume level, so adding a size opens no new catalogue product. Browsing did not stay on one axis. Scent family and note run alongside the category tree, letting a shopper who knows no brand names start from the character of a scent and reach the bottle. One perfume attaches to several notes, so the same item is reachable from different searches. The stack stayed deliberately narrow: the scale asked for no search or cache tier, and the shop runs on Laravel and MySQL.

Read the case study →

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

  • Why not open a separate product for every volume?

    You can, and the cost accumulates in the catalogue. One scent scatters across several entries, copy and imagery get updated in each of them, and the same name repeats down a results page. Here the scent is one record and the volume is the sellable unit, with price and stock held at that level.

  • We already have a category tree. What is the second axis for?

    A category tree assumes the shopper knows what to look for. The second axis assumes nothing: scent family and note give a way in to someone who knows no brand names. And because an item can attach to several notes, it is never locked into a single branch.

  • Will you add a search engine or a cache tier?

    The catalogue's scale never asked for one, so we left it out. Every tier is something to install, version and repair when it breaks. The shop sits on Laravel and MySQL, and there is little to carry. If the scale changes, adding a tier becomes a written decision of its own.

  • Can you point to a client of yours in Kadikoy?

    We have no client in Kadikoy and will not invent the connection. We keep no office either; the way we work has been remote from the start. What we show is the work in our portfolio closest to how businesses here are shaped, and the record behind it.

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