What Java 8 Brings and Why Full‑Stack Engineers Favor NoSQL Over RDBMS

Interview Overview

The interview is part of a series featuring a full‑stack engineer who discusses his background, technical insights, and industry opinions.

Career Background

The guest, known as "jieforest," graduated in 1998 with an engineering degree, started in circuit design, switched to Java programming after three years, earned a master's in computer science, and now works as a project manager and chief system architect, leading outsourcing projects and mentoring newcomers.

Java 8 New Features

He highlights several Java 8 innovations that developers should adopt:

Lambda expressions – anonymous functions that simplify code. Syntax: parameters -> body. Example in Swing:

button.addActionListener(e -> {
    System.out.println("ActionDetected");
});

Compared with the pre‑Java 8 style using an anonymous inner class.

JavaFX enhancements – new Modena theme, richer HTML5 support in WebView, and ARM platform support.

New tools – jjs (Nashorn engine), jdeps (class dependency analysis), enhanced jmx remote diagnostics, and additional options for javac and javadoc.

Nashorn JavaScript engine – replaces the older Rhino engine.

Advice for Programmers

He stresses reading many books and writing code frequently. Practical experience accelerates learning, while reading alone can lead to “paper knowledge” without real skill.

NoSQL vs. Relational Databases

He argues that NoSQL emerged to meet high‑concurrency, high‑read/write, weak‑consistency, and flexible schema needs of modern internet applications, which traditional RDBMS struggle with due to heavyweight features.

RDBMS are mature and feature‑rich (security, transactions, views, backup, etc.), but many of these capabilities are unnecessary for many web services.

NoSQL and RDBMS are complementary; neither can fully replace the other. For example, MongoDB fits scenarios where MySQL’s transaction load is low and a flexible schema is beneficial.

MongoDB Highlights

Simple distributed and clustering setup, providing high availability.

High read/write performance suitable for massive internet traffic.

Ease of use reduces the need for dedicated DBAs.

Schema‑free design while still allowing relational‑like modeling.

Programmer vs. DBA Outlook

He notes that the “full‑stack” label reflects engineers who can handle many layers of a system, similar to building a ten‑story house alone versus collaborating on a skyscraper. While Oracle DBAs may earn higher salaries, long‑term success depends on becoming an expert in a chosen domain.