Loading...

What is Java I/O and what are streams? | Interview Question | TechyTalkWithDev

Core Java Interview Questions

253 Questions

What is Java I/O and what are streams?

What is the difference between byte streams and character streams in Java?

What is the difference between InputStream/OutputStream and Reader/Writer?

What is BufferedReader/BufferedWriter and why is buffering important?

What is serialization in Java?

What is the Serializable interface and what does serialVersionUID do?

What does the transient keyword do in Java?

What is the difference between Serializable and Externalizable?

What are the security risks of Java deserialization?

What is the Java NIO (New I/O) package and how does it differ from classic I/O?

What is the difference between FileInputStream and FileReader?

What is the Scanner class used for in Java?

What is the difference between PrintWriter and BufferedWriter?

What is the difference between shallow copy and deep copy of an object?

What are the common approaches to reading and writing files in Java?

What is the difference between a Path and a File in Java?

How do you copy a file in Java using NIO?

Interview questions

Question 190 of 253

Free

What is Java I/O and what are streams?

I/O & Serialization

Java I/O (java.io) provides classes for reading and writing data — files, network connections, in-memory buffers — through the abstraction of streams: a sequential flow of data from a source (InputStream/Reader) or to a destination (OutputStream/Writer).

Beginner3 min

TCS

Infosys

Wipro

Capgemini

Accenture

#Java I/O#Streams

What is Java I/O and what are streams?

The Stream Abstraction's Real Value

The same InputStream/OutputStream contract works identically whether the underlying source is a file, a network socket, or an in-memory byte array — code written against the abstract stream types doesn't need to know or care which, which is why so much of the java.io API is built around wrapping and chaining these general-purpose abstractions.

Source (file/socket/buffer) → stream abstraction → destination — same contract regardless of source

Source (file/socket/buffer) → stream abstraction → destination — same contract regardless of source