Isuru Madusanka

Isuru Madusanka

Creative, resourceful and flexible, able to adapt to changing priorities and maintain a positive attitude and strong work ethic.


E-mail: nkimadusankaucsc@gmail.com | phone: +94770190519 | Course: CS

Creative, resourceful and flexible, able to adapt to changing priorities and maintain a positive attitude and strong work ethic.

Interests: UNIX-like OS’s,Virtualization, Mobile Application, SPA, IOT

Technical Skills: Java, C/C++, HTML5/CSS3, PHP, SQL, JS, Angular JS, Android, Docker, LXC, GIT, Web Services

Project Experience

iTranfussion.lk
Web, mobile and chrome extension based project to manage blood donation events and donors in Sri Lanka.

Conditional Compilation Validator
Detect invalid API calls in conditional compilation blocks of PLSQL IFS oracle server.

EMIS
Educational institute management software. {Technologies: JavaRMI, MySql, Java Persistence}

Work Experience

NIBM software development team: Developing Student Management System of NIBM by using JAVAEE
IFS R&D International (Pvt) Ltd: Build QA tools and supported to automate bug reporting.

Achievements | Awards

• 2012: 1st place Software Development Competition at NIBM is organized by the UCDAASL
• 2015: 1st place iHack 1.0 24 hour software development competition organized by the UCSC – ISACA.
• 2015: Participate to IOT Hackathon organized by Google IO 2015 extended Sri Lanka

Final Year Project

Process Virtualization uses Hybrid approach by combining Hypervisor and Container Virtualizations.

In these days, Virtualization becomes popular and major technology use in Cloud computing, and likewise it is the buzzword in Developers, DevOps communities and Research communities. We can categorize Virtualization to mainly two different methods, which are Hypervisor based virtualization and operating system virtualization (container virtualization). But recent year’s container based virtualization have gained substantial popularity among developer and researchers more than Hypervisor based virtualizations. Because container based ones are portable, low boot time, version support, dependencies handling etc. But hypervisor based virtualization still can give benefit such as providing hardware virtualization, host operating system independent, process isolation among virtual systems and etc, Which are not provided and support in the container based. Question is can we introduce a better hybrid approach (hypervisor based + container based) have almost all advantages of these two different methods.

View complete CV