ESU mobilizes efforts on the social dimension

No ratings yet. Log in to rate.
SiS Catalyst ESU representatives took an active part in the event.

LIVERPOOL – A training was organised in Liverpool, England, from 10 to 13 June 2014 in the framework of the SiS Catalyst project. The main aim of this project was to train new students‘ experts in the area of social dimension. Ten student representatives from Sweden, Romania, France, Denmark, Iceland, Latvia, Portugal, Germany and Ireland participated in the meeting.

This training session introduced some of the most challenging debates taking place in the area of the social dimension of higher education. The participants were invited to an extensive session where the history and development of the social dimension was analysed as well as specifics in the field of higher education.

Understanding the social dimension

The SiS Catalyst training provided food for thought when the participants engaged in discussions about terms such as inclusive excellence and locally defined minorities and performance based funding. Not only did this event disseminate the general outcomes of the project, but also create a broader understanding of the social dimension within the European Higher Education Area.

Representatives of the European Students‘ Union (ESU) took an active part in the meeting, as the organisation is a partner of the SiS Catalyst project. ESU used the opportunity to present other projects that it has involved in and concern the social dimension, such as PL4SD and IDEAS.

Push for the social dimension

This meeting was a clear sign of ESU’s commitment to push work on the social dimension forward, in preperation for a new and challenging year of the Bologna process ending with a ministerial conference in 2015.

A visit to the Slavery Museum was also organised during the meeting with a social evening held at the Victoria’s Quarter and a presentation on the so-called student volunteer module, where ESU participated in one of the pilot sessions for the use of making a SiS Catalyst toolkit.

-- END ---

For more information, please contact:

Elisabeth Gehrke, ESU Chairperson: +32/479.591.499 // or Robert Hlynur Baldursson, ESU Communications Manager: +32/473.669.894 //

The European Students’ Union, headquartered in Brussels, is the umbrella organisation of 47 national unions of students from 39 European countries. ESU represents and promotes the educational, social, economical and cultural interests of students at the European level. Through its member unions, ESU represents over 11 million students in Europe. To find out more about ESU, follow us on Twitter @ESUtwt, check out or Facebook page or visit ESU celebrates its 30th anniversary in 2012.



Wq123 Wq123
03:03 on 26 Oct 15 In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit. Enterprise Applications are often built in three main parts: a client-side user interface (consisting of HTML pages and javascript running in a browser on the user's machine) a database (consisting of many tables inserted into a common, and usually relational, database management system), and a server-side application. The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. This server-side application is a monolith - a single logical executable[2]. Any changes to the system involve building and deploying a new version of the server-side application. Such a monolithic server is a natural way to approach building such a system. All your logic for handling a request runs in a single process, allowing you to use the basic features of your language to divide up the application into classes, functions, and namespaces. With some care, you can run and test the application on a developer's laptop, and use a deployment pipeline to ensure that changes are properly tested and deployed into production. You can horizontally scale the monolith by running many instances behind a load-balancer. Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the cloud . Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource.
Please log in to comment.