All good points Amir, and sure I think more like a DBA, but some of my requirements cannot be fulfilled with the service as it presently is configured to work.
At the moment, the way an Archive behaves limits me to a calendar representation of our data. Which I am sure for many people is fine. However, many changes to the land record, do not necessarily fall within the calendar year in which an edit could be reasonably applied.
Further complicating that point, a lot of our data requirements have me posting 'stale' data for the public at large to consume for not just the current version, but past versions as well. Legally, certain changes to the property record can go back as far as 5 years, and in some limited scenarios, they can go back 10.
Creating a View of those transactions outside a calendar, allows us to preserve the data for a tax year in which something was applied. We may have to change parcels in place in the Fabric, that had a change filed lets say today, but was effective for 2 years ago. While the service can easily show this change today, it is not great at having to present data that was for 2 years ago, and still show how that changed progressed to today, something I know that I have spoken with both you and @DanielStone about at length.
Were I just showing people today information, I would not hesitate to just putting out a simple service as opposed to ETL, wouldn't argue that point at all, and if my reality was that simple, well, I wouldn't be talking about it here.