Short history of information technologies

1950s – Compilers will make programmers obsolete
1960-70s - 3rd generation programming languages will reduce programmer shortages

...

1980s - 4rd generation programming languages and CASE tools will definitely reduce programmer shortages
1980s – client server SQL DBMS will solve mainframe “vendor lock”
1990s – 3-tiers architecture will solve DBMS “vendor lock”
1996 – XML and SOAP will fix interoperability between tiers and app server “vendor lock”
1996 – Java will fix code portability (write once – run everywhere)
1997 – CORBA will solve all integration issues
1998 – MS Java extension will fix Sun Java poor performance
2000 – .NET will fix Java “vendor lock”

...

2001 – Enterprise Service Buses (ESB) will solve CORBA complexity and "vendor lock"
2005 – SOA will fix the challenges ESB introduced
2006 – NoSQL will overcome relational database limits
2008 – REST APIs will simplify SOA and fix SOAP performance
2009 – "SQL" over NoSQL databases will fix NoSQL poor querying
2015 – Microservices will save us from SOA complexity (and monoliths)
2016 – Docker will fix microservice headaches
2018 – Kubernetes will fix Docker headaches
2020 – Service Mesh will make Kubernetes manageable
2022 – Serverless programming will abstract away Service Mesh
2024 – AI Observability will bring clarity to Serverless chaos
2025 - AI will replace programmers
^^ YOU ARE HERE ^^

Mechanics of software Programming is thinking, not typing
Home \| Categories \| Tags \| Search	\| eng \| рус