{"id":34262,"date":"2025-11-14T02:31:17","date_gmt":"2025-11-13T23:31:17","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/"},"modified":"2025-11-14T02:31:17","modified_gmt":"2025-11-13T23:31:17","slug":"phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/","title":{"rendered":"PHP’de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f"},"content":{"rendered":"

Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP’de “Temiz” ve “S\u00fcr\u00fcc\u00fc Bilin\u00e7li” bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.<\/p>\n

Her PHP geli\u015ftiricisi, kariyerinin bir noktas\u0131nda do\u011frudan SQL sorgular\u0131yla bo\u011fu\u015fmu\u015ftur. mysqli_query<\/code> veya PDO kullanarak yaz\u0131lan her SQL c\u00fcmlesi, genellikle tekrar eden kal\u0131plar i\u00e7erir: ba\u011flant\u0131 kurma, sorguyu haz\u0131rlama, parametreleri ba\u011flama, \u00e7al\u0131\u015ft\u0131rma, sonu\u00e7lar\u0131 \u00e7ekme ve hata y\u00f6netimi. Bu s\u00fcre\u00e7, k\u00fc\u00e7\u00fck projeler i\u00e7in idare edilebilir olsa da, b\u00fcy\u00fck ve karma\u015f\u0131k uygulamalarda h\u0131zla bir kabusa d\u00f6n\u00fc\u015febilir. Veritaban\u0131 \u015femas\u0131 de\u011fi\u015fti\u011finde, ilgili her SQL sorgusunu manuel olarak g\u00fcncellemek zorunda kalmak, zaman al\u0131c\u0131 ve hataya a\u00e7\u0131k bir i\u015ftir. Ayr\u0131ca, SQL enjeksiyonu gibi g\u00fcvenlik a\u00e7\u0131klar\u0131yla m\u00fccadele etmek de ayr\u0131 bir y\u00fckt\u00fcr.<\/p>\n

\u0130\u015fler daha da karma\u015f\u0131kla\u015f\u0131r: ya projeniz ba\u015flang\u0131\u00e7ta MySQL kullan\u0131rken, bir noktada PostgreSQL veya SQL Server’a ge\u00e7me ihtiyac\u0131 duyarsa? Do\u011frudan SQL sorgular\u0131 yaz\u0131yorsan\u0131z, bu ge\u00e7i\u015f neredeyse t\u00fcm veri eri\u015fim katman\u0131n\u0131z\u0131 yeniden yazmak anlam\u0131na gelebilir. Her veritaban\u0131n\u0131n kendi SQL leh\u00e7esi ve \u00f6zg\u00fcll\u00fckleri vard\u0131r; \u00f6rne\u011fin, LIMIT\/OFFSET sentaks\u0131 farkl\u0131l\u0131k g\u00f6sterebilir veya baz\u0131 veri tipleri farkl\u0131 \u015fekilde ele al\u0131nabilir. \u0130\u015fte tam bu noktada, ORM mimarileri devreye girer. ORM’ler, veritaban\u0131 i\u015flemlerini nesne odakl\u0131 bir yakla\u015f\u0131mla soyutlayarak bu sorunlara zarif \u00e7\u00f6z\u00fcmler sunar. Ancak her ORM ayn\u0131 de\u011fildir; “temiz” ve “s\u00fcr\u00fcc\u00fc bilin\u00e7li” bir yakla\u015f\u0131m benimsemek, bu ara\u00e7lar\u0131n ger\u00e7ek potansiyelini ortaya \u00e7\u0131kar\u0131r. Temiz bir ORM, uygulaman\u0131z\u0131n di\u011fer katmanlar\u0131ndan veri eri\u015fim mant\u0131\u011f\u0131n\u0131 ay\u0131r\u0131rken, s\u00fcr\u00fcc\u00fc bilin\u00e7li bir yap\u0131, veritaban\u0131 sa\u011flay\u0131c\u0131s\u0131ndan ba\u011f\u0131ms\u0131zl\u0131k sa\u011flayarak esnekli\u011fi en \u00fcst d\u00fczeye \u00e7\u0131kar\u0131r. Bu sayede, geli\u015ftiriciler veritaban\u0131n\u0131n alt\u0131ndaki karma\u015f\u0131k SQL detaylar\u0131na tak\u0131lmak yerine, uygulaman\u0131n i\u015f mant\u0131\u011f\u0131na odaklanabilirler. Bu yakla\u015f\u0131m, sadece kodu basitle\u015ftirmekle kalmaz, ayn\u0131 zamanda test edilebilirli\u011fi, bak\u0131m\u0131 ve gelecekteki \u00f6l\u00e7eklenebilirli\u011fi de \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirir.<\/p>\n

Temel Kavramlar: ORM Nedir ve Neden \u0130htiyac\u0131m\u0131z Var?<\/h2>\n

ORM, yani Object-Relational Mapping (Nesne-\u0130li\u015fkisel E\u015fle\u015ftirme), ili\u015fkisel veritabanlar\u0131 ile nesne tabanl\u0131 programlama dilleri aras\u0131ndaki uyumsuzluklar\u0131 \u00e7\u00f6zmek i\u00e7in kullan\u0131lan bir programlama tekni\u011fidir. K\u0131saca, veritaban\u0131ndaki tablolar\u0131 ve sat\u0131rlar\u0131, PHP’deki nesnelere (s\u0131n\u0131flara ve bu s\u0131n\u0131flar\u0131n \u00f6rneklerine) d\u00f6n\u00fc\u015ft\u00fcrmeyi sa\u011flar. Bu sayede, geli\u015ftiriciler veritaban\u0131 tablolar\u0131yla do\u011frudan SQL sorgular\u0131 yazmak yerine, PHP nesneleriyle etkile\u015fime girerek veri i\u015flemleri yapabilirler. Bir User<\/code> nesnesini d\u00fc\u015f\u00fcn\u00fcn; bu nesne, veritaban\u0131ndaki users<\/code> tablosundaki bir sat\u0131r\u0131 temsil edebilir. $user->save()<\/code> veya User::find(1)<\/code> gibi y\u00f6ntemlerle veritaban\u0131yla etkile\u015fime ge\u00e7mek, SQL bilmekten \u00e7ok daha sezgiseldir.<\/p>\n

Peki, bir ORM’e neden ihtiyac\u0131m\u0131z var? Birincisi, \u00fcretkenli\u011fi art\u0131r\u0131r<\/strong>. ORM’ler, geli\u015ftiricilerin tekrar eden SQL yazma ve sonu\u00e7 k\u00fcmesi i\u015fleme gibi s\u0131k\u0131c\u0131 g\u00f6revlerden kurtulmas\u0131n\u0131 sa\u011flar. \u0130kincisi, bak\u0131m\u0131 kolayla\u015ft\u0131r\u0131r<\/strong>. Veritaban\u0131 \u015femas\u0131 de\u011fi\u015fti\u011finde, ORM genellikle bu de\u011fi\u015fiklikleri otomatik olarak y\u00f6netir veya en az\u0131ndan de\u011fi\u015fikliklerin etkisini minimuma indirir. \u00dc\u00e7\u00fcnc\u00fcs\u00fc, SQL enjeksiyonu gibi g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 \u00f6nlemeye yard\u0131mc\u0131 olur<\/strong>. Parametre ba\u011flama gibi g\u00fcvenli uygulamalar\u0131 varsay\u0131lan olarak sunar. D\u00f6rd\u00fcnc\u00fcs\u00fc, kodun okunabilirli\u011fini ve anla\u015f\u0131l\u0131rl\u0131\u011f\u0131n\u0131 art\u0131r\u0131r<\/strong>. Nesne tabanl\u0131 bir aray\u00fcz, i\u015f mant\u0131\u011f\u0131n\u0131 daha net bir \u015fekilde ifade etmeyi sa\u011flar. Son olarak, test edilebilirli\u011fi iyile\u015ftirir<\/strong>. Veritaban\u0131 i\u015flemlerini soyutlad\u0131\u011f\u0131 i\u00e7in, birim testlerinde sahte veritaban\u0131 ba\u011flant\u0131lar\u0131 veya in-memory veritabanlar\u0131 kullanmak \u00e7ok daha kolayd\u0131r.<\/p>\n

Ancak, her ORM m\u00fckemmel de\u011fildir. Performans overhead’i, \u00f6\u011frenme e\u011frisi ve “leaky abstraction” riski (yani ORM’in alt\u0131ndaki veritaban\u0131 detaylar\u0131n\u0131n s\u0131zmas\u0131) gibi potansiyel dezavantajlar\u0131 da vard\u0131r. Bu dezavantajlar\u0131 en aza indirmek i\u00e7in “s\u00fcr\u00fcc\u00fc bilin\u00e7li” bir yakla\u015f\u0131m benimsemek kritiktir. “S\u00fcr\u00fcc\u00fc Bilin\u00e7li” (Driver-Aware) ne anlama geliyor? Bu, ORM’in farkl\u0131 veritaban\u0131 sistemlerinin (MySQL, PostgreSQL, SQL Server vb.) kendine \u00f6zg\u00fc \u00f6zelliklerini ve SQL leh\u00e7elerini anlay\u0131p y\u00f6netebilmesi demektir. \u00d6rne\u011fin, bir sorgu olu\u015fturucu, MySQL i\u00e7in LIMIT<\/code> ve OFFSET<\/code> kullan\u0131rken, SQL Server i\u00e7in TOP<\/code> veya ROW_NUMBER() OVER (...)<\/code> gibi farkl\u0131 sentakslar\u0131 otomatik olarak uygulayabilmelidir. Bu, veritaban\u0131 sa\u011flay\u0131c\u0131s\u0131ndan ba\u011f\u0131ms\u0131zl\u0131k sa\u011flayarak uygulaman\u0131z\u0131n esnekli\u011fini ve gelece\u011fe d\u00f6n\u00fckl\u00fc\u011f\u00fcn\u00fc maksimize eder. Uygulaman\u0131z\u0131n temel veri eri\u015fim katman\u0131, kulland\u0131\u011f\u0131n\u0131z veritaban\u0131n\u0131n detaylar\u0131ndan haberdar olmal\u0131 ancak i\u015f mant\u0131\u011f\u0131 katman\u0131 bu detaylardan tamamen soyutlanm\u0131\u015f kalmal\u0131d\u0131r. Bu ayr\u0131m, karma\u015f\u0131k projelerde esnekli\u011fi art\u0131r\u0131r, b\u00f6ylece geli\u015ftiriciler sistemin veri depolama katman\u0131nda yap\u0131lan de\u011fi\u015fiklikler hakk\u0131nda endi\u015felenmek zorunda kalmazlar.<\/p>\n

Temiz Bir ORM Mimarisi Nas\u0131l Tasarlan\u0131r? Katmanlara Ayr\u0131lm\u0131\u015f Bir Yakla\u015f\u0131m<\/h2>\n

Temiz ve s\u00fcr\u00fcc\u00fc bilin\u00e7li bir ORM mimarisi olu\u015fturman\u0131n temelinde, sorumluluklar\u0131n net bir \u015fekilde ayr\u0131\u015ft\u0131r\u0131lmas\u0131 yatar. Bu, genellikle birka\u00e7 ana katmana b\u00f6l\u00fcnerek ba\u015far\u0131l\u0131r:<\/p>\n

    \n
  1. Veritaban\u0131 Soyutlama Katman\u0131 (Driver Layer):<\/strong> Do\u011frudan veritaban\u0131yla etkile\u015fim kuran en alt katmand\u0131r. PDO gibi bir PHP uzant\u0131s\u0131n\u0131 kullanarak farkl\u0131 veritabanlar\u0131na ba\u011flanma ve temel sorgular\u0131 \u00e7al\u0131\u015ft\u0131rma yetene\u011fi sa\u011flar.<\/li>\n
  2. Sorgu Olu\u015fturucu (Query Builder):<\/strong> Veritaban\u0131 sorgular\u0131n\u0131 nesne tabanl\u0131 bir aray\u00fczle olu\u015fturmay\u0131 sa\u011flayan katmand\u0131r. SQL sentaks\u0131n\u0131n karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 gizler ve s\u00fcr\u00fcc\u00fc bilin\u00e7li \u00f6zellikleri burada devreye girer.<\/li>\n
  3. Veri E\u015fleme Katman\u0131 (Data Mapper):<\/strong> Veritaban\u0131 sat\u0131rlar\u0131n\u0131 PHP nesnelerine ve PHP nesnelerini veritaban\u0131 sat\u0131rlar\u0131na d\u00f6n\u00fc\u015ft\u00fcrmekten sorumludur.<\/li>\n
  4. Varl\u0131k Katman\u0131 (Entity Layer):<\/strong> Uygulaman\u0131zdaki i\u015f nesnelerini (varl\u0131klar\u0131) temsil eden katmand\u0131r. Veritaban\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131ndan ar\u0131nd\u0131r\u0131lm\u0131\u015f saf PHP nesneleridir.<\/li>\n
  5. Depo Katman\u0131 (Repository Layer):<\/strong> Varl\u0131klar i\u00e7in koleksiyon benzeri bir aray\u00fcz sa\u011flar. Veri eri\u015fim mant\u0131\u011f\u0131n\u0131 i\u015f mant\u0131\u011f\u0131ndan ay\u0131r\u0131r ve Data Mapper’\u0131 kullan\u0131r.<\/li>\n<\/ol>\n

    Veritaban\u0131 Soyutlama Katman\u0131 (Driver Layer) Ne \u0130\u015fe Yarar?<\/h3>\n

    Bu katman, ORM’imizin kalbidir ve farkl\u0131 veritaban\u0131 sistemleriyle uyumlulu\u011fun temelini olu\u015fturur. Amac\u0131m\u0131z, uygulaman\u0131n geri kalan\u0131n\u0131n hangi veritaban\u0131n\u0131 kulland\u0131\u011f\u0131n\u0131 bilmek zorunda kalmadan, standart bir aray\u00fcz \u00fczerinden veritaban\u0131 i\u015flemleri yapabilmesini sa\u011flamakt\u0131r. PHP’de genellikle PDO (PHP Data Objects) bu soyutlaman\u0131n temelini olu\u015fturur. Ancak PDO’nun kendisi de bir soyutlama olmas\u0131na ra\u011fmen, baz\u0131 veritabanlar\u0131na \u00f6zg\u00fc farkl\u0131l\u0131klar (\u00f6rne\u011fin, sorgu sentaks\u0131, hata kodlar\u0131) hala mevcuttur. Bizim “Driver Layer”\u0131m\u0131z, bu PDO farkl\u0131l\u0131klar\u0131n\u0131 da soyutlayarak tam bir veritaban\u0131 ba\u011f\u0131ms\u0131zl\u0131\u011f\u0131 sunar.<\/p>\n

    \u00d6ncelikle, t\u00fcm s\u00fcr\u00fcc\u00fclerin uygulayaca\u011f\u0131 bir aray\u00fcz tan\u0131mlar\u0131z:<\/p>\n

    \ninterface DatabaseDriverInterface\n{\n    public function connect(array $config): void;\n    public function disconnect(): void;\n    public function query(string $sql, array $params = []): array;\n    public function execute(string $sql, array $params = []): int;\n    public function lastInsertId(): ?string;\n    public function beginTransaction(): bool;\n    public function commit(): bool;\n    public function rollBack(): bool;\n}\n<\/pre>\n
    <\/code><\/p>\n
    \u015eimdi, bu aray\u00fcz\u00fc uygulayan belirli s\u00fcr\u00fcc\u00fcler (\u00f6rne\u011fin, MySQL i\u00e7in) olu\u015fturabiliriz:<\/p>\n
    \nclass MySqlDriver implements DatabaseDriverInterface\n{\n    private ?\\PDO $pdo = null;\n\n    public function connect(array $config): void\n    {\n        $dsn = \"mysql:host={$config['host']};dbname={$config['dbname']};charset={$config['charset']}\";\n        $this->pdo = new \\PDO($dsn, $config['user'], $config['pass'], $config['options'] ?? []);\n        $this->pdo->setAttribute(\\PDO::ATTR_ERRMODE, \\PDO::ERRMODE_EXCEPTION);\n        $this->pdo->setAttribute(\\PDO::ATTR_DEFAULT_FETCH_MODE, \\PDO::FETCH_ASSOC);\n    }\n\n    public function disconnect(): void\n    {\n        $this->pdo = null;\n    }\n\n    public function query(string $sql, array $params = []): array\n    {\n        $stmt = $this->pdo->prepare($sql);\n        $stmt->execute($params);\n        return $stmt->fetchAll();\n    }\n\n    public function execute(string $sql, array $params = []): int\n    {\n        $stmt = $this->pdo->prepare($sql);\n        $stmt->execute($params);\n        return $stmt->rowCount();\n    }\n\n    public function lastInsertId(): ?string\n    {\n        return $this->pdo->lastInsertId();\n    }\n\n    public function beginTransaction(): bool\n    {\n        return $this->pdo->beginTransaction();\n    }\n\n    public function commit(): bool\n    {\n        return $this->pdo->commit();\n    }\n\n    public function rollBack(): bool\n    {\n        return $this->pdo->rollBack();\n    }\n}\n<\/pre>\n
    <\/code><\/p>\n
    Benzer \u015fekilde, bir PostgreSqlDriver<\/code> veya SqliteDriver<\/code> da ayn\u0131 DatabaseDriverInterface<\/code>'i uygulayarak farkl\u0131 veritabanlar\u0131 i\u00e7in \u00f6zel ba\u011flant\u0131 ve sorgu mant\u0131\u011f\u0131 sa\u011flayabilir. Bu yap\u0131, uygulaman\u0131z\u0131n temel veritaban\u0131 operasyonlar\u0131n\u0131 tamamen soyutlar ve alt katmanda herhangi bir veritaban\u0131 de\u011fi\u015fiminde, yaln\u0131zca ilgili s\u00fcr\u00fcc\u00fcn\u00fcn g\u00fcncellenmesi veya yenisinin eklenmesi yeterli olur.<\/p>\n
    Veri E\u015fleme Katman\u0131 (Data Mapper) Neden Gereklidir?<\/h3>\n
    Veri E\u015fleme (Data Mapper) deseni, uygulaman\u0131z\u0131n veritaban\u0131 ile etkile\u015fimini, i\u015f nesnelerinizden (varl\u0131klar\u0131n\u0131zdan) tamamen ay\u0131r\u0131r. Bu, \"persistence ignorance\" (kal\u0131c\u0131l\u0131k bilgisizli\u011fi) ilkesini destekler; yani, varl\u0131k nesneleriniz veritaban\u0131na nas\u0131l kaydedildikleri veya oradan nas\u0131l y\u00fcklendikleri hakk\u0131nda hi\u00e7bir bilgiye sahip de\u011fildir. Bu ayr\u0131m, ba\u011f\u0131ms\u0131zl\u0131\u011f\u0131 art\u0131r\u0131r ve hem i\u015f mant\u0131\u011f\u0131n\u0131n hem de veri eri\u015fim mant\u0131\u011f\u0131n\u0131n ayr\u0131 ayr\u0131 geli\u015ftirilmesine ve test edilmesine olanak tan\u0131r. Data Mapper, bir yandan veritaban\u0131ndan \u00e7ekilen sat\u0131rlar\u0131 PHP nesnelerine d\u00f6n\u00fc\u015ft\u00fcr\u00fcrken, di\u011fer yandan PHP nesnelerinin \u00f6zelliklerini veritaban\u0131 s\u00fctunlar\u0131na e\u015fleyerek kay\u0131t veya g\u00fcncelleme i\u015flemlerini ger\u00e7ekle\u015ftirir.<\/p>\n
    Her varl\u0131k (entity) i\u00e7in bir Data Mapper olacakt\u0131r. \u00d6rne\u011fin, bir User<\/code> varl\u0131\u011f\u0131 i\u00e7in UserDataMapper<\/code> \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n
    \n\/\/ Varl\u0131k (Entity) Tan\u0131m\u0131\nclass User\n{\n    private ?int $id;\n    private string $username;\n    private string $email;\n    private \\DateTimeImmutable $createdAt;\n\n    public function __construct(?int $id, string $username, string $email, \\DateTimeImmutable $createdAt)\n    {\n        $this->id = $id;\n        $this->username = $username;\n        $this->email = $email;\n        $this->createdAt = $createdAt;\n    }\n\n    \/\/ Getter ve Setter metotlar\u0131\n    public function getId(): ?int { return $this->id; }\n    public function setId(int $id): void { $this->id = $id; } \/\/ Sadece yeni kay\u0131tlar i\u00e7in\n    public function getUsername(): string { return $this->username; }\n    public function setUsername(string $username): void { $this->username = $username; }\n    public function getEmail(): string { return $this->email; }\n    public function setEmail(string $email): void { $this->email = $email; }\n    public function getCreatedAt(): \\DateTimeImmutable { return $this->createdAt; }\n}\n\n\/\/ Data Mapper Aray\u00fcz\u00fc\ninterface DataMapperInterface\n{\n    public function mapRowToObject(array $row): object;\n    public function mapObjectToRow(object $object): array;\n}\n\n\/\/ User Data Mapper Uygulamas\u0131\nclass UserDataMapper implements DataMapperInterface\n{\n    public function mapRowToObject(array $row): User\n    {\n        \/\/ Veritaban\u0131 sat\u0131r\u0131ndan User nesnesine e\u015fleme\n        return new User(\n            $row['id'],\n            $row['username'],\n            $row['email'],\n            new \\DateTimeImmutable($row['created_at'])\n        );\n    }\n\n    public function mapObjectToRow(object $user): array\n    {\n        if (!$user instanceof User) {\n            throw new \\InvalidArgumentException(\"Beklenen User nesnesi de\u011fil.\");\n        }\n        \/\/ User nesnesinden veritaban\u0131 sat\u0131r\u0131na e\u015fleme\n        return [\n            'username' => $user->getUsername(),\n            'email' => $user->getEmail(),\n            'created_at' => $user->getCreatedAt()->format('Y-m-d H:i:s')\n        ];\n    }\n}\n<\/pre>\n
    <\/code><\/p>\n
    Bu yap\u0131 sayesinde, User<\/code> s\u0131n\u0131f\u0131 veritaban\u0131 detaylar\u0131ndan tamamen habersiz kal\u0131rken, UserDataMapper<\/code> sadece bu iki d\u00fcnya aras\u0131ndaki k\u00f6pr\u00fcy\u00fc kurma sorumlulu\u011funu \u00fcstlenir. Bu, daha temiz, daha esnek ve daha test edilebilir bir mimariye yol a\u00e7ar. \u00d6rne\u011fin, bir g\u00fcn created_at<\/code> s\u00fctununun ad\u0131n\u0131 creation_date<\/code> olarak de\u011fi\u015ftirmek isterseniz, yaln\u0131zca UserDataMapper<\/code> s\u0131n\u0131f\u0131n\u0131 g\u00fcncellemeniz yeterli olur, User<\/code> varl\u0131\u011f\u0131nda hi\u00e7bir de\u011fi\u015fiklik yapman\u0131za gerek kalmaz.<\/p>\n
    \n  Uzman \u0130pucu: Data Mapper pattern'\u0131n\u0131 uygularken, s\u00fctun adlar\u0131 ile nesne \u00f6zellikleri aras\u0131ndaki e\u015flemeyi otomatikle\u015ftirmek i\u00e7in reflection API kullanabilirsiniz. Bu, her s\u00fctun i\u00e7in manuel olarak e\u015fleme yazma ihtiyac\u0131n\u0131 azalt\u0131r ve daha az tekrar eden kod yazman\u0131z\u0131 sa\u011flar. Ancak bu, performansa k\u00fc\u00e7\u00fck bir y\u00fck getirebilir, bu nedenle dengeli bir yakla\u015f\u0131m benimsemek \u00f6nemlidir.\n<\/div>\n
    S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Uygulamas\u0131: Ad\u0131m Ad\u0131m Entegrasyon<\/h2>\n
    S\u00fcr\u00fcc\u00fc bilin\u00e7li bir ORM'in temel g\u00fcc\u00fc, kullan\u0131lan veritaban\u0131 s\u00fcr\u00fcc\u00fcs\u00fcne g\u00f6re farkl\u0131 SQL sentakslar\u0131n\u0131 ve \u00f6zelliklerini otomatik olarak y\u00f6netebilmesidir. Bu, uygulaman\u0131n farkl\u0131 veritaban\u0131 sistemleri aras\u0131nda kolayca ge\u00e7i\u015f yapabilmesini sa\u011flar. Bu b\u00f6l\u00fcmde, bu yetene\u011fi nas\u0131l entegre edece\u011fimizi ve ana bile\u015fenlerini inceleyece\u011fiz.<\/p>\n
    Bir Sorgu Olu\u015fturucu (Query Builder) Nas\u0131l Geli\u015ftirilir?<\/h3>\n
    Sorgu Olu\u015fturucu (Query Builder), karma\u015f\u0131k SQL sorgular\u0131n\u0131 nesne tabanl\u0131, ak\u0131c\u0131 (fluent) bir aray\u00fcz kullanarak olu\u015fturmam\u0131z\u0131 sa\u011flayan merkezi bir bile\u015fendir. Do\u011frudan SQL yazmaktan ka\u00e7\u0131narak, hem kod okunabilirli\u011fini art\u0131r\u0131r hem de SQL enjeksiyonu gibi g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 azalt\u0131r. En \u00f6nemlisi, s\u00fcr\u00fcc\u00fc bilin\u00e7li mimaride Query Builder, kullan\u0131lan DatabaseDriverInterface<\/code> uygulamas\u0131na g\u00f6re farkl\u0131 veritaban\u0131 leh\u00e7elerini otomatik olarak d\u00f6n\u00fc\u015ft\u00fcrebilmelidir.<\/p>\n
    Basit bir QueryBuilder<\/code> s\u0131n\u0131f\u0131 \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n
    \ninterface QueryBuilderInterface\n{\n    public function select(array $columns = ['*']): self;\n    public function from(string $table): self;\n    public function where(string $column, string $operator, mixed $value): self;\n    public function limit(int $limit): self;\n    public function offset(int $offset): self;\n    public function build(): array; \/\/ ['sql' => ..., 'params' => ...]\n    public function getDriver(): DatabaseDriverInterface;\n}\n\nclass GenericQueryBuilder implements QueryBuilderInterface\n{\n    protected DatabaseDriverInterface $driver;\n    protected array $parts = [];\n    protected array $params = [];\n    protected string $table = '';\n\n    public function __construct(DatabaseDriverInterface $driver)\n    {\n        $this->driver = $driver;\n    }\n\n    public function getDriver(): DatabaseDriverInterface\n    {\n        return $this->driver;\n    }\n\n    public function select(array $columns = ['*']): self\n    {\n        $this->parts['select'] = 'SELECT ' . implode(', ', $columns);\n        return $this;\n    }\n\n    public function from(string $table): self\n    {\n        $this->table = $table;\n        $this->parts['from'] = 'FROM ' . $table;\n        return $this;\n    }\n\n    public function where(string $column, string $operator, mixed $value): self\n    {\n        $paramName = ':where_' . count($this->params);\n        $this->parts['where'][] = \"{$column} {$operator} {$paramName}\";\n        $this->params[$paramName] = $value;\n        return $this;\n    }\n\n    public function limit(int $limit): self\n    {\n        $this->parts['limit'] = $limit;\n        return $this;\n    }\n\n    public function offset(int $offset): self\n    {\n        $this->parts['offset'] = $offset;\n        return $this;\n    }\n\n    public function build(): array\n    {\n        $sql = [];\n        if (isset($this->parts['select'])) {\n            $sql[] = $this->parts['select'];\n        }\n        if (isset($this->parts['from'])) {\n            $sql[] = $this->parts['from'];\n        }\n        if (!empty($this->parts['where'])) {\n            $sql[] = 'WHERE ' . implode(' AND ', $this->parts['where']);\n        }\n\n        \/\/ S\u00fcr\u00fcc\u00fc bilin\u00e7li limit\/offset uygulamas\u0131\n        if (isset($this->parts['limit']) || isset($this->parts['offset'])) {\n            \/\/ Buras\u0131 veritaban\u0131 s\u00fcr\u00fcc\u00fcs\u00fcne g\u00f6re de\u011fi\u015febilir.\n            \/\/ \u00d6rne\u011fin, MySQL i\u00e7in \"LIMIT X OFFSET Y\"\n            \/\/ PostgreSQL i\u00e7in \"LIMIT X OFFSET Y\"\n            \/\/ SQL Server i\u00e7in farkl\u0131 bir yakla\u015f\u0131ma ihtiya\u00e7 duyulabilir (TOP veya ROW_NUMBER)\n            \/\/ Bu mant\u0131k asl\u0131nda QueryBuilder'\u0131n \u00f6zel t\u00fcrevlerinde veya bir QueryGrammar s\u0131n\u0131f\u0131nda olmal\u0131d\u0131r.\n            if (isset($this->parts['limit'])) {\n                $sql[] = \"LIMIT \" . $this->parts['limit'];\n            }\n            if (isset($this->parts['offset'])) {\n                $sql[] = \"OFFSET \" . $this->parts['offset'];\n            }\n        }\n\n        return ['sql' => implode(' ', $sql), 'params' => $this->params];\n    }\n}\n<\/pre>\n
    <\/code><\/p>\n
    Yukar\u0131daki \u00f6rnekte build()<\/code> metodunda LIMIT<\/code> ve OFFSET<\/code> k\u0131sm\u0131 i\u00e7in bir yorum bulunmaktad\u0131r. Bu, s\u00fcr\u00fcc\u00fc bilin\u00e7li tasar\u0131m\u0131n en net g\u00f6stergelerinden biridir. MySQL ve PostgreSQL, LIMIT<\/code> ve OFFSET<\/code> sentaks\u0131n\u0131 do\u011frudan desteklerken, SQL Server gibi baz\u0131 veritabanlar\u0131 bu i\u015flemleri farkl\u0131 \u015fekillerde (\u00f6rne\u011fin TOP<\/code> anahtar kelimesi veya ROW_NUMBER()<\/code> pencere fonksiyonu ile) yapar. Bu durumu y\u00f6netmek i\u00e7in, GenericQueryBuilder<\/code> s\u0131n\u0131f\u0131ndan t\u00fcreyen MySqlQueryBuilder<\/code>, PostgreSqlQueryBuilder<\/code> veya SqlServerQueryBuilder<\/code> gibi s\u0131n\u0131flar olu\u015fturulabilir. Her t\u00fcrev s\u0131n\u0131f, kendi veritaban\u0131n\u0131n spesifikasyonlar\u0131na uygun build()<\/code> metodunu veya ayr\u0131 bir QueryGrammar<\/code> (sorgu grameri) s\u0131n\u0131f\u0131n\u0131 kullanarak SQL \u00e7\u0131kt\u0131s\u0131n\u0131 \u00fcretecektir. Bu sayede, uygulaman\u0131z\u0131n \u00fcst katmanlar\u0131 ayn\u0131 QueryBuilder<\/code> aray\u00fcz\u00fcn\u00fc kullanmaya devam ederken, altta yatan veritaban\u0131 karma\u015f\u0131kl\u0131\u011f\u0131 soyutlanm\u0131\u015f olur.<\/p>\n
    Varl\u0131k Y\u00f6netimi ve De\u011fi\u015fim Takibi (Unit of Work) Nas\u0131l Sa\u011flan\u0131r?<\/h3>\n
    Unit of Work (\u0130\u015f Birimi) deseni, bir i\u015f ak\u0131\u015f\u0131 veya i\u015flem s\u0131ras\u0131nda yap\u0131lan t\u00fcm de\u011fi\u015fiklikleri (yeni nesneler olu\u015fturma, mevcutlar\u0131 g\u00fcncelleme, silme) tek bir \"birim\" olarak izler. Bu de\u011fi\u015fiklikler, i\u015flemin sonunda tek bir veritaban\u0131 i\u015flemi (commit) olarak uygulan\u0131r. Bu desenin temel faydalar\u0131 \u015funlard\u0131r:<\/p>\n
      \n
    • Tutarl\u0131l\u0131k:<\/strong> T\u00fcm de\u011fi\u015fiklikler ba\u015far\u0131l\u0131 bir \u015fekilde uygulan\u0131r veya hi\u00e7biri uygulanmaz, bu da veritaban\u0131 tutarl\u0131l\u0131\u011f\u0131n\u0131 sa\u011flar.<\/li>\n
    • Performans:<\/strong> Bir\u00e7ok k\u00fc\u00e7\u00fck veritaban\u0131 i\u015flemi yapmak yerine, de\u011fi\u015fiklikler toplan\u0131r ve tek bir toplu i\u015flemde veritaban\u0131na g\u00f6nderilir. Bu, \u00f6zellikle bir\u00e7ok varl\u0131\u011f\u0131n ayn\u0131 anda de\u011fi\u015ftirildi\u011fi senaryolarda performans\u0131 art\u0131r\u0131r.<\/li>\n
    • Basitle\u015ftirme:<\/strong> Geli\u015ftiricilerin her de\u011fi\u015fiklik i\u00e7in manuel olarak INSERT<\/code>, UPDATE<\/code> veya DELETE<\/code> sorgusu yazmak zorunda kalmadan varl\u0131klarla \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar.<\/li>\n<\/ul>\n
      Bir UnitOfWork<\/code>'\u00fcn temel i\u015flevleri \u015funlar\u0131 i\u00e7erir:<\/p>\n
        \n
      1. Yeni Kay\u0131tlar\u0131 \u0130zleme:<\/strong> Hen\u00fcz veritaban\u0131na kaydedilmemi\u015f varl\u0131klar\u0131 kaydeder.<\/li>\n
      2. De\u011fi\u015ftirilmi\u015f Kay\u0131tlar\u0131 \u0130zleme:<\/strong> Mevcut olup, \u00f6zellikleri de\u011fi\u015ftirilmi\u015f varl\u0131klar\u0131 kaydeder.<\/li>\n
      3. Silinecek Kay\u0131tlar\u0131 \u0130zleme:<\/strong> Veritaban\u0131ndan silinmesi gereken varl\u0131klar\u0131 kaydeder.<\/li>\n<\/ol>\n
        Basit bir UnitOfWork<\/code> yap\u0131s\u0131:<\/p>\n
        \nclass UnitOfWork\n{\n    private DatabaseDriverInterface $driver;\n    private array $newEntities = [];\n    private array $dirtyEntities = []; \/\/ De\u011fi\u015ftirilmi\u015f varl\u0131klar\n    private array $removedEntities = [];\n    private array $entityMappers = []; \/\/ Varl\u0131k t\u00fcr\u00fcne g\u00f6re DataMapper'lar\u0131 tutar\n\n    public function __construct(DatabaseDriverInterface $driver)\n    {\n        $this->driver = $driver;\n    }\n\n    public function registerMapper(string $entityClassName, DataMapperInterface $mapper): void\n    {\n        $this->entityMappers[$entityClassName] = $mapper;\n    }\n\n    public function registerNew(object $entity): void\n    {\n        $this->newEntities[] = $entity;\n    }\n\n    public function registerDirty(object $entity): void\n    {\n        \/\/ Ger\u00e7ek bir UoW'de, bir varl\u0131\u011f\u0131n ger\u00e7ekten de\u011fi\u015fip de\u011fi\u015fmedi\u011fini kontrol etmek i\u00e7in\n        \/\/ orijinal halini saklamak gerekir. Basitlik ad\u0131na burada direkt ekliyoruz.\n        $this->dirtyEntities[] = $entity;\n    }\n\n    public function registerRemoved(object $entity): void\n    {\n        $this->removedEntities[] = $entity;\n    }\n\n    public function commit(): void\n    {\n        $this->driver->beginTransaction();\n        try {\n            \/\/ Yeni varl\u0131klar\u0131 kaydet\n            foreach ($this->newEntities as $entity) {\n                $mapper = $this->getMapperForEntity($entity);\n                $data = $mapper->mapObjectToRow($entity);\n                $query = \"INSERT INTO \" . $this->getTableName($entity) . \" (\" . implode(', ', array_keys($data)) . \") VALUES (:\" . implode(', :', array_keys($data)) . \")\";\n                $this->driver->execute($query, $data);\n                \/\/ E\u011fer varl\u0131\u011f\u0131n bir ID'si yoksa, yeni olu\u015fturulan ID'yi atayabiliriz.\n                if (method_exists($entity, 'setId') && $entity->getId() === null) {\n                    $entity->setId((int)$this->driver->lastInsertId());\n                }\n            }\n\n            \/\/ De\u011fi\u015ftirilmi\u015f varl\u0131klar\u0131 g\u00fcncelle\n            foreach ($this->dirtyEntities as $entity) {\n                $mapper = $this->getMapperForEntity($entity);\n                $data = $mapper->mapObjectToRow($entity);\n                \/\/ ID de\u011ferini d\u0131\u015far\u0131da b\u0131rak\u0131p WHERE ko\u015fulunda kullan\n                $id = $entity->getId();\n                unset($data['id']); \/\/ E\u011fer mapObjectToRow id'yi d\u00f6nd\u00fcr\u00fcyorsa\n                $setParts = [];\n                foreach ($data as $key => $value) {\n                    $setParts[] = \"{$key} = :{$key}\";\n                }\n                $query = \"UPDATE \" . $this->getTableName($entity) . \" SET \" . implode(', ', $setParts) . \" WHERE id = :id\";\n                $this->driver->execute($query, array_merge($data, ['id' => $id]));\n            }\n\n            \/\/ Silinecek varl\u0131klar\u0131 sil\n            foreach ($this->removedEntities as $entity) {\n                $query = \"DELETE FROM \" . $this->getTableName($entity) . \" WHERE id = :id\";\n                $this->driver->execute($query, ['id' => $entity->getId()]);\n            }\n\n            $this->driver->commit();\n            $this->clear(); \/\/ \u0130\u015flemler bittikten sonra izlenen varl\u0131klar\u0131 temizle\n        } catch (\\Exception $e) {\n            $this->driver->rollBack();\n            throw $e;\n        }\n    }\n\n    private function clear(): void\n    {\n        $this->newEntities = [];\n        $this->dirtyEntities = [];\n        $this->removedEntities = [];\n    }\n\n    private function getMapperForEntity(object $entity): DataMapperInterface\n    {\n        $className = get_class($entity);\n        if (!isset($this->entityMappers[$className])) {\n            throw new \\RuntimeException(\"Entity i\u00e7in DataMapper bulunamad\u0131: \" . $className);\n        }\n        return $this->entityMappers[$className];\n    }\n\n    private function getTableName(object $entity): string\n    {\n        \/\/ Basit bir isimlendirme kural\u0131: User -> users\n        \/\/ Ger\u00e7ek bir ORM'de bu, Entity'nin bir \u00f6zelli\u011fi veya konfig\u00fcrasyondan gelir.\n        $className = (new \\ReflectionClass($entity))->getShortName();\n        return strtolower($className) . 's';\n    }\n}\n<\/pre>\n
        <\/code><\/p>\n
        Bu UnitOfWork<\/code>, varl\u0131klar\u0131n durumunu izler ve commit()<\/code> \u00e7a\u011fr\u0131ld\u0131\u011f\u0131nda, DatabaseDriverInterface<\/code>'i kullanarak ilgili veritaban\u0131 i\u015flemlerini ger\u00e7ekle\u015ftirir. Bu sayede, i\u015f mant\u0131\u011f\u0131 katman\u0131n\u0131z do\u011frudan veritaban\u0131 i\u015flemleriyle u\u011fra\u015fmak zorunda kalmaz, sadece varl\u0131k nesnelerini de\u011fi\u015ftirir ve UnitOfWork<\/code>'e bildirir. Bu yakla\u015f\u0131m, karma\u015f\u0131k i\u015f ak\u0131\u015flar\u0131nda bile veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve performans\u0131 korumaya yard\u0131mc\u0131 olur. Ayr\u0131ca, transaction y\u00f6netimi sayesinde olas\u0131 hatalarda t\u00fcm de\u011fi\u015fikliklerin geri al\u0131nmas\u0131n\u0131 sa\u011flar.<\/p>\n
        Ger\u00e7ek D\u00fcnya Senaryosu: E-ticaret Projesinde S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Kullan\u0131m\u0131<\/h2>\n
        S\u00fcr\u00fcc\u00fc bilin\u00e7li bir ORM mimarisinin ger\u00e7ek de\u011ferini anlamak i\u00e7in, bir e-ticaret platformu senaryosunu inceleyelim. Diyelim ki, yeni bir e-ticaret platformu geli\u015ftiriyorsunuz. Ba\u015flang\u0131\u00e7ta, d\u00fc\u015f\u00fck maliyet ve geli\u015ftirme kolayl\u0131\u011f\u0131 nedeniyle MySQL veritaban\u0131n\u0131 tercih ettiniz. Ancak i\u015fler b\u00fcy\u00fcd\u00fck\u00e7e ve platform daha fazla kullan\u0131c\u0131ya ula\u015ft\u0131k\u00e7a, performans ve \u00f6l\u00e7eklenebilirlik endi\u015feleriyle birlikte, baz\u0131 m\u00fc\u015fterilerinizin \u015firket i\u00e7i altyap\u0131lar\u0131 gere\u011fi PostgreSQL veya hatta SQL Server kullanma talepleri ortaya \u00e7\u0131k\u0131yor. E\u011fer manuel SQL sorgular\u0131 yazm\u0131\u015f olsayd\u0131n\u0131z, bu durum projenizin veri eri\u015fim katman\u0131n\u0131 tamamen yeniden yazma kabusunu beraberinde getirirdi.<\/p>\n
        S\u00fcr\u00fcc\u00fc bilin\u00e7li ORM mimarimiz sayesinde, bu ge\u00e7i\u015f olduk\u00e7a y\u00f6netilebilir hale gelir. Temelde, veritaban\u0131 s\u00fcr\u00fcc\u00fcleri (MySqlDriver<\/code>, PostgreSqlDriver<\/code>, SqlServerDriver<\/code>) ayn\u0131 DatabaseDriverInterface<\/code>'i uygulad\u0131\u011f\u0131ndan ve Query Builder'\u0131m\u0131z ile Data Mapper'lar\u0131m\u0131z bu soyutlamaya ba\u011f\u0131ml\u0131 oldu\u011fundan, veritaban\u0131 de\u011fi\u015fikli\u011fi sadece bir konfig\u00fcrasyon de\u011fi\u015fikli\u011fine indirgenir. \u00d6rne\u011fin, config.php<\/code> dosyan\u0131zda sadece kullanmak istedi\u011finiz s\u00fcr\u00fcc\u00fcy\u00fc ve ba\u011flant\u0131 ayarlar\u0131n\u0131 belirtmeniz yeterlidir:<\/p>\n
        \n\/\/ config.php\nreturn [\n    'database' => [\n        'driver' => 'mysql', \/\/ veya 'postgresql', 'sqlserver'\n        'mysql' => [\n            'host' => 'localhost',\n            'dbname' => 'ecommerce_db',\n            'user' => 'root',\n            'pass' => 'password',\n            'charset' => 'utf8mb4'\n        ],\n        'postgresql' => [\n            'host' => 'localhost',\n            'dbname' => 'ecommerce_pg_db',\n            'user' => 'pguser',\n            'pass' => 'pgpassword',\n            'charset' => 'utf8'\n        ],\n        \/\/ ... di\u011fer s\u00fcr\u00fcc\u00fcler\n    ]\n];\n<\/pre>\n
        <\/code><\/p>\n
        Uygulaman\u0131z\u0131n ba\u015flang\u0131\u00e7 noktas\u0131nda (\u00f6rne\u011fin bir Dependency Injection konteyneri kullanarak), bu konfig\u00fcrasyona g\u00f6re uygun s\u00fcr\u00fcc\u00fcy\u00fc dinamik olarak y\u00fckleyebilirsiniz:<\/p>\n
        \n\/\/ Uygulama ba\u015flang\u0131c\u0131\n$config = require 'config.php';\n$driverType = $config['database']['driver'];\n$driverConfig = $config['database'][$driverType];\n\n$driver = match ($driverType) {\n    'mysql' => new MySqlDriver(),\n    'postgresql' => new PostgreSqlDriver(),\n    \/\/ ...\n    default => throw new \\InvalidArgumentException(\"Desteklenmeyen veritaban\u0131 s\u00fcr\u00fcc\u00fcs\u00fc: \" . $driverType),\n};\n$driver->connect($driverConfig);\n\n$queryBuilder = new GenericQueryBuilder($driver); \/\/ veya s\u00fcr\u00fcc\u00fcye \u00f6zel QueryBuilder\n$userDataMapper = new UserDataMapper();\n$userRepository = new UserRepository($driver, $userDataMapper, $queryBuilder);\n$unitOfWork = new UnitOfWork($driver);\n$unitOfWork->registerMapper(User::class, $userDataMapper);\n\n\/\/ Kullan\u0131c\u0131 i\u015flemleri\n$users = $userRepository->findAll();\nforeach ($users as $user) {\n    echo $user->getUsername() . \"\\n\";\n}\n\n$newUser = new User(null, \"new_user\", \"new@example.com\", new \\DateTimeImmutable());\n$userRepository->add($newUser); \/\/ UserRepository i\u00e7inden UnitOfWork'e kaydolur\n$unitOfWork->commit();\n<\/pre>\n
        <\/code><\/p>\n
        Bu senaryoda, bir kullan\u0131c\u0131n\u0131n \u00fcr\u00fcn sipari\u015f etme ak\u0131\u015f\u0131n\u0131 d\u00fc\u015f\u00fcnelim: Kullan\u0131c\u0131 sipari\u015f verir, stok g\u00fcncellenir, \u00f6deme kayd\u0131 olu\u015fturulur. T\u00fcm bu i\u015flemler, UnitOfWork<\/code> i\u00e7inde bir veritaban\u0131 transaction'\u0131 olarak y\u00f6netilir. E\u011fer stokta yeterli \u00fcr\u00fcn yoksa veya \u00f6deme ba\u015far\u0131s\u0131z olursa, UnitOfWork<\/code> t\u00fcm de\u011fi\u015fiklikleri geri al\u0131r ve veritaban\u0131n\u0131n tutarl\u0131 kalmas\u0131n\u0131 sa\u011flar. Ayr\u0131ca, SQL Server'\u0131n TOP<\/code> sentaks\u0131na ihtiya\u00e7 duydu\u011funuz bir performans kritik sorgu varsa, sadece SqlServerQueryBuilder<\/code> s\u0131n\u0131f\u0131ndaki limit()<\/code> veya build()<\/code> metodunu bu spesifik sentaks\u0131 \u00fcretecek \u015fekilde \u00f6zelle\u015ftirmeniz yeterlidir. Uygulaman\u0131z\u0131n di\u011fer katmanlar\u0131 bu de\u011fi\u015fiklikten etkilenmez. Bu esneklik, uzun vadeli projelerde s\u00fcrd\u00fcr\u00fclebilirli\u011fi ve adaptasyonu inan\u0131lmaz derecede kolayla\u015ft\u0131r\u0131r.<\/p>\n
        \n  Uzman \u0130pucu: Front-end taraf\u0131nda veritaban\u0131ndan \u00e7ekilen verileri mobil cihazlara duyarl\u0131 bir \u015fekilde sunmak i\u00e7in, modern CSS \u00f6zelliklerinden faydalan\u0131n. \u00d6rne\u011fin, <\/p>\n
        ...<\/div>\n
        <\/code> yap\u0131s\u0131 i\u00e7inde tablolar\u0131n\u0131z\u0131 bar\u0131nd\u0131r\u0131rken, CSS'te a\u015fa\u011f\u0131daki gibi bir medya sorgusu kullanabilirsiniz:<\/p>\n
        \n@media screen and (max-width: 768px) {\n  .responsive-table table,\n  .responsive-table thead,\n  .responsive-table tbody,\n  .responsive-table th,\n  .responsive-table td,\n  .responsive-table tr {\n    display: block;\n  }\n  .responsive-table thead tr {\n    position: absolute;\n    top: -9999px;\n    left: -9999px;\n  }\n  .responsive-table td {\n    border: none;\n    border-bottom: 1px solid #eee;\n    position: relative;\n    padding-left: 50%;\n    text-align: right;\n  }\n  .responsive-table td:before {\n    position: absolute;\n    top: 6px;\n    left: 6px;\n    width: 45%;\n    padding-right: 10px;\n    white-space: nowrap;\n    text-align: left;\n    font-weight: bold;\n    content: attr(data-label); \/* Her td i\u00e7in \u00f6zel bir etiket *\/\n  }\n}\n  <\/pre>\n
        <\/code>
        \n  Bu \u015fekilde, sunulan veriler sadece i\u015f mant\u0131\u011f\u0131 a\u00e7\u0131s\u0131ndan de\u011fil, kullan\u0131c\u0131 deneyimi a\u00e7\u0131s\u0131ndan da modern standartlara uygun hale getirilebilir. ORM, verileri temiz bir \u015fekilde sa\u011flamakla y\u00fck\u00fcml\u00fcyken, sunum katman\u0131 bu verileri en iyi \u015fekilde g\u00f6stermelidir.\n<\/div>\n
        Geli\u015fmi\u015f Konular ve Optimizasyonlar: ORM'inizi Nas\u0131l Daha G\u00fc\u00e7l\u00fc Hale Getirirsiniz?<\/h2>\n
        Temiz ve s\u00fcr\u00fcc\u00fc bilin\u00e7li bir ORM mimarisi olu\u015fturmak harika bir ba\u015flang\u0131\u00e7t\u0131r, ancak ger\u00e7ek d\u00fcnya uygulamalar\u0131nda performans, \u00f6l\u00e7eklenebilirlik ve esneklik gibi konular\u0131 ele almak i\u00e7in daha ileri d\u00fczey tekniklere ihtiya\u00e7 duyulur. Bu b\u00f6l\u00fcmde, ORM'inizi daha g\u00fc\u00e7l\u00fc ve verimli hale getirecek baz\u0131 geli\u015fmi\u015f konular\u0131 ve optimizasyonlar\u0131 inceleyece\u011fiz.<\/p>\n
        \u00d6nbellekleme (Caching) Nas\u0131l Entegre Edilir?<\/h3>\n
        Veritaban\u0131 i\u015flemleri genellikle uygulaman\u0131n en yava\u015f k\u0131s\u0131mlar\u0131ndan biridir. S\u0131k\u00e7a eri\u015filen ancak nadiren de\u011fi\u015fen veriler i\u00e7in \u00f6nbellekleme (caching) kullanmak performans\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir. Bir ORM'e \u00f6nbellekleme entegre etmenin iki ana seviyesi vard\u0131r:<\/p>\n
          \n
        1. Birinci Seviye \u00d6nbellek (First-Level Cache):<\/strong> Genellikle Unit of Work i\u00e7inde bulunur ve bir HTTP iste\u011fi s\u00fcresince ayn\u0131 varl\u0131\u011f\u0131n birden fazla kez veritaban\u0131ndan \u00e7ekilmesini engeller. E\u011fer bir varl\u0131k zaten Unit of Work taraf\u0131ndan izleniyorsa, veritaban\u0131na gitmeden do\u011frudan \u00f6nbellekten d\u00f6nd\u00fcr\u00fcl\u00fcr.<\/li>\n
        2. \u0130kinci Seviye \u00d6nbellek (Second-Level Cache):<\/strong> Birden fazla HTTP iste\u011fi veya t\u00fcm uygulama boyunca \u00f6nbelleklenen verilerdir. Redis, Memcached veya APCu gibi harici bir \u00f6nbellek deposu kullan\u0131larak uygulan\u0131r. \u00d6zellikle s\u0131k okunan ve nadiren yaz\u0131lan veriler (\u00f6rne\u011fin, \u00fcr\u00fcn kategorileri, ayarlar, pop\u00fcler \u00fcr\u00fcn listeleri) i\u00e7in \u00e7ok etkilidir.<\/li>\n<\/ol>\n
          \u0130kinci seviye \u00f6nbellekleme entegrasyonu i\u00e7in, ORM'iniz, bir varl\u0131\u011f\u0131 veritaban\u0131ndan \u00e7ekmeden \u00f6nce \u00f6nbelle\u011fi kontrol etmeli, \u00f6nbellekte yoksa veritaban\u0131ndan \u00e7ekip \u00f6nbelle\u011fe almal\u0131 ve sonra d\u00f6nd\u00fcrmelidir. Varl\u0131k g\u00fcncellendi\u011finde veya silindi\u011finde, ilgili \u00f6nbelle\u011fin temizlenmesi (invalidasyon) kritik \u00f6nem ta\u015f\u0131r. \u00d6nbellek entegrasyonu, Repository<\/code> katman\u0131nda veya do\u011frudan QueryBuilder<\/code> i\u00e7inde bir \u00f6nbellek servisi (CacheInterface<\/code>) enjekte edilerek yap\u0131labilir.<\/p>\n
          \ninterface CacheInterface\n{\n    public function get(string $key): mixed;\n    public function set(string $key, mixed $value, int $ttl = 0): bool;\n    public function delete(string $key): bool;\n}\n\n\/\/ Bir Repository i\u00e7inde \u00f6nbellek kullan\u0131m\u0131\nclass ProductRepository\n{\n    private DatabaseDriverInterface $driver;\n    private ProductDataMapper $mapper;\n    private QueryBuilderInterface $queryBuilder;\n    private CacheInterface $cache; \/\/ Cache servisi\n\n    public function __construct(DatabaseDriverInterface $driver, ProductDataMapper $mapper, QueryBuilderInterface $queryBuilder, CacheInterface $cache)\n    {\n        $this->driver = $driver;\n        $this->mapper = $mapper;\n        $this->queryBuilder = $queryBuilder;\n        $this->cache = $cache;\n    }\n\n    public function findById(int $id): ?Product\n    {\n        $cacheKey = \"product_{$id}\";\n        $cachedProductData = $this->cache->get($cacheKey);\n\n        if ($cachedProductData) {\n            return $this->mapper->mapRowToObject($cachedProductData);\n        }\n\n        $query = $this->queryBuilder->select()->from('products')->where('id', '=', $id)->build();\n        $result = $this->driver->query($query['sql'], $query['params']);\n\n        if (empty($result)) {\n            return null;\n        }\n\n        $product = $this->mapper->mapRowToObject($result[0]);\n        $this->cache->set($cacheKey, $result[0], 3600); \/\/ 1 saat \u00f6nbellekte tut\n        return $product;\n    }\n\n    \/\/ \u00dcr\u00fcn g\u00fcncellendi\u011finde veya silindi\u011finde \u00f6nbelle\u011fi temizlemeyi unutmay\u0131n\n    public function update(Product $product): void\n    {\n        \/\/ ... g\u00fcncelleme i\u015flemleri ...\n        $this->cache->delete(\"product_{$product->getId()}\");\n    }\n}\n<\/pre>\n
          <\/code><\/p>\n
          Lazy Loading ve Eager Loading Stratejileri Nelerdir?<\/h3>\n
          \u0130li\u015fkili verileri (\u00f6rne\u011fin, bir kullan\u0131c\u0131n\u0131n sipari\u015fleri veya bir \u00fcr\u00fcn\u00fcn kategorileri) ne zaman y\u00fckleyece\u011fimiz, ORM performans\u0131n\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde etkileyen \u00f6nemli bir karard\u0131r. \u0130ki temel strateji vard\u0131r:<\/p>\n
            \n
          1. Lazy Loading (Tembel Y\u00fckleme):<\/strong> \u0130li\u015fkili veri, yaln\u0131zca eri\u015fildi\u011finde y\u00fcklenir. \u00d6rne\u011fin, $user->getOrders()<\/code> \u00e7a\u011fr\u0131ld\u0131\u011f\u0131nda, veritaban\u0131na bir sorgu g\u00f6nderilir ve kullan\u0131c\u0131n\u0131n sipari\u015fleri y\u00fcklenir. Faydas\u0131, gereksiz verilerin y\u00fcklenmesini \u00f6nlemesidir. Dezavantaj\u0131 ise \"N+1 problemi\"dir: Bir liste i\u00e7indeki her varl\u0131k i\u00e7in ili\u015fkili veriye eri\u015fti\u011finizde, N adet ek sorgu \u00e7al\u0131\u015f\u0131r (N varl\u0131k say\u0131s\u0131 + 1 ana sorgu). Bu, performans\u0131 ciddi \u015fekilde etkileyebilir.<\/li>\n
          2. Eager Loading (Hevesli Y\u00fckleme):<\/strong> \u0130li\u015fkili veriler, ana varl\u0131kla birlikte tek bir sorguda (genellikle JOIN kullanarak) veya ayr\u0131 ancak optimize edilmi\u015f sorgularla \u00f6nceden y\u00fcklenir. \u00d6rne\u011fin, t\u00fcm kullan\u0131c\u0131lar\u0131 ve onlar\u0131n sipari\u015flerini tek bir sorguda \u00e7ekmek. Bu, N+1 sorununu \u00f6nler ve genellikle daha iyi performans sunar. Ancak, her zaman t\u00fcm ili\u015fkili veriye ihtiyac\u0131n\u0131z yoksa gereksiz veri y\u00fcklenmesine neden olabilir.<\/li>\n<\/ol>\n
            ORM'iniz, QueryBuilder<\/code> arac\u0131l\u0131\u011f\u0131yla bu stratejileri desteklemelidir. \u00d6rne\u011fin, QueryBuilder<\/code>'a bir with()<\/code> metodu ekleyerek eager loading'i etkinle\u015ftirebilirsiniz:<\/p>\n
            \n\/\/ Eager Loading \u00f6rne\u011fi\n$usersWithOrders = $userRepository->findAllWithOrders(); \/\/ Repository i\u00e7inde with('orders') \u00e7a\u011fr\u0131labilir\n\/\/ Veya do\u011frudan QueryBuilder \u00fczerinden:\n\/\/ $queryBuilder->select(['u.*', 'o.*'])->from('users u')->leftJoin('orders o', 'u.id', '=', 'o.user_id')->build();\n<\/pre>\n
            <\/code><\/p>\n
            Bu, userRepository<\/code>'nin findAllWithOrders()<\/code> metodunun, kullan\u0131c\u0131lar\u0131 ve ilgili sipari\u015flerini tek bir sorguda (JOIN ile) veya iki ayr\u0131 sorguda (birincisi t\u00fcm kullan\u0131c\u0131lar i\u00e7in, ikincisi bu kullan\u0131c\u0131lar\u0131n ID'lerini kullanarak t\u00fcm sipari\u015fler i\u00e7in) \u00e7ekmesini sa\u011flar. Veritaban\u0131 s\u00fcr\u00fcc\u00fcn\u00fcz\u00fcn ve Query Builder'\u0131n\u0131z\u0131n yeteneklerine ba\u011fl\u0131 olarak, en uygun eager loading y\u00f6ntemini se\u00e7melisiniz.<\/p>\n
            \u00c7oklu Veritaban\u0131 Deste\u011fi ve Dinamik S\u00fcr\u00fcc\u00fc Se\u00e7imi Nas\u0131l Yap\u0131l\u0131r?<\/h3>\n
            Baz\u0131 karma\u015f\u0131k uygulamalar, farkl\u0131 mod\u00fcller veya mikro servisler i\u00e7in birden fazla veritaban\u0131 kullanabilir. \u00d6rne\u011fin, kullan\u0131c\u0131 y\u00f6netimi i\u00e7in bir veritaban\u0131, \u00fcr\u00fcn katalo\u011fu i\u00e7in ba\u015fka bir veritaban\u0131. S\u00fcr\u00fcc\u00fc bilin\u00e7li ORM'imiz, bu senaryoyu kolayca y\u00f6netebilir. Yap\u0131land\u0131rma dosyan\u0131zda birden fazla veritaban\u0131 ba\u011flant\u0131s\u0131 tan\u0131mlayabilir ve daha sonra \u00e7al\u0131\u015fma zaman\u0131nda veya Dependency Injection (DI) konteyneri arac\u0131l\u0131\u011f\u0131yla do\u011fru ba\u011flant\u0131y\u0131 enjekte edebilirsiniz.<\/p>\n
            \n\/\/ config.php (\u00c7oklu veritaban\u0131 yap\u0131land\u0131rmas\u0131)\nreturn [\n    'databases' => [\n        'default' => [\n            'driver' => 'mysql',\n            'host' => 'localhost',\n            'dbname' => 'main_db',\n            'user' => 'root',\n            'pass' => 'password',\n            'charset' => 'utf8mb4'\n        ],\n        'reporting' => [ \/\/ Raporlama i\u00e7in ayr\u0131 bir PostgreSQL veritaban\u0131\n            'driver' => 'postgresql',\n            'host' => 'report_db_server',\n            'dbname' => 'reports',\n            'user' => 'reportuser',\n            'pass' => 'reportpass',\n            'charset' => 'utf8'\n        ]\n    ]\n];\n\n\/\/ Uygulama ba\u015flang\u0131c\u0131 veya bir service provider i\u00e7inde\nclass DatabaseConnectionManager\n{\n    private array $connections = [];\n    private array $config;\n\n    public function __construct(array $config)\n    {\n        $this->config = $config['databases'];\n    }\n\n    public function getConnection(string $name = 'default'): DatabaseDriverInterface\n    {\n        if (!isset($this->connections[$name])) {\n            $dbConfig = $this->config[$name];\n            $driver = match ($dbConfig['driver']) {\n                'mysql' => new MySqlDriver(),\n                'postgresql' => new PostgreSqlDriver(),\n                default => throw new \\InvalidArgumentException(\"Desteklenmeyen s\u00fcr\u00fcc\u00fc: \" . $dbConfig['driver']),\n            };\n            $driver->connect($dbConfig);\n            $this->connections[$name] = $driver;\n        }\n        return $this->connections[$name];\n    }\n}\n\n\/\/ Kullan\u0131m \u00f6rne\u011fi\n$dbManager = new DatabaseConnectionManager(require 'config.php');\n$mainDbDriver = $dbManager->getConnection('default');\n$reportDbDriver = $dbManager->getConnection('reporting');\n\n\/\/ Ana veritaban\u0131ndan kullan\u0131c\u0131 \u00e7ek\n$userRepository = new UserRepository($mainDbDriver, new UserDataMapper(), new GenericQueryBuilder($mainDbDriver));\n$users = $userRepository->findAll();\n\n\/\/ Raporlama veritaban\u0131ndan \u00f6zel rapor \u00e7ek\n\/\/ Bunun i\u00e7in ayr\u0131 bir ReportRepository ve ReportDataMapper gerekebilir\n$reportQueryBuilder = new GenericQueryBuilder($reportDbDriver);\n$monthlyReports = $reportDbDriver->query($reportQueryBuilder->select()->from('monthly_reports')->build()['sql']);\n<\/pre>\n
            <\/code><\/p>\n
            Bu yakla\u015f\u0131m, uygulaman\u0131z\u0131n farkl\u0131 b\u00f6l\u00fcmlerinin, ihtiya\u00e7lar\u0131na en uygun veritaban\u0131 \u00e7\u00f6z\u00fcm\u00fcn\u00fc kullanmas\u0131na olanak tan\u0131r. Her veritaban\u0131 ba\u011flant\u0131s\u0131, kendi s\u00fcr\u00fcc\u00fcs\u00fc ve yap\u0131land\u0131rmas\u0131yla izole edilir, bu da sistemin genel esnekli\u011fini ve bak\u0131m kolayl\u0131\u011f\u0131n\u0131 art\u0131r\u0131r. Geli\u015fmi\u015f optimizasyonlar ve esneklik, ORM'inizin sadece bir veritaban\u0131 soyutlama arac\u0131 olmaktan \u00e7\u0131k\u0131p, uygulaman\u0131z\u0131n veri katman\u0131n\u0131n stratejik bir par\u00e7as\u0131 haline gelmesini sa\u011flar.<\/p>\n
            Sonu\u00e7: Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM'in Gelece\u011fi<\/h2>\n
            Bu makale boyunca, PHP'de temiz ve s\u00fcr\u00fcc\u00fc bilin\u00e7li bir ORM mimarisinin neden gerekli oldu\u011funu, nas\u0131l tasarlanaca\u011f\u0131n\u0131 ve ger\u00e7ek d\u00fcnya senaryolar\u0131nda nas\u0131l uygulanaca\u011f\u0131n\u0131 detayl\u0131 bir \u015fekilde inceledik. G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, bu yakla\u015f\u0131m sadece kod tekrar\u0131n\u0131 azaltmakla ve geli\u015ftirici \u00fcretkenli\u011fini art\u0131rmakla kalm\u0131yor, ayn\u0131 zamanda g\u00fcvenlik, bak\u0131m kolayl\u0131\u011f\u0131 ve en \u00f6nemlisi veritaban\u0131 ba\u011f\u0131ms\u0131zl\u0131\u011f\u0131 sa\u011flayarak uygulaman\u0131z\u0131n gelece\u011fe d\u00f6n\u00fckl\u00fc\u011f\u00fcn\u00fc garanti alt\u0131na al\u0131yor. Bir e-ticaret platformunda farkl\u0131 veritaban\u0131 gereksinimlerine nas\u0131l kolayca adapte olunabilece\u011fini, sorgu olu\u015fturucular\u0131n ve veri e\u015fleyicilerin bu s\u00fcre\u00e7te nas\u0131l merkezi bir rol oynad\u0131\u011f\u0131n\u0131 ele ald\u0131k. Ayr\u0131ca, \u00f6nbellekleme, lazy\/eager loading ve \u00e7oklu veritaban\u0131 deste\u011fi gibi geli\u015fmi\u015f optimizasyonlarla ORM'inizi daha da g\u00fc\u00e7l\u00fc hale getirme yollar\u0131n\u0131 ke\u015ffettik.<\/p>\n
            Temiz bir mimari, sorumluluklar\u0131n net bir \u015fekilde ayr\u0131\u015ft\u0131r\u0131lmas\u0131n\u0131 gerektirir: veritaban\u0131 s\u00fcr\u00fcc\u00fcleri, sorgu olu\u015fturucular, veri e\u015fleyiciler, varl\u0131klar ve depolar. S\u00fcr\u00fcc\u00fc bilin\u00e7li olmak ise, bu katmanlar\u0131n temel veritaban\u0131 leh\u00e7elerini ve \u00f6zelliklerini anlay\u0131p soyutlayarak, PHP uygulaman\u0131z\u0131n PostgreSQL'den MySQL'e, oradan SQL Server'a veya ba\u015fka bir ili\u015fkisel veritaban\u0131na sorunsuz bir \u015fekilde ge\u00e7i\u015f yapabilmesini sa\u011flar. Bu mimari, test edilebilirli\u011fi art\u0131r\u0131r, \u00e7\u00fcnk\u00fc her bile\u015fen kendi ba\u015f\u0131na test edilebilir ve ba\u011f\u0131ml\u0131l\u0131klar enjeksiyon yoluyla y\u00f6netilir. Gelecekte, NoSQL veritabanlar\u0131n\u0131n y\u00fckseli\u015fiyle birlikte, bu t\u00fcr soyutlamalar\u0131n NoSQL \u00e7\u00f6z\u00fcmlerine adapte edilmesi veya GraphQL gibi yeni API paradigmalar\u0131yla entegrasyonu, ORM benzeri ara\u00e7lar\u0131n evriminde yeni ufuklar a\u00e7acakt\u0131r. \u00d6nemli olan, veri eri\u015fim katman\u0131n\u0131 her zaman uygulaman\u0131z\u0131n geri kalan\u0131ndan ba\u011f\u0131ms\u0131z ve esnek tutmakt\u0131r. Bu sayede, teknolojiler de\u011fi\u015ftik\u00e7e uygulaman\u0131z da onlarla birlikte evrilebilir ve i\u015f ihtiya\u00e7lar\u0131na h\u0131zla yan\u0131t verebilir.<\/p>\n
            S\u0131k\u00e7a Sorulan Sorular<\/h3>\n
            \n
            Soru 1: ORM kullanmak her zaman iyi bir fikir midir?<\/dt>\n
            Cevap: \u00c7o\u011fu durumda evet, \u00e7\u00fcnk\u00fc \u00fcretkenli\u011fi, bak\u0131m\u0131 ve g\u00fcvenli\u011fi art\u0131r\u0131r. Ancak, \u00e7ok performans kritik ve karma\u015f\u0131k sorgular\u0131n oldu\u011fu durumlarda veya veritaban\u0131n\u0131n spesifik \u00f6zelliklerinden faydalanmak istedi\u011finizde, do\u011frudan SQL yazmak daha iyi bir se\u00e7enek olabilir. ORM'ler, performans overhead'i getirebilir, bu nedenle her zaman dengeli bir yakla\u015f\u0131m benimsemek \u00f6nemlidir.<\/dd>\n
            Soru 2: S\u00fcr\u00fcc\u00fc bilin\u00e7li mimarinin ana faydas\u0131 nedir?<\/dt>\n
            Cevap: Ana faydas\u0131, veritaban\u0131 sa\u011flay\u0131c\u0131s\u0131ndan ba\u011f\u0131ms\u0131zl\u0131k sa\u011flamas\u0131d\u0131r. Uygulaman\u0131z\u0131n temel i\u015f mant\u0131\u011f\u0131, altta yatan veritaban\u0131n\u0131n t\u00fcr\u00fcn\u00fc bilmek zorunda kalmaz. Bu, gelecekte farkl\u0131 bir veritaban\u0131na ge\u00e7i\u015f yapman\u0131z gerekti\u011finde veya birden fazla veritaban\u0131 t\u00fcr\u00fcn\u00fc desteklemeniz gerekti\u011finde b\u00fcy\u00fck bir esneklik ve kolayl\u0131k sunar.<\/dd>\n
            Soru 3: ORM'de performans sorunlar\u0131n\u0131 nas\u0131l giderebilirim?<\/dt>\n
            Cevap: Performans sorunlar\u0131n\u0131 gidermek i\u00e7in \u00f6nbellekleme (birinci ve ikinci seviye), do\u011fru y\u00fckleme stratejileri (eager loading ile N+1 problemini \u00e7\u00f6zme), indekslerin etkin kullan\u0131m\u0131 ve gerekti\u011finde ORM'i atlayarak do\u011frudan optimize edilmi\u015f SQL sorgular\u0131 \u00e7al\u0131\u015ft\u0131rmak gibi y\u00f6ntemler kullanabilirsiniz. Ayr\u0131ca, iyi tasarlanm\u0131\u015f bir veritaban\u0131 \u015femas\u0131 ve d\u00fczenli sorgu optimizasyonu da kritiktir.<\/dd>\n
            Soru 4: Kendi ORM'imi yazmal\u0131 m\u0131y\u0131m, yoksa mevcut bir k\u00fct\u00fcphaneyi mi kullanmal\u0131y\u0131m?<\/dt>\n
            Cevap: \u00c7o\u011fu durumda, Doctrine, Eloquent gibi mevcut ve olgun ORM k\u00fct\u00fcphanelerini kullanmak daha mant\u0131kl\u0131d\u0131r. Bu k\u00fct\u00fcphaneler, y\u00fczlerce geli\u015ftiricinin tecr\u00fcbesiyle \u015fekillenmi\u015f, geni\u015f \u00f6zellik setleri sunan ve iyi test edilmi\u015f \u00e7\u00f6z\u00fcmlerdir. Kendi ORM'inizi yazmak, genellikle zaman al\u0131c\u0131 ve karma\u015f\u0131k bir i\u015ftir ve ancak \u00e7ok spesifik ihtiya\u00e7lar\u0131n\u0131z varsa veya \u00f6\u011frenme amac\u0131yla yap\u0131lmal\u0131d\u0131r.<\/dd>\n
            Soru 5: Hangi durumlarda raw SQL tercih edilmeli?<\/dt>\n
            Cevap: ORM'in sundu\u011fu soyutlama katman\u0131n\u0131n performans veya esneklik a\u00e7\u0131s\u0131ndan yetersiz kald\u0131\u011f\u0131 \u00f6zel durumlar (\u00f6rne\u011fin, \u00e7ok karma\u015f\u0131k raporlama sorgular\u0131, depolanm\u0131\u015f prosed\u00fcrlerin \u00e7a\u011fr\u0131lmas\u0131 veya veritaban\u0131na \u00f6zel optimize edilmi\u015f fonksiyonlar\u0131n kullan\u0131lmas\u0131) i\u00e7in raw SQL tercih edilebilir. Bu gibi durumlarda, yine de PDO gibi g\u00fcvenli y\u00f6ntemlerle parametre ba\u011flamay\u0131 kullanarak SQL enjeksiyonu riskinden ka\u00e7\u0131nmal\u0131s\u0131n\u0131z. Temiz bir ORM mimarisinde, raw SQL'i do\u011frudan Driver Layer \u00fczerinden \u00e7al\u0131\u015ft\u0131rmak i\u00e7in bir mekanizma her zaman bulunmal\u0131d\u0131r.<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[133],"tags":[],"class_list":{"0":"post-34262","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-php","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nPHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f<\/title>\n<meta name=\"description\" content=\"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de "Temiz" ve "S\u00fcr\u00fcc\u00fc Bilin\u00e7li" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f\" \/>\n<meta property=\"og:description\" content=\"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de "Temiz" ve "S\u00fcr\u00fcc\u00fc Bilin\u00e7li" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-13T23:31:17+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"30 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"PHP’de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f\",\"datePublished\":\"2025-11-13T23:31:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\"},\"wordCount\":4211,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"PHP\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\",\"name\":\"PHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-13T23:31:17+00:00\",\"description\":\"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de \\\"Temiz\\\" ve \\\"S\u00fcr\u00fcc\u00fc Bilin\u00e7li\\\" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PHP’de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f","description":"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de \"Temiz\" ve \"S\u00fcr\u00fcc\u00fc Bilin\u00e7li\" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/","og_locale":"tr_TR","og_type":"article","og_title":"PHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f","og_description":"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de \"Temiz\" ve \"S\u00fcr\u00fcc\u00fc Bilin\u00e7li\" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.","og_url":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-13T23:31:17+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"30 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"PHP’de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f","datePublished":"2025-11-13T23:31:17+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/"},"wordCount":4211,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["PHP"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/","url":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/","name":"PHP'de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-13T23:31:17+00:00","description":"Veritaban\u0131 i\u015flemleri, modern web uygulamalar\u0131n\u0131n karma\u015f\u0131k ve hata yapmaya a\u00e7\u0131k bir par\u00e7as\u0131 olabilir. Peki, uygulaman\u0131z\u0131n farkl\u0131 veritaban\u0131 t\u00fcrleriyle sorunsuz bir \u015fekilde konu\u015fmas\u0131n\u0131 sa\u011flarken, ayn\u0131 zamanda kodu daha okunabilir ve s\u00fcrd\u00fcr\u00fclebilir hale getirecek sihirli bir y\u00f6ntem var m\u0131? Bu makalede, PHP'de \"Temiz\" ve \"S\u00fcr\u00fcc\u00fc Bilin\u00e7li\" bir ORM (Object-Relational Mapping) mimarisinin nas\u0131l in\u015fa edilece\u011fini, ger\u00e7ek d\u00fcnya senaryolar\u0131yla ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z.","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/phpde-temiz-ve-surucu-bilincli-orm-mimarisi-derinlemesine-bir-bakis\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PHP’de Temiz ve S\u00fcr\u00fcc\u00fc Bilin\u00e7li ORM Mimarisi: Derinlemesine Bir Bak\u0131\u015f"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34262","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=34262"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34262\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=34262"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=34262"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=34262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}