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

System Architecture for Pendik businesses

A seller photographs a machine where it stands: under the crane hook, still bolted to the floor. The frame shows a grey body, and the distinction is not in the picture. Pendik's fabric leans on small manufacturers and multi-site service organisations; if you have to photograph a machine where it stands, that condition returns on every listing. On Plastik ve Makina the record carries the distinction instead: the whole category tree is built from one machine family's own divisions, and the property a buyer searches on is a field in the model rather than a line of free text.

Get a quote Tell us about your project

System Architecture — Pendik

In Pendik small manufacturers and multi-site service organisations sit side by side, and one catalogue can be read with two sets of eyes: one buying or selling the machine, the other after a spare for the same body. What the platform does not cover is plain. Plastik ve Makina is a listings platform, so no basket, no payment and no stock count live in it, and for a service organisation's work order flow we have nothing to show. What carries over is how many distinctions the record can hold as fields, and where the list is produced. That list is built on the server: Laravel assembles the result, Inertia carries it to the browser, and a filter change does not reload the page. MySQL holds the listings, Redis takes the read load, Tailwind shapes the interface.

  • The whole category tree is built from one machine family's own divisions, so a split that stays a subheading on a general listings site becomes the main axis here.
  • The record says what the photograph cannot: because the distinction is a field in the model it can be filtered on, instead of sitting in the free text of a description.
  • The list is assembled on the server and carried over by Inertia, so a filter change refreshes results in place while MySQL holds listings and Redis takes the read load.

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

Plastik ve Makina — the record carries the distinction, the list is built server side

A sector listings platform for buyers and sellers of plastics processing machinery. The whole category tree is built from one machine family's own divisions, so a split that would be a subheading elsewhere becomes the main axis. Because the property searched on is a field in the model, it can be filtered rather than left in free text. New and used stay in one list, so a buyer weighs both inside a single search. The read path was decided too: Laravel assembles the list on the server, Inertia carries it over, and a filter change refreshes results in place with no reload. MySQL holds the listings and Redis takes the read load.

Read the case study →

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

  • Are a photo and a description not enough? Why open separate fields?

    A photo shows the body, not the distinction, and a description is free text so nothing can be filtered on it. Once the distinction is a field in the model, a buyer narrows the list by the criterion that matters and the seller is found by that same criterion.

  • Could we not run a separate list for used machines?

    You could, and at that moment you have two catalogues, two things to maintain and two search habits. On Plastik ve Makina new and used stay in one list, so a buyer weighs both inside a single search and a seller appears in one place.

  • Is refreshing without a page reload a design preference?

    No, it is a read path decision. Laravel assembles the list on the server and Inertia carries the result to the browser, so nothing is rebuilt from scratch and results refresh in place. Redis takes the frequently read lists, which keeps trying another filter cheap.

  • We do not sell machine listings. What does this evidence say to a manufacturer here?

    The platform was written for listings and we say so plainly: no work order, no basket, no stock count. What transfers is what the catalogue is divided by — the axis comes from the machine's own family rather than a broad industrial heading. Nobody travels to Pendik to install anything; the work runs remotely.

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