Give the new batch of static app CLIs a chance before making them Rails engines
If you find me out in the wild and talk to me about what I'm excited about, topic #1 is most likely going to be how much Ember-CLI rocks. Here's a rough list as to why:
- Fully decoupled front-end and back-end code. Ember deploys down to four static files that rely on external JSON apis to do rich data access. We can think of front-end . . .
duplicating the interoperability that SOA has on our backend
Roughly three years ago at Iora Health I began pitching the engineering group on splitting our monolithic application infrastructure down into a SOA platform. There's a lot of data and problem domain in your medical record. It's not uncommon for startups to be focusing one of the areas of the domain we function in (biometric markers, . . .