Facebooktwittergoogle_plusredditpinterestlinkedin

Hi Everyone,

Here is a common question: “Can iDempiere run on a micro AWS instance?” Answer: yes.

Another question: “How many iDempiere users can you support using the micro AWS instance?” Answer: between 1 and 3 concurrent users (more if you get creative – read the directions at the bottom of this post).

Introduction: The purpose of this post is to help you get iDempiere up and running as inexpensively and easily as possible. Evaluating ERP is one of the most challenging tasks you will undertake. This post helps make your job a little easier. Please be sure to let me know if I missed any details relating to this topic!!

Performance: Here is what htop looks like after (a) running for just under a week and (b) two users pounding on the box for an hour. Here are the specs for an AWS micro instance.

htop for idempiere - memory usage on aws micro instance

Here are my thoughts and recommendations for getting iDempiere up and running on a micro instance:

  1. Here is how to quickly install iDemipere on AWS Ubuntu Linux.
  2. The above server is running both the application server (app server) and the PostgreSQL DB. It depends on no other servers.
  3. I did not optimize the PostgreSQL database for this size server. It remains as it was installed using apt-get. You can improve resource management by optimizing the DB for the server specifics.
  4. Most companies will not run iDempiere on a micro instance for production; however it is nice to know that you can test iDempiere for almost no money. And, you get all the benefits of the AWS infrastructure and tools for backup and high availability.

AWS Micro financials: You total per user cost is $7 per month ($728 from below /36mo/3users). Please keep in mind that I doubled the below costs to ensure this number errors on the high side. Here are the cost details:

  1. Your three-year cost of running iDempiere on a micro instance using the heavy usage pricing model is $240 ($100+$0.005*24*7*52*3).
  2. Let’s assume you keep 4GB worth of backups on AWS S3 at cost of $0.02 per GB-month. This yields a total 3-yr cost of about $4 (4*$0.02*36).
  3. Let’s assume you maintain 24GB worth of EBS storage at $0.10 per GB-month. This yields a total 3-yr cost of about $90 (24*$0.10*36)
  4. Let’s assume you have about about $30 in network and disk IO related charges over the three years.
  5. NOW, let’s assume that I am wrong in every category, and we double to costs to ensure the cost numbers error on the high side.
  6. Your total three year cost = $728 (($240+$4+$90+$30)*2)

The Next Step: If you exceed the abilities of a single micro instance, you can split the AppServer and database between two micro instances. Two micros cost less than a single AWS Small, and micros have more CPU power. If two micro instances are not enough, you can scale (change the instance types of) either the app server or the database server independently to match your exact requirements without modifying the configuration of iDempiere. In an extreme case, I have seen a production system with a single DB server and single app server support 300+ concurrent users.

Here are the steps to bring up a separate app server. Bringing up a new app server is far easier than migrating to a new DB.

  1. Make sure your AWS security group allows servers to communicate with other servers in the same security group.
  2. If you are already using iDempiere in production,
    1. make a backup of your database, and store the backup in a safe place.
    2. make an ami backup of your whole server. The process is easy and inexpensive – why not??
  3. Update the database to allow external communications.
  4. Bring up a new app server server using the same directions as before; however, skip the DB section.
  5. Run server setup.sh or console-setup.sh on your new app server and point the app server to your existing DB server.

The Next Next Step: If you exceed the abilities of a AWS Large app server + AWS Large DB server, you should consider splitting the app server into two servers: (a) the WebUI server and (b) the services server. Once the WebUI server exists by itself, you can use an AWS load balancer, AWS CloudWatch and AWS Auto-Scaling features to bring up as many WebUI servers as is needed to support the load during any given hour of the day.

iDempiere for Hunderds of Users: If you would like to know more about hosting and scaling iDempiere up through 500 concurrent users, let me know. The cost per user remains fairly constant as you grow the application using standard AWS EC2 and CloudWatch tools.  The iDempiere code base has been used to support some large ($400M+ USD revenue) multinational companies around the world.

I hope this helps!!!

ADempiere vs iDempiere vs Openbravo vs Compiere

Please note that ADempiere, iDempiere and Openbravo are forks or copies from Compiere. Therefore, they have similar abilities mentioned above. The biggest difference is that ADempiere and iDempiere are pure open source. There are no features held behind a commercial or paid license.

About Chuck Boecking: I am an ERP educator. I believe that open source ERP have achieved mainstream capabilities, and as a result, more companies can create greater efficiency across their organization. I started using the iDempiere code base in 2003. Back then, it was called Compiere. In 2006, I started my first multi-million dollar installation. Since then, ADempiere has helped me create great success with distribution and manufacturing companies all over the world. My vision of success is to find companies that can best use open source ERP to help them achieve a single, global instance that drives a discontinuous increase in profitability. I believe that organizations win when they own their technology.

If you have questions, comments or concerns, let me know. I definitely want your feedback.

You can contact me by phone using 512.850.6068.

My email is chuck@chuboe.com.

You can complete the form on this page.

Thank you for taking the time. I look forward to speaking with you.

Regards,
Chuck Boecking
http://www.linkedin.com/pub/chuck-boecking/10/970/17b

 

Facebooktwittergoogle_plusredditpinterestlinkedin

Leave a Reply

Your email address will not be published. Required fields are marked *