4 ms·
The author mentions service-oriented designs as means to improving iteration time. However, it's also a great way to enable parallel development and incremental
by snprbob86 16y ago
The author mentions service-oriented designs as means to improving iteration time. However, it's also a great way to enable parallel development and incremental rollout, as well as reduce code complexity. I'd really like to see more work go into making services more easily. Right now, it's simply too difficult to set up new services. Each one needs it's own version control, staging/production servers, etc. etc. I'd love to see something to help spin up everything you'd need for a new service instantly.
- aaronblohowiak 16y agoGoing from monolithic app to SOA does introduce some complexity: Services complicate the debugging process. Also, parallel development means more co-ordination overhead. Deployments become a little trickier -- with a monolithic app, you can easily roll out one version while the other version is removed from the load balancers. With services, you start getting into supporting different versions of services (through forwards or backwards compatibility) or requiring downtime.
- gnufied 16y agoNot to mention test driving a SOA app is much harder than writing a monolithic Rails app.