Ember & SOA
summary
A monolithic HDR photo app becomes CloudHdr split into 3 main service apps plus a collection of Ember frontends, implemented as Rails JSON APIs. Authentication uses OAuth flows: session‑based via server redirects with a jQuery withCredentials fix to send cookies, and a token flow prototyped but not yet deployed. Cross‑domain CORS is solved using the rack-cors gem. File uploads, single sign‑on, and small focused apps all function in production after those fixes.
AI-written summary · about
chapters (6)
- 0:00Ember and SOA intro
- 1:41Context goals and CloudHDR
- 4:10SOA with Ember first steps
- 6:17SOA auth with OAuth
- 15:27Deploying SOA beyond localhost
- 20:25Key takeaways
related talks
42mBuilding modular, scalable web apps? of CORS!
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
37mRails as an SOA Client
36mService Oriented Authenication
34mSOA and the Monolithic Rails App Anti-Pattern
40mFacing the Monolith Overcoming Monolithic Applications with SOA
43mRails services in the walled garden
37mArchitecture: The Next Generation
