Scala JVM par chalti hai aur us ke aagay aik mazboot type system rakhti hai, jis ka matlab hai ke ghaltiyon ki poori qismein compile ke waqt pakri jati hain, na ke jab customer istemaal kar raha ho. NUZM ise pecheeda qawaid wali back-end services ke liye istemaal karta hai, aur wahan jahan pehle se mojood Java system ke sath kaam karna ho, use badalna na ho.
Is mein kya shamil hai
- Domain ke qawaid types mein likhe jate hain, taake ghalat halat compile error bane, support ticket nahi.
- Aap ki mojooda Java libraries ke sath interoperation, jis se aam tor par rewrite ka jawaz khatam ho jata hai.
- Example tests ke sath property-based tests, jo wo inputs dhoond leti hain jo kisi ke zehan mein nahi aatay.
- Documented build, kyunke bina documentation wali JVM build usi hafte kaam chhor deti hai jis hafte use banane wala chala jata hai.
Kya ye aap ke liye theek hai?
Data se bhari back ends, financial aur qawaid par mabni logic, aur un teams ke liye theek jo pehle se JVM par lagi hui hain.
Aisi chhoti service ke liye ghalat jo Go ya PHP jaldi mukammal kar deti. Scala us codebase ko faida deti hai jo itna bara ho ke type system compile ke waqt ki qeemat chuka de, aur us se chhote ko nuqsan.
Commit karne se pehle janna zaroori
Scala par aam aitraz ye hai ke har team us ki alag boli likhti hai. Ye durust hai aur ye faisla project ka hai, zaban ka nahi. Hum tay karte hain ke codebase kaun sa subset istemaal karega aur use likh lete hain, taake agla developer aik hi style parhe, teen nahi.