I definitely remember that era as the age of Perl but I should note that my first database-driven web app was in 1996, using a beta Java servlet runner with DB/2 on OS/2.
I'm happy to report that I got better at making technology choices.
I stand partly corrected. I only knew for certain servlet spec 2 was out in 99, and had not known anyone doing Java web serving stuff. I had colleagues doing java, and I worked in a commercial web house with those same colleagues, but none seemed to consider java web stuff (server side) usable (again memory's a bit hazy). I do know by 2000 some jumped in to servlets big time, but not many before that.
I think my first was perl/cgi in Jan 96 - not a full "web app" but I could read and write data via web forms to a database (msql IIRC). Feb 96 I know I was doing some PHP/FI, though still did a lot of Perl for years, mostly because that's what most hosts supported. For my own stuff, it was generally PHP even then when I had a choice.
By '97/'98 there were multiple vendors vying in this space - htmlos and ihtml are two names that stick with me, but there are some others I remember but can't recall names. And ColdFusion and whatnot, but... Perl and PHP were the big freebies, even by '97. ASP had speed on its side, but PHP already had convenience and price by '97, and it's gained ever since then. re: Java as server-side web platform - was outside my radar much, but the majority of people I worked with, even Java enthusiasts, didn't give it much credence before '99 - I don't think the infrastructure support was quite settled, and it was too 'wild west' for my colleagues (bunch of other reasons too). (IIRC, CF didn't support user-defined functions for several years, leading to much more difficult to maintain code than it should have been, but... memory gets hazy after 18 years).
But... PHP and Perl were free and largely "good enough" for enough of the problems most people were facing which is why they gained as much foothold as they did. ASP and CF both required a fairly hefty outlay and setup that you generally wouldn't be able to pay for without working in a corporate gig.