Since the requirement is a near instantaneous and fully automatic synchronization of multiple tables with a chance of "catching up" if the connection is temporarily broken, satya's suggestion is probably the best suggestion for this task.
The real question is, however, is there really a requirement for "near instantaneous"? Transactional replication has it's own set of headaches and can interfere with the truncation of logs during backups if there is a break or other problem with the connection between the two boxes for any reason.
If "near instantaneous" is not negotiable, then, yes, use transactional replication even with some of the pain it causes. If something like "once per hour" is good enough, then do something across a linked server or with OPENROWSET as previously suggested.
Service Broker could work and without the problems associated with the log file if the connection is broken but it has it's own set of headaches both for setup and when the connection breaks.
IMHO, there's no way in hell that I'd use SSIS for this.