Richard Searle's Blog

Thoughts about software

heroku and intellectual property exposure

Posted by eggsearle on October 9, 2011

The implementation is ingenious and very easy to use. Pushing from a GIT is both elegant and effective.

However, this exposes the entire code base to Heroku.
That is troublesome for anything but an OSS application.

Heroku started as a Rails platform where there is no alternative to deploying the source code.  That is not true for Java or Scala.

Obviously this disadvantage does not greatly impact the business model of Heroku or their competitors. Presumably their customer base is not overly concerned with IP protection


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: