Caching is something we use to reduce the access to the original source. To do that, we store the data temporarily on another medium. We can use various tech to achieve that, but whatever we choose should be faster or lighter than the original source. This will help our users to retrieve our data faster than before. It will also help lower the initial resource utilization. Depending on what we choose, we can save some costs.

Although we use monolithic architecture, we actually “break down” the application into several parts in production, such as:

• Web
• Free API
• Paid API
• Mobile API

Workers (background jobs)

Therefore, when we deploy, it does not mean that all servers will receive the new application. If we deploy to the Web and there are issues, only the Web will be affected. However, some applications may still have problems if they manipulate shared data until it becomes corrupted.

These days we might have multiple local applications that are running on different ports (e.g: http://localhost:3000, http://localhost:3001 and so on). This is pretty troublesome as we have to remember which application is running on which port.

On the 5th of July 2011, Hospital Universiti Sains Malaysia (HUSM) has been chosen as one of the speakers in Malaysia Open Source Conference 2011. It was presented by Mr Yusdirman Bin Yusoff as “Open Source in Health Care: HUSM 10 Years of Innovation”.

Basically it’s about what and how HUSM as one among few hospitals in Malaysia managed to develop its own Total Hospital Information System thus saved millions ringgit of taxpayers money. This is actually the first step for us (IT Unit, HUSM) to show to the world what we have done in this 10 years where most hospitals not willing to do.

The slide can be accessed at https://speakerdeck.com/amree/open-source-in-healthcare-husm-10-years-of-innovative-effort