TecnoCampus Foundation
eCampus
University Business
eCampus

What are you looking for?

General information

Subject type: Mandatory

Coordinator: Rosa Herrero Antón

Trimester: Second term

Credits: 6

Teaching staff: 

Josep Roure Alcobé
Alfredo Rueda Unsain 

Teaching languages

  • Catalan

Skills

Basic skills

  • B2_That students know how to apply their knowledge to their job or vocation in a professional way and have the skills they demonstrate by developing and defending arguments and solving problems within their area of ​​study

  • B3_Students have the ability to gather and interpret relevant data (usually within their area of ​​study), to make judgments that include reflection on relevant social, scientific or ethical issues

  • B4_That students can convey information, ideas, problems and solutions to both specialized and non-specialized audiences

  • B5_That students have developed those learning skills necessary to undertake further studies with a high degree of autonomy

Specific skills

  • EFB6_Adequate knowledge of the concept of company, institutional and legal framework of the company. Organization and management of companies

  • EIS1_Ability to develop, maintain and evaluate software services and systems that meet all user requirements and that behave reliably and efficiently, are affordable to develop and maintain and comply with quality standards, applying theories, principles, methods and software engineering practices

  • EIS2_Ability to assess customer needs and specify software requirements to meet those needs, reconciling conflicting goals, by seeking acceptable compromises, within the limitations of cost, time, the existence of already developed systems and of the organizations themselves

  • EIS3_Ability to solve integration problems based on available strategies, standards and technology

  • EIS4_Ability to identify and analyze problems and design, develop, implement, verify and document software solutions based on adequate knowledge of current theories, models and techniques

  • EIS5_Ability to identify, assess and manage potential associated risks that may arise

  • EIS6_Ability to design appropriate solutions in one or more application domains, using software engineering methods that integrate ethical, social, legal and economic aspects

  • ESI1_Ability to integrate Information and Communications Technology solutions and business processes to meet the information needs of organizations, enabling them to achieve their goals effectively and efficiently, thus achieving competitive advantage

  • ESI2_Ability to determine the requirements of the information and communication systems of an organization, taking into account security aspects and compliance with current regulations and legislation

  • ESI3_Ability to actively participate in the specification, design, implementation and maintenance of information and communication systems

  • ESI4_Ability to understand and apply the principles and practices of organizations, so that they can act as a link between the technical and management communities of an organization and actively participate in user training

  • ESI5_Ability to understand and apply the principles of risk assessment and apply them correctly in the elaboration and execution of action plans

  • ESI6_Ability to understand and apply the principles and techniques of quality management and technological innovation in organizations

Transversal competences

  • T1_That students know a third language, which will be preferably English, with an adequate level of oral and written form, according to the needs of the graduates in each degree

  • T2_That students have the ability to work as members of an interdisciplinary team either as one more member, or performing management tasks in order to contribute to developing projects with pragmatism and a sense of responsibility, making commitments taking into account the available resources

Description

In this subject you will see a global view of the three architectures of the information systems most used today in the industry. First, two monolithic architectures where all functionality is in a single module: layered architecture and we'll also see the family of "clean" or hexagonal architectures that separate the domain and application controllers from the outside. This second architecture (the clean) facilitates the separation of functionalities in different modules. Third, we'll explore microservice-based architectures that seek to separate functionality into independent but interconnected applications. We will see the advantages and disadvantages of each of them while referring to the consequences they have in the organization of the teams that develop and manage Information Systems. We will also introduce tools related to DevOps such as containers and the server concept immutable The practices will focus on hexagonal architectures and those based on microservices.

Important: in the practices we use the programming framework Spring boot i SpringCloud which are introduced during the subject Internet Applications Laboratory. It is recommended to have taken it before doing Information Systems Design.

 

Contents

1.- Motivation
2.- Introduction to software and systems architecture
3.- Monolithic architectures
    3.1.- Characteristics
    3.2.- We revisit the architecture in layers
4.- "Clean" or hexagonal architectures
    4.1.- Characteristics
    4.2.- A structure that explains the functionality
    4.3.- Ports and adapters
    4.4.- Mapping between layers
    4.5.- Organization in modules
5.- Distributed architectures: microservices
    5.1.- Introduction: “the monolith hell”
    5.2.- Modeling: DDD 
    5.3.- Communication models (synchronous and asynchronous)
    5.4.- Transactions and “eventual consistency”
    5.5.- Infrastructure patterns

Evaluation system

Assessment

  • PR_E: written test. Weighting of the final grade 30%
  • PR_P: practical test. Weighting of the final grade 30%
  • PRAC: practices from 1 to 5. Weighting in the final grade 40% (each 8%) if the grade of PR_E> = 3,5 and PR_P> = 3,5

Final grade calculation (NF):

  • If PR_E> = 3,5 and PR_P> = 3,5: NF = PON = PR_E 0,3 + PR_E2 0,3 + PRAC 0.4
  • Si (PR_E <3,5 or PR_P <3,5: NF = min ((PR_E 0,3 + PR_P 0,3), PON)

Recovery:

  • The two tests (PR_E and PR_P) can be retrieved separately. The final grade will be calculated as set out above with the test recovery grades.

Normative:

  • Attendance at internships is mandatory. If a student does not attend an internship session he will be graded with a grade of 0 (zero) in the corresponding internship
  • Following UPF regulations, if it is detected that a practice or test has been copied, it will be 0 (zero) of both the copy and the copy.
  • In order for the student to be entitled to recovery, he / she must have taken both tests (PR_E and PR_R).

REFERENCES

Basic

Get Your Hands Dirty on Clean Architecture: A hands-on guide to creating clean web applications with code examples in Java. Tom Hombergs. Package Ed

Newman, Sam (2021), “Building Microservices: Designing Fine-Grained Systems” (2nd edition). O'Reilly Media

Complementary

Josh Long, Kenny Bastani, "Cloud Native Java. Designing Resilient Systems with Spring Boot, Spring Cloud, and Cloud Foundry." O'Reilly 2017

Chris Richardson. Microservice patterns: https://microservices.io/

Hands-On Microservices with Spring Boot and Spring Cloud. By Magnus Larsson. Packt publisher (2019)