Amazon Aurora is a MySQL and PostgreSQL compatible relational database built for the cloud that combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases.
Aurora is up to five times faster than standard MySQL databases and three times faster than standard PostgreSQL databases. It provides the security, availability, and reliability of commercial-grade databases at 1/10th the cost. Aurora is fully managed by Amazon Relational Database Service (RDS), which automates time-consuming administration tasks like hardware provisioning, database setup, patching, and backups.
Aurora features a distributed, fault-tolerant, self-healing storage system that auto-scales up to 64TB per database instance. Aurora delivers high performance and availability with up to 15 low-latency read replicas, point-in-time recovery, continuous backup to Amazon S3, and replication across three Availability Zones.
Our Amazon Aurora Connector honors the security of source databases and provides both full and incremental crawls so that users have the latest information available to them at all times. It indexes content from Amazon Aurora into Azure, SharePoint Online or SharePoint 2016/2013, surfacing it through BA Insight’s SmartHub to provide users with integrated search results.
Our Amazon Aurora Connector is built upon industry standard database access methods, so it equally supports databases from other systems such as Oracle, MySQL, and IBM DB2
Our Amazon Aurora connector is standard, off the shelf software that addresses the following requirements:
Works with all types of data.
Works with custom tables, documents, attachments, and BLOB data.
Indexes every desired item with a very high throughput. Many SQL databases have millions of rows, making high throughput critical to the success of the implementation.
Minimizes the impact on the source system through views or stored procedures as necessary, ensuring no impact to its performance.
Only surfaces the content that users are permitted to see, even if the security configuration is custom designed.
The source system retains the master information and the search index has only a representation (pointers). If applicable to the database being crawled, users click on a search result and are taken to their original item or document.