Key Takeaways from 2024

Learn how AI is transforming document processing and delivering near-instant ROI to enterprises across various sectors.

Blogs

Home / Blogs / Astera Centerprise 8.3: Improved UI, Better Performance, Extended Connectivity

Table of Content
The Automated, No-Code Data Stack

Learn how Astera Data Stack can simplify and streamline your enterprise’s data management.

    Astera Centerprise 8.3: Improved UI, Better Performance, Extended Connectivity

    February 6th, 2024

    Packed with six in-demand database connectors and significant UI and performance improvements, Astera Centerprise 8.3 is better than ever!

    The latest Astera Centerprise 8.3 is out and available for download. This release of Astera Centerprise has been aimed at resolving longstanding bugs, improving the visual interface and client-server communication, as well as extending the native connectivity to include new, in-demand databases and enterprise applications.

    Here’s a round-up of all that has been added, improved, and fixed in Astera Centerprise 8.3.

    UI/UX Improvements

    One of the top targets for us for this release was to resolve the pending UI issues and give a polished look and feel to the product. This has been achieved by giving a fresh identity to some features with new icons relevant to the functionality and the overall visual theme of the product. We have also implemented async client-server calls for client actions that do not essentially require a response from the server. This has brought about a notable improvement in the overall client response as well as the design time in Astera Centerprise 8.3.

    New Options

    In addition to visual and performance enhancements, we have introduced some new options in the following areas:

    • Server Explorer: A ‘Delete Stale Jobs’ option has been introduced in the server context menu. This option is a single-click way to delete stale jobs deployed on the server.
    server explorer improvements

    Figure 1: Delete Stale Jobs from Server Explorer

    • Job Progress: The Job Progress window now shows information such as job duration and the real-time status of the job. The load time as well as navigation for long trace outputs have also been improved.
    job progress improvements

    Figure 2: Job Progress Improvements

    • Job Monitor and Server Log: A ‘Pause/Resume Auto-Refresh’ button has been added in the Server Log and Job Monitor window with improved navigation.
    server log improvements

    Figure 3: Pause/Resume Auto-Refresh in Server Log

     

    Extended Connectivity to New Databases and Applications

    We have extended our out-of-the-box connectivity to include six new connectors to in-demand databases and applications.

    • Salesforce SOAP (Legacy)
    • Vertica
    • Amazon Aurora MySQL (Beta)
    • Amazon Aurora PostgreSQL (Beta)
    • Amazon Redshift (Beta)
    • Snowflake (Beta)
    new database connectors

    Figure 4: In-Built Connectors for New Databases and Applications

    Users will now be able to connect to these databases and applications to read or write data, at source and destination. The connectivity also extends to other functionalities such as Database Lookups, SQL Scripts, SQL Statement Lookup, and Database Write Strategies.

     

    Server and Repository Improvements

    • Optimized Job Concurrency

    We have modified the code to optimize job concurrency on the server. The server now counts only active running jobs (either parent or child nodes) against its limit for concurrent jobs. For instance, for a complex, nested flow, the server will count only leaf/child nodes and exclude idle parent nodes while calculating jobs for concurrent execution. This will also improve the performance of the repository with improved indexing and reduced database contention.

    • Purge

    The server repository records information about the server’s activity, such as jobs running, scheduled or queued for run, job trace, and server events information. Purging the repository periodically ensures that there’s no unnecessary load of old and outdated records on the repository. The Purge function for server repository has been improved in Centerprise 8.3, with options to set a frequency and time range, and customize timeout settings and chunk sizes, to help optimize purging in high-load environments.

    Figure 5: Purge Frequency Settings

     

    Ready to test-drive Astera Centerprise 8.3? Download a free trial and streamline your data integration processes with our end-to-end solution.

    For more information on Astera Centerprise 8.3, visit our documentation site or contact [email protected].

     

    Authors:

    • Fiza Baig
    You MAY ALSO LIKE
    Why Your Organization Should Use AI to Improve Data Quality
    Data Mesh vs. Data Fabric: How to Choose the Right Data Strategy for Your Organization
    A Comprehensive Guide to Workflow Automation
    Considering Astera For Your Data Management Needs?

    Establish code-free connectivity with your enterprise applications, databases, and cloud applications to integrate all your data.

    Let’s Connect Now!
    lets-connect