The FASTEST new Smart Safe is almost here!

Technical Information For IT
In SQL Server replication, communication between the publisher (source) and subscriber (replicated Database) is managed through a series of agents and jobs.
Here’s a high-level breakdown:
-
Log Reader Agent (for transactional replication) monitors the transaction log of the publisher database for changes.
-
When a new transaction occurs, the Log Reader picks it up and moves it to the distribution database.
-
The Distribution Agent then takes those changes and applies them to the subscriber database.
This process ensures data consistency by:
-
Reading committed transactions (not ongoing ones).
-
Using SQL Server Agent jobs to schedule and automate the communication.
-
Sending data over the network (usually over TCP/IP via port 1433) from the distributor to the subscriber.
The replicated data is applied in the exact order it was committed, preserving data integrity and synchronization between systems.
Option 1: Cloud-Hosted Website with Secure API Communication (Recommended)
-
How it Works:
The website is hosted in the cloud (e.g., at oursite.customer.com) and communicates via HTTPS with your on-prem IIS-hosted API (api.customersite.com). -
What’s Required:
-
You provide a secure subdomain (e.g., api.customersite.com)
-
We generate and provide a .pfx SSL certificate for secure communication.
-
Your IIS server hosts the API with inbound access for our cloud service.
-
Outbound communication from your network to our server is also needed for responses or validations.
-
-
Benefits:
-
The website can be accessed from anywhere (remote work).
-
Suitable for distributed teams or multiple site management.
-
Option 2: Fully Local-Hosted Website and API (No Outside Internet Communication)
-
How it Works:
If external communication (inbound/outbound) is not permitted, we can provide a locally hosted version of the website, identical in appearance and functionality to the cloud version. -
What’s Required:
-
Two subdomains hosted internally:
-
One for the website (e.g., localweb.cutomersite.com)
-
One for the API (e.g., localapi.customersite.com)
-
-
These must be hosted on machines within the same local network.
-
The customer installs the provided .pfx certificates for secure local communication.
-
-
Limitations:
-
The system can only be accessed within the local network.
-
Updates to the web application may need to be manually deployed onsite.
-
-
Benefits:
-
Ideal for organizations with strict IT or compliance policies.
-