API-centric cloud PaaS is concerned with cloud platform as a service delivery that provisions development and deployment tools specific to underlying cloud provider s infrastructure for developing cloud-aware applications. With the advent of API-centric cloud PaaS and the new approach to software development it poses, there still stands some uncertainties as to whether development processes for these platforms are same as traditional application development and deployment processes. The significance of this work is evaluating and establishing a comparison of the software development process between the API-centric cloud PaaS and traditional development platform following the MVC design pattern with comparison case studies as Google App Engine and Glassfish respectively. An experimental approach was adopted for this research, and empirical results show that traditional development platform may require more processes at selected development stages and consequently more flexibility,from an MVC perspective, compared to API-centric cloud PaaS development (depending on the nature of requirement or deterministic factors).