Zum Inhalt springen
SAP, DATEV and Dynamics experts

Blog — Page 2

ERP Migration: Legacy to APILegacy State (Before)CSV ExportDirect DB AccessFTP UploadBatch ScriptsManual, error-prone, not scalableModern State (After)REST APIEvent WebhooksMessage QueueMiddlewareAutomated, robust, scalableStrangler Fig Pattern: Gradual MigrationPhase 1: Master DataPhase 2: InventoryPhase 3: OrdersPhase 4: PricingParallel OperationOld and new active simultaneouslyComparison TestsVerify old vs. new resultsRollback OptionSwitch back to legacy anytimeRisk minimization through gradual replacement | No big bang | Each phase individually testable
Integration May 10, 2026

ERP Migration: From Legacy Interfaces to Modern API Connections

ERP migration from legacy interfaces to modern API connections: strangler fig pattern, risk analysis and gradual replacement of old integrations.

14 min read Read →
Customer-Specific Price SynchronizationERP Price Lists10 Price Lists, TiersFramework Agreements, SpecialsMiddlewarePrice MappingCaching LayerNet to Gross + TaxB2B StoreCustomer Group PricesPrice Rules, Tiered PricingPrice StructuresList PricesStandard price for allGroup PricesPer customer groupTiered PricesQuantity-dependentSpecial PricesTime-limitedCaching ArchitectureRedis CacheTTL per Price TypeCache InvalidationFallback StrategySync StrategiesFull sync: All prices periodicallyDelta sync: Only changesOn-demand: At customer loginHybrid: Combination by price typePerformance Metrics500,000 price recordsunder 50ms query time95% cache hit rateDelta sync every 15 minutes
Integration May 7, 2026

Customer-Specific Prices from ERP: Synchronization and Caching

Customer-specific prices from SAP or Dynamics in B2B stores: synchronization strategies, caching architectures and tiered price mapping.

10 min read Read →
Error Handling in InterfacesStoreOrders, DataMiddleware: Error HandlingRetry, Queue, Circuit Breaker, LoggingERP / DATEVTarget SystemError Handling Pipeline1. ValidationCheck required fieldsValidate data typesCheck references2. Retry LogicExponential BackoffMax 5 attempts1s, 4s, 16s, 64s, 256s3. Circuit BreakerSystem protectionClosed / Open / Half-OpenAuto recovery4. Dead Letter QueueNot processableSafely storedManual clarificationMonitoring and AlertingTrack error rateMonitor queue depthMeasure latencyConfigure alertsIdempotencyEvery message can be processed multiple timeswithout undesired side effectsCorrelation IDsEnd-to-end traceabilityfrom store to ERP across all stations
Integration May 4, 2026

Error Handling in Interfaces: Retry, DLQ and Monitoring

Error handling in store interfaces: retry logic with exponential backoff, dead letter queues, circuit breaker and proactive monitoring.

11 min read Read →