{"id":34734,"date":"2019-10-31T22:00:06","date_gmt":"2019-10-31T19:00:06","guid":{"rendered":"https:\/\/prohoster.info\/blog\/sravnenie-i-vybor-sistem-migratsii-dannyh\/"},"modified":"2019-10-31T22:00:06","modified_gmt":"2019-10-31T19:00:06","slug":"sravnenie-i-vybor-sistem-migratsii-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/sravnenie-i-vybor-sistem-migratsii-dannyh","title":{"rendered":"Krahasimi dhe zgjedhja e sistemeve t\u00eb migrimit t\u00eb t\u00eb dh\u00ebnave.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Krahasimi dhe zgjedhja e sistemeve t\u00eb migrimit t\u00eb t\u00eb dh\u00ebnave.<\/h2>\n

\n\"Krahasimi
\n
\nModeli i t\u00eb dh\u00ebnave n\u00eb procesin e zhvillimit ka vetin\u00eb t\u00eb ndryshoj\u00eb, dhe n\u00eb nj\u00eb moment ai ndalon s\u00eb qenuri n\u00eb p\u00ebrputhje me baz\u00ebn e t\u00eb dh\u00ebnave. Sigurisht, mund t\u00eb fshini DB-n\u00eb, dhe at\u00ebher\u00eb ORM do t\u00eb krijoj\u00eb nj\u00eb version t\u00eb ri q\u00eb do t\u00eb p\u00ebrputhet me modelin, por nj\u00eb procedur\u00eb e till\u00eb do t\u00eb \u00e7oj\u00eb n\u00eb humbjen e t\u00eb dh\u00ebnave ekzistuese. K\u00ebshtu, funksioni i sistemit t\u00eb migrimit p\u00ebrfshin sinkronizimin e skem\u00ebs me modelin e t\u00eb dh\u00ebnave n\u00eb aplikacion pa humbjen e t\u00eb dh\u00ebnave ekzistuese.<\/p>\n

N\u00eb k\u00ebt\u00eb artikull do t\u00eb shqyrtojm\u00eb mjete t\u00eb ndryshme p\u00ebr menaxhimin e migrimeve t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave. Shpresojm\u00eb q\u00eb ky p\u00ebrmbledhje do t\u00eb jet\u00eb e dobishme p\u00ebr zhvilluesit q\u00eb jan\u00eb p\u00ebrballur me nj\u00eb zgjedhje t\u00eb till\u00eb.
\n<\/a><\/noindex><\/p>\n

Detyra<\/h3>\n

\nN\u00eb kompani po zhvillohet aktivisht gjenerata e ardhshme e produktit \u2013 Docs Security Suite (DSS). Pjesa server nd\u00ebrt\u00e7ohet n\u00eb .Net Core, dhe si DBMS p\u00ebrdoret Entity Framework Core. Kur projektojm\u00eb aplikacionin, ne p\u00ebrdorim qasjen Code First.<\/p>\n

Modeli i domenit t\u00eb aplikacionit krijohet nga disa zhvillues n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb \u2013 secili p\u00ebrgjigjet p\u00ebr pjes\u00ebn e tij logjike t\u00eb sistemit. <\/p>\n

N\u00eb brezin e m\u00ebparsh\u00ebm t\u00eb DSS, sistemi i menaxhimit t\u00eb migrimeve p\u00ebrdorte klasiken Entity Framework Migrations (EF 6). Megjithat\u00eb, ndaj k\u00ebtij sistemi kishin shp\u00ebrthyer disa ankesat, m\u00eb e r\u00ebnd\u00ebsishmja prej t\u00eb cilave ishte se n\u00eb EF mungonte nj\u00eb qasje e arsyeshme p\u00ebr zgjidhjen e konflikteve t\u00eb versioneve. Ky fakt vazhdon t\u00eb na shqet\u00ebsoj\u00eb gjat\u00eb rregullimit t\u00eb defekteve n\u00eb kuad\u00ebr t\u00eb mb\u00ebshtetjes, prandaj u mor vendimi p\u00ebr t\u00eb shqyrtuar opsione alternative.<\/p>\n

Si rezultat i diskutimeve, u formuluan k\u00ebrkesa t\u00eb m\u00ebposhtme p\u00ebr sistemin e menaxhimit t\u00eb migrimeve:<\/p>\n

    \n
  1. Mb\u00ebshtetje p\u00ebr DBM t\u00eb ndryshme. Domosdoshm\u00ebrisht MS SQL Server, PostgreSQL, Oracle, por potencialisht mund t\u00eb p\u00ebrdoren edhe t\u00eb tjera.<\/li>\n
  2. Puna me ORM. Fillimisht ishte parashikuar p\u00ebrdorimi i EF Core, megjithat\u00eb n\u00eb faz\u00ebn e projektimit ishim t\u00eb gatsh\u00ebm t\u00eb shqyrtonim edhe ORM t\u00eb tjera.<\/li>\n
  3. Autogjenerimi i migrimeve. Duke marr\u00eb parasysh zhvillimin Code First, do t\u00eb donim t\u00eb evitonim nevoj\u00ebn p\u00ebr t\u00eb \"shkruar dorazi\" migrimet.<\/li>\n
  4. Konfliktet e versioneve. N\u00eb kushte zhvillimi t\u00eb shp\u00ebrndar\u00eb, gjat\u00eb bashkimit, EF Core mund t\u00eb has\u00eb konflikte. Kjo b\u00ebhet nj\u00eb problem i r\u00ebnd\u00ebsish\u00ebm, pasi pjes\u00eb t\u00eb ndryshme t\u00eb aplikacionit krijohen nga zhvillues t\u00eb ndrysh\u00ebm, prandaj duhet t\u00eb kalojm\u00eb shum\u00eb koh\u00eb p\u00ebr \u00e7do konflikt.<\/li>\n
  5. Dokumentacion i avancuar dhe mb\u00ebshtetje. K\u00ebtu, mendojm\u00eb se shpjegimet nuk jan\u00eb t\u00eb nevojshme.<\/li>\n
  6. P\u00ebrfitimi nga falas. Kriteri \u00ebsht\u00eb i kushtuesh\u00ebm, pasi sistemet jo shum\u00eb t\u00eb shtrenjta apo shum\u00eb t\u00eb shtrenjta, por ideale n\u00eb leht\u00ebsin\u00eb e p\u00ebrdorimit, jemi gjithashtu t\u00eb gatsh\u00ebm t'i shqyrtojm\u00eb.<\/li>\n<\/ol>\n

    \nSi rezultat i nj\u00eb hulumtimi t\u00eb vog\u00ebl, u gjend\u00ebn dhe u njoh\u00ebn si t\u00eb d\u00ebshiruara p\u00ebr shqyrtim k\u00ebto mund\u00ebsi:<\/p>\n

      \n
    1. Efekti i Transferimeve EF Core<\/li>\n
    2. DBup<\/li>\n
    3. RoundhousE<\/li>\n
    4. ThinkingHome.Migrator<\/li>\n
    5. Fluent Migrator <\/li>\n<\/ol>\n

      <\/p>\n

      Tani pak m\u00eb n\u00eb detaje<\/h3>\n

      \n\"Krahasimi
      \n      Transferimet e EntityFramework Core<\/a><\/noindex><\/b><\/p>\n

      Natyrisht, kjo ishte zgjedhja e par\u00eb dhe kryesore. Nj\u00eb mjet natyror q\u00eb funksionon nga kutia pa asnj\u00eb komplikim. Nj\u00eb sasi e madhe dokumentacioni, zyrtar dhe jo aq zyrtar, thjesht\u00ebsia etj. Sidoqoft\u00eb, ankesat q\u00eb jan\u00eb ngritur p\u00ebr EF klasik jan\u00eb gjithashtu aktuale p\u00ebr EF Core. <\/p>\n

      Pra, p\u00ebr EF Core jan\u00eb identifikuar avantazhet:<\/p>\n