Three-tier architecture Rational tools, XML, and BEA Weblogic. Very 2000 article.
There's not really enough technical details there to know for sure what they did over 20 years ago, but here's a couple of clues:
"A component is simply a chunk of software that performs work or provides information within a wider application. A component could be the user interface on an order entry system, the rules for how and when to increase a customer's credit limit, or a data warehouse detailing every customer transaction conducted during the past five years."
...
'"we developed once and used everywhere throughout our site," says Mitchell. "If we hadn't . . . we would have to rewrite [that] code in every page on our site."'
That doesn't sound like microservices, that just sounds like libraries of code. The two are not interchangable.
I think there is a difference. Components were units of code which were compiled and linked into application executables. Microservices run independently and are invoked over a network connection and protocol.
Three-tier architecture Rational tools, XML, and BEA Weblogic. Very 2000 article.
There's not really enough technical details there to know for sure what they did over 20 years ago, but here's a couple of clues:
"A component is simply a chunk of software that performs work or provides information within a wider application. A component could be the user interface on an order entry system, the rules for how and when to increase a customer's credit limit, or a data warehouse detailing every customer transaction conducted during the past five years."
...
'"we developed once and used everywhere throughout our site," says Mitchell. "If we hadn't . . . we would have to rewrite [that] code in every page on our site."'
That doesn't sound like microservices, that just sounds like libraries of code. The two are not interchangable.