New Software ArchitectureTo be implemented on ICT Application Service 2015

Herman Wahyudi, T&D @ ICT Application Service

Where we’ve been

Web based programming “The Servlet Way” JSP or HTML Form Submit to servlet Servlet

Processes data & Outputs information Perencanaan untuk aplikasi kecil namun tumbuh

diluar kendali karena HTML, scrip-lets, java script, tag-libraries, database access, dan business logic sulit untuk dikendalikan

JSP’s compile to Servlet

Current JSP Architecture

Why need to changes ?

Sulit dipahami Tidak bisa mengguankan library pihak ketiga Menyianyiakan dukungan tipe data yang sudah disediakan Java Code asynchron antar developer To many manual process (sync folder, develop not using IDE,

reload/restart tomcat) Tidak ada unit testing (tidak dimungkinkan testing untuk JSP) Tidak ada logging

A Better Way ?

Separate the Data Access, Business Logic and Presentation using a M.V.C.

Framework

MVC Architecture

Kriteria Pemilihan Teknologi

Benar Mudah dipahami

Kualifikasi tim lebih rendah lebih mudah cari orang Bootstrap tim lebih cepat cukup training sebentar

Sedikit coding Time to market lebih cepat Less code = less bug Less code = less maintenance

Mudah dikembangkan (templatting base)

Kriteria Pemilihan Teknologi (Lanj..)

Mudah dideploy Rentang waktu source to live

Mudah dioperasikan Spec hardware minim System service dependency minim

Ringan maintenance Backward compatibility

All Architecture

Development Workflow• Issue Creation• Local deployment• Sync Code• Less code• Templatting base

• Unit Test• Black Box• Easy tracing• Responsive

capability

• Deploy to Development

• Easy and safe deploy

• Deploy to Production

Development Testing

UATGo Live

• IDE Java• Structure Management

• Tomcat Server

• Unit Testing• Maven Test

• Git• Maven• Tomcat

Integration

Eclipse Integration

ECLIPSE

Development Integration