User Tools

Site Tools


tanszek:oktatas:iss_t:evolution_of_software_integration_methods

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
tanszek:oktatas:iss_t:evolution_of_software_integration_methods [2023/03/27 08:15] kneheztanszek:oktatas:iss_t:evolution_of_software_integration_methods [2026/02/23 06:01] (current) – [Middleware development method] knehez
Line 1: Line 1:
-Following figure shows the six classical Software Integration methods.+==== Six Standard Software Integration Methods ==== 
  
-{{tanszek:oktatas:integration_evolution.png|}}+{{tanszek:oktatas:integration_evolution.png?600x0|}}
  
  
 ==== Development methods of Information System Components ==== ==== Development methods of Information System Components ====
  
-Below we present the basic methods by which IT system components can be developed. IT systems and some of their components differ from traditional stand-alone applications in that, **we expect them to function as a service with almost constant availability**. +Belowwe present the basic methods for developing IT system components. IT systems and some of their components differ from traditional stand-alone applications in that, **we expect them to function as a service with almost constant availability**. 
  
 However, in order for an application/software to function as a service, it immediately raises the following questions: However, in order for an application/software to function as a service, it immediately raises the following questions:
Line 13: Line 13:
   * How can we manage the resources of the component?   * How can we manage the resources of the component?
   * Where/how can we get the configuration information needed to run?   * Where/how can we get the configuration information needed to run?
-  * How can we communicate with the environment, or the other sw components?+  * How can we communicate with the environment, or the other software components?
  
 ==== Native development method ==== ==== Native development method ====
Line 35: Line 35:
  
   * the standard handling of used dependencies (components developed by others) is not uniform, but after 2020, we can use [[https://conan.io/]] or [[https://vcpkg.io/en/]] or the modern [[https://cmake.org/cmake/help/latest/guide/using-dependencies/index.html]].    * the standard handling of used dependencies (components developed by others) is not uniform, but after 2020, we can use [[https://conan.io/]] or [[https://vcpkg.io/en/]] or the modern [[https://cmake.org/cmake/help/latest/guide/using-dependencies/index.html]]. 
-  * RELEASE/DEBUG mode compilation method slows down development+  * RELEASE/DEBUG mode compilation method slows down development (see: https://godbolt.org)
   * it is possible that the operation of the program is different (erroneous, slower) with another compiler   * it is possible that the operation of the program is different (erroneous, slower) with another compiler
  
Line 67: Line 67:
   * LLVM: this is not the classic VM, but it compiles the source into an llvm byte code, which then turns into native code. "LLVM is designed around a language-independent intermediate representation that serves as a portable, high-level assembly language that can be optimized with a variety of transformations over multiple passes.   * LLVM: this is not the classic VM, but it compiles the source into an llvm byte code, which then turns into native code. "LLVM is designed around a language-independent intermediate representation that serves as a portable, high-level assembly language that can be optimized with a variety of transformations over multiple passes.
  
-**Just in Time (JIT) translation**+**Just in Time (JIT) compilation**
   * The virtual machine can continuously optimize the application code, the byte code conversion is dynamic.   * The virtual machine can continuously optimize the application code, the byte code conversion is dynamic.
  
Line 92: Line 92:
 {{tanszek:oktatas:informatikai_rendszerek_epitese:jee_fejlesztes.png|}} {{tanszek:oktatas:informatikai_rendszerek_epitese:jee_fejlesztes.png|}}
  
-Application server development method. It was originally released by Sun Microsystems in 1999 under the name J2EE (Java 2 Enterprise Edition). The standard specification is currently at version 8 (2017): https://javaee.github.io/javaee-spec/+Application server development method. It was originally released by Sun Microsystems in 1999 under the name J2EE (Java 2 Enterprise Edition). The standard specification is currently at version 8 (2017): https://javaee.github.io/javaee-spec/ - latest: https://jakarta.ee/specifications/
  
-  * It typically uses middleware implemented in Java. [[https://en.wikipedia.org/wiki/List_of_application_servers]|List of App Servers]+  * It typically uses middleware implemented in Java. [[https://en.wikipedia.org/wiki/List_of_application_servers]]
   * famous implementations: Glashfish, Websphere, Weblogic, JBoss, Wildfly   * famous implementations: Glashfish, Websphere, Weblogic, JBoss, Wildfly
  
Line 126: Line 126:
 In the first versions, metadata was managed with XML descriptors. In these, it was possible to specify how a class should behave: URL mapping, number of running instances, etc. In the first versions, metadata was managed with XML descriptors. In these, it was possible to specify how a class should behave: URL mapping, number of running instances, etc.
  
-== ESB - Enterprise service bus ==+==== ESB - Enterprise service bus ==== 
 +{{tanszek:oktatas:informatikai_rendszerek_epitese:esb.png|ESB}}
  
 Service BUS: Service Oriented Architecture (SOA). It is based on loosely coupled components (services). Analogy of the BUS concept known in networks. Service BUS: Service Oriented Architecture (SOA). It is based on loosely coupled components (services). Analogy of the BUS concept known in networks.
tanszek/oktatas/iss_t/evolution_of_software_integration_methods.1679904954.txt.gz · Last modified: 2023/03/27 08:15 by knehez