SQL Server Stretch database, and archiving table to SQL Azure SQL Server 2016 Standard Edition

We have a generic need: A large, growing table.

For performance reasons, we want to move obsolete/old data out to an archive table.

SQL Azure would be the perfect home.

The question is:  Should we use a table in a "stretch" db (new in SQL 2016), or should we simply manage this in application code?
Stretch table could be good fit for your need. However i suggest to check the current limitations of enabling stretch feature. 

https://msdn.microsoft.com/en-us/library/mt605114.aspx

The other manual way of doing this is partitioning the table and switching out to another table in the same DB.