Please turn JavaScript on
Software AG Adabas & Natural Tech Community & Forums - Latest posts icon

Software AG Adabas & Natural Tech Community & Forums - Latest posts

Subscribe to Software AG Adabas & Natural Tech Community & Forums - Latest posts’s news feed.

Click on “Follow” and decide if you want to get news from Software AG Adabas & Natural Tech Community & Forums - Latest posts via RSS, as email newsletter, via mobile or on your personal news page.

Subscription to Software AG Adabas & Natural Tech Community & Forums - Latest posts comes without risk as you can unsubscribe instantly at any time.

You can also filter the feed to your needs via topics and keywords so that you only receive the news from Software AG Adabas & Natural Tech Community & Forums - Latest posts which you are really interested in. Click on the blue “Filter” button below to get started.

Website title: Software AG Adabas & Natural Tech Community & Forums - Adabas & Natural forums, tutorials and experts

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.9 / day

Message History

I’d lean gradual for systems that are still business-critical: use the strangler pattern, put an API/anti-corruption layer in front of legacy functions, and migrate one bounded capability at a time. Avoid dual writes where possible; prefer change data capture or a single system of record with reconciliation jobs, and define consistency expectations per use case. For Adabas/Na...


Read full story
Hi everyone,

Many organizations still rely on legacy enterprise applications because they have been running reliably for years and support important business operations. However, as technology evolves, integrating these systems with modern platforms, cloud env...


Read full story

Thanks for sharing these practical insights. I agree that measuring performance before making changes is essential, especially when working with long-running enterprise applications where the root cause isn’t always obvious.

The point about separating application CPU, database wait, and I/O is particularly useful because it helps narrow down where optimization efforts ...


Read full story

One suggestion on the sidebar: persist each user’s collapsed/expanded state and their edited category/tag selection across sessions, rather than resetting it. It would also help if the popular tags shown reflected what that person actually browses, not just global popularity. On topic cards, showing the reaction count next to replies and likes would make it easier to judge wh...


Read full story

Start by measuring before changing. Capture end-to-end timings and split them into application CPU, database wait, and I/O. For Natural/Adabas, time critical subprograms and review Adabas command-log and buffer-pool statistics; look for high read counts, excessive sequential reads, poor descriptor use, and many small calls. Batch database calls and fetch only needed fields. T...


Read full story