# Reusable Applications - Architecture Question

**URL:** <https://www.ruby-forum.com/t/reusable-applications-architecture-question/189332>\
**Category:** Ruby\
**Created:** [May 28, 2010, 9:21pm UTC](https://www.ruby-forum.com/t/reusable-applications-architecture-question/189332 "2010-05-28T21:21:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![di3go](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@di3go](https://www.ruby-forum.com/u/di3go)\
**Post date:** [May 28, 2010, 9:21pm UTC](https://www.ruby-forum.com/t/reusable-applications-architecture-question/189332/1 "2010-05-28T21:21:30Z")

</div>

Some times i ask my self about reusable applications, ive build several  
rails/.net applications where it need a ticket system, forum and wiki.

All the time i copy and paste the code.

Now we have the Rails 3 with Pluggable Applications (well i could use  
Rails Engines later, but… nevermind 😛 ).

Most of the aplications i develop stay in my server, i take care if the  
app is running or not, if is slow, if needs update and so.

What its a better idea in your opnion, make plugins/pluggable  
applications or stick to something like SOA/Google services.

Every application in Google have a web api, this can be done to my  
applications too, api to blog, forum, tickets…