Java call stack – from HTTP upto JDBC as a picture (2006)
ptrthomas.wordpress.com
Java call stack – from HTTP upto JDBC as a picture (2006)
1–10 of 63 posts
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#2This should be titled "Acegi/Spring/Hibernate" call stack. And none of those technologies are needed to build a JEE webapp.
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#3This should be titled "Acegi/Spring/Hibernate" call stack. And none of those technologies are needed to build a JEE webapp.
While that's entirely true, the glueing of those frameworks together is very common in the Enterprise Java development space especially around 2006 when this was taken.
I'm a big fan of the JVM and the Java ecosystem but in many ways the JVM ecosystem is split into two worlds: frameworks or libraries. This would be an example of a framework heavy development model where god knows what is going on between the outside world, your biz logic and the database calls.
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#4This should be titled "Acegi/Spring/Hibernate" call stack. And none of those technologies are needed to build a JEE webapp.
While that's entirely true, the glueing of those frameworks together is very common in the Enterprise Java development space especially around 2006 when this was taken. I'm a big fan of the JVM and the Java ecosystem but in many ways the JVM ecosystem is split into two worlds: frameworks or libraries. This would be an example of a framework heavy development model where god knows what is going on between the outside…
> common in the Enterprise Java development space especially around 2006
Can you mention which frameworks and glues are common today ?
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#5Not sure it is any smaller today. Some additional layers not seen are the DTO transformations (not seen because they don't become part of the stack when it's hitting JDBC) but two more major subsystems. Many IDEs now automatically filter out these well known stacks from view.
Personally moving from a mostly Java background to entirely typescript on the backend and front-end.
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#6Earlier quoted context omitted.
While that's entirely true, the glueing of those frameworks together is very common in the Enterprise Java development space especially around 2006 when this was taken. I'm a big fan of the JVM and the Java ecosystem but in many ways the JVM ecosystem is split into two worlds: frameworks or libraries. This would be an example of a framework heavy development model where god knows what is going on between the outside…
> common in the Enterprise Java development space especially around 2006 Can you mention which frameworks and glues are common today ?
Acegi/Spring/Hibernate :>
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#7The fact that Spring even exists should be a big red flag for the value of static typing. People routinely make mistakes using type systems. And when done correctly I see static type systems work very well solving problems that they themselves created.
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#8Not sure it is any smaller today. Some additional layers not seen are the DTO transformations (not seen because they don't become part of the stack when it's hitting JDBC) but two more major subsystems. Many IDEs now automatically filter out these well known stacks from view. Personally moving from a mostly Java background to entirely typescript on the backend and front-end.
[deleted]
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#9Earlier quoted context omitted.
While that's entirely true, the glueing of those frameworks together is very common in the Enterprise Java development space especially around 2006 when this was taken. I'm a big fan of the JVM and the Java ecosystem but in many ways the JVM ecosystem is split into two worlds: frameworks or libraries. This would be an example of a framework heavy development model where god knows what is going on between the outside…
> common in the Enterprise Java development space especially around 2006 Can you mention which frameworks and glues are common today ?
Spring Boot, but that includes Spring Security (was Acegi) and Spring MVC. Spring Data (JPA) has taken over from Hibernate.
Re: Java call stack – from HTTP upto JDBC as a picture (2006)
#10This should be titled "Acegi/Spring/Hibernate" call stack. And none of those technologies are needed to build a JEE webapp.
While that's entirely true, the glueing of those frameworks together is very common in the Enterprise Java development space especially around 2006 when this was taken. I'm a big fan of the JVM and the Java ecosystem but in many ways the JVM ecosystem is split into two worlds: frameworks or libraries. This would be an example of a framework heavy development model where god knows what is going on between the outside…
Man the java era was seriously seriously wrong[1]. IMO it's only there because people invested so much, they'll never cut their losses and stay in denial for one or two decades.
[1] java 8 makes thinks bearable, but even then you feel like sculpting chapter 1 lisp/haskell idioms in granite with a spoon.