Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Design and Architecture
  4. Distributed transactions within a microservices architecture

Distributed transactions within a microservices architecture

Scheduled Pinned Locked Moved Design and Architecture
databaseoracledotnetjsonhelp
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    Pelle30
    wrote on last edited by
    #1

    Hello, In my company we had a system on .net framework platform. That was made from an orchestator, different rest API services on top of a monolithic oracle DB. With a huge plsql library. We used distributed transaction for the operation (import of data). Because of the rollback possibilities if one request did fail e.t.c. And used a orchestrator in front of the rest API services (micro services) that organized the different requests all in one transaction. We had to upgrade the system to .net core. But .net core don't support DTC anymore ! Have anyone had a similar situation, and what what did you do about it? Or do anyone have any comments to this issue/problem.? That if one request fails in a big operation of many requests the database data will not be consistent, if no rollback is done. When we use many "micro"services on top of one monolithic database. BR

    L 1 Reply Last reply
    0
    • P Pelle30

      Hello, In my company we had a system on .net framework platform. That was made from an orchestator, different rest API services on top of a monolithic oracle DB. With a huge plsql library. We used distributed transaction for the operation (import of data). Because of the rollback possibilities if one request did fail e.t.c. And used a orchestrator in front of the rest API services (micro services) that organized the different requests all in one transaction. We had to upgrade the system to .net core. But .net core don't support DTC anymore ! Have anyone had a similar situation, and what what did you do about it? Or do anyone have any comments to this issue/problem.? That if one request fails in a big operation of many requests the database data will not be consistent, if no rollback is done. When we use many "micro"services on top of one monolithic database. BR

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      I think a DTC implies "multiple" "micro services". A transaction that spans multiple databases is not what I would can micro.

      It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups