In the wikipedia page for EEPROM: http://en.wikipedia.org/wiki/EEPROM it is given that "Parallel EEPROM devices typically have an 8-bit data bus and an address bus wide enough to cover the complete memory" and also "Operation of a parallel EEPROM is simple and fast when compared to serial EEPROM". In that case why are serial EEPROMs becoming more popular than the parallel EEPROM?
It is very simple. Number of pins and cost of packaging.
EEPROM devices are primarily used to store parametric data or characterization constants for a device. The typical scenario is to write very seldom and read typically once each time the host device boots up. For this type of application the relatively slow writing times of EEPROM are of little concern. And the reading time to load at most a few K-bytes of data from a serial device (SPI or I2C) is not normally an excessive time impact.
There is another factor that has played into the popularity of serial devices over parallel devices. That has been the migration of MCU devices from older microprocessor units with parallel busses to the much more prevalent modern types that have all their program storage memory and data memory built right on the chip. Often there is no longer a parallel bus option directly available. And in most applications there is very little interest in using up scads of pins to bit bang to a parallel peripheral.
In the early days, wires were cheap and transistors were expensive. These days it's the reverse. Hence why almost everything is done serially.
In the early days, chips weren't very sophisticated, and a CPU would power up and read the first thing it found on its memory bus at the starting address, so parallel EEPROMs effectively mimicked the DRAM that was hanging on the bus.
These days, DDR RAM is screaming away at gigahertz on huge wide buses, making a flash chip that could hang on the same bus would be prohibitively expensive and fairly pointless when modern CPUs have enough built-in intelligence (thanks to cheap small transistors) to boot from I²C/SPI flash.
With micros, these days the program flash and RAM is usually internal to the device. External storage like EEPROM can hang on an I²C bus, saving I/O pins for other functions whilst maintaining acceptable throughput. The fewer I/O pins you use, the smaller, cheaper and more energy efficient you get. Plus it's far easier to track two wires around a board than two 8/16/32-bit wide buses, with the associated EMC issues, etc., etc.
Don't forget there is a "half-way house" called SQI. That is a multiple parallel bit serial interface (it stands for Serial Quad Interface).
From a protocol point of view it is just the same as working with a normal serial interface, but instead of just one bit being transferred every clock, 4 bits can be transferred at once. Instead of a single data/clock, or din/dout/clock arrangement it has 4 data pins and one clock. This gives 4x the through put of a normal serial interface and doesn't require many more pins. In fact many SPI flash chips can also run in SQI mode without requiring any more than the existing 8 pins they already have. A significant increase in speed without any increase in real estate.
SQI is becoming a popular interface for faster loading of programs from external flash chips - not only used for simple microcontrollers, but also now often used for booting the BIOS of PCs, especially laptops, where space is a real concern.
The low pin count on the device itself is probably less important than the saving on the MCU or FPGA you connect it up to.
Finding 8 data pins, plus many more address, select and enable pins means a much bigger package and probably more expense for the MCU too.
While parallel EEPROM chips are faster and less complicated to communicate with, serial ones are less expensive hardware-wise, as they require less pins, energy, and wires/circuits.
Just for grins, let's say I have an old-timey 2-way radio in my airplane, with 16 frequencies available and selectable from the cockpit, where the control unit resides.
Aft, somewhere, is the transmitter-receiver unit with a cable running to the control unit containing, among other things, the 16 wires running to the cockpit selector switch required to do the frequency selection.
One day, when talking to a friend, I bring up the subject of the radio and ask him if it wouldn't be possible to encode the cockpit frequency settings into a four bit binary number and send that number over four wires (saving 12 wires) to the T/R unit where it would be decoded into the sixteen signals needed to do the frequency selection.
"Sure", he says, "but why stop there? instead of sending the [four bit] number all at once, why not send it a bit at a time over a single wire and have the decoder in the T/R unit figure out the frequency to select, saving 15 wires in the cable and 15 pins each in the connectors connecting the units?"
Below are some reasons why serial EEPROM is preferred over parallel EEPROM.
Lower Current Consumption. For example, operating currents for 16K serials are around 3 mA; the same for 16K parallel devices is approximately 30 mA and above. So the lower the current, the lower the power consumption.
Lower Voltage - serial EEPROMs are available in the markets which operates on low voltages (1.8-2.5 V). Low voltage operation also has a positive effect on power consumption.
Programmability - serial EEPROMs are easier to program compared to parallel. Serial EEPROMs have the ability and ease of programming one byte at a time;
Serial EEPROMs are available in smaller footprint
Lower pin count
Available at a lower price compared to parallel ones
Low microcontroller overhead and support