Ta yaya za ka haɗa SaaS da tsohon ERP mai karɓar batch kawai?

Question

IT Interview Practice · Accepted Answer

Tsara **musayar asincrone da za a iya farfaɗowa** wadda ke mutunta iyakokin batch na ERP. Fara da yarda kan jinkirin kasuwanci da za a karɓa da tsarin da ya mallaki kowane nau'in bayanai; kada a yi alƙawarin kammala nan take bisa import da yake gudana sau ɗaya a awa.

## Architecture da mallaka

```text
[SaaS API/events] --> [Durable staging] --> [Mapping adapter]
                                               |
                                         [Batch files]
                                               |
                                         [ERP importer]
                                               |
[Status + reconciliation] <------------- [Result files]
```

A misalin haɗin tallace-tallace, SaaS ne ke mallakar buƙatar oda da aka aika, ERP kuma ke mallakar takardar kuɗin da aka yi posting. Haɗa lambobinsu a fili. Adapter yana fassara statuses, units da ma'anar fields domin ƙa'idojin ERP na musamman kada su yaɗu cikin workflow na SaaS.

## Sanya kowane mataki ya iya farfaɗowa

Adana aikin da ya shigo dindindin kafin sanar da karɓarsa idan protocol na tushen ya yarda. Idan polling ya zama dole, yi amfani da checkpoint mai ɗorewa da dokokin overlap ko replay da za su hana ɓacewar rikodin iyaka. Riƙe batch IDs, record IDs, schema versions, counts da checksums. Fitar da cikakkun fayiloli atomically inda ake tallafawa, ko amfani da alamar kammalawa daban.

Bi kowane rikodi cikin yanayin pending, submitted, accepted ko rejected. Nasarar tura fayil ba tana nufin an yi posting na bayanin kasuwanci ba. Karanta sakamakon ERP sannan daidaita lambobin kasuwanci da adadin kuɗi, ba yawan fayiloli kawai ba. Ware bayanan da ba su inganta ba tare da dalili da mai alhakin kula da su.

## Magance gazawar da ba a san sakamakonta ba

Idan ERP ya yi posting na batch amma sanarwar ta ɓace, sake aika ba tare da bincike ba na iya ninka takardun kasuwanci. Yi amfani da duplicate key da ERP ya tallafa ko query/reconciliation kafin retry. Idan ba a da kowannensu, dakatar da rikodin da ba a tabbatar ba domin daidaitawa da aka sarrafa; ledger a adapter kaɗai ba zai tabbatar da tasiri sau ɗaya tak a ERP ba.

## Ƙarfi da gudanarwa

Ƙiyasta ko import window guda zai iya gama tarin aikin baya, har da peak volume da farfaɗowa bayan katsewa. Yi amfani da backpressure sannan nuna wa masu amfani pending state da ainihin lokacin da ake tsammani. Yi gargaɗi kan shekarun aikin da ya fi daɗewa yana jira, rejection rate da bambance-bambancen reconciliation. Kare fayilolin staging kuma fayyace alhakin shiga da lokacin riƙe su.

## Alamar ƙwarewa a hira

Bayyana iyakar consistency da hanyar farfaɗowa. “Ƙara queue” bai warware map ɗin ma'ana, karɓar wani ɓangare ko ERP da ba ya iya deduplicate retries ba. Zane yana musanya saurin nan take da compatibility kuma dole ya nuna wannan jinkiri ga kasuwanci.

Madogara: [Microsoft: anti-corruption layer](https://learn.microsoft.com/en-us/azure/architecture/patterns/anti-corruption-layer).

Architecture da mallaka

Sanya kowane mataki ya iya farfaɗowa

Magance gazawar da ba a san sakamakonta ba

Ƙarfi da gudanarwa

Alamar ƙwarewa a hira

Tambayoyi masu alaƙa