The effective Supervisory Control and Data Acquisition (SCADA) system can improve the reliability, safety and economic benefits of microgrid operation. In this research, the lower central controller and upper WEB monitoring system are connected by the SCADA system which is as the hub of microgrid intelligent monitoring platform. This system contains a set of specific functions programmed by Java as a middleware which can provide control and communication between the central controller and the upper monitoring system. The system realizes the real-time data acquisition and storage, the control instructions parsing and transmitting, the microgrid security and stability, the load balancing and resource recovery of the microgrid. All that functions have been tested and verified in the actual operation.

In recent years, Cloud Computing and Big Data have been considered the most attractive areas that are revolutionizing the IT world. Cloud Computing paradigm has recently appeared that allows running proprietary or difficult portable applications outside their original software environment on one or more virtual hardware platforms. Therefore, we are to developing such techniques which make it possible to secure communication between the communicating Cloud entities. These techniques must take into account several factors due to the data transmitted in this type of environment is proprietary and of significant size. Conventional data security techniques are not suitable for today's cloud usage. Hence, the main research of this thesis is to define an adaptable architecture with the aim to propose a scalable system that supports cloud services. We will define feasible security solutions dedicated to the Cloud computing context in order to robustly protect data stored in the Cloud. We are more precisely looking for working on NoSQL databases. We also intend to propose a secure solution based on the blockchain that has powerful features like decentralization, autonomy, security, reliability, and transparency.

Blockchain decentralized applications (ÐApps) are applications which run on Blockchains nodes. Thus, in order to interact directly with this sort of applications, users need to have a blockchain address, wallet and knowledge about how to make transactions in order to interact with ÐApps. Therefore, the knowledge required to use a ÐApp can easily make users to desist when trying to interact with them. In order to tackle this issue, we propose a software architecture that will be located in the middle of the user and the ÐApp, thus making users initially unaware that they are interacting with a ÐApp. This is achieved by analyzing the relationship between ÐApps and Apps by using UML modelling. Next, based in the previous analysis, we created a middleware for users to interact with a ÐApp in the same manner the do with a traditional web app, i.e. by using usernames, passwords and UI elements instead of addresses, private keys or transactions. Finally, in order to put the developed middleware into practice, we developed a ÐApp that makes use of it. This ÐApp registers the time control of workers from companies by using Blockchain to store the data in a secure and non-modifiable manner.

Currently, most middleware application developers have two choices when designing or implementing API services: They can either stick with REST or explore the emerging GraphQL technology. Although REST is widely considered the standard method for API development, GraphQL is believed to overcome the main drawbacks of REST, especially data fetching issues. Yet, doubts remain as there are no experimental studies with convincing results to evaluate the performance of the two services. In this paper, we propose a research methodology to evaluate the performance of REST and GraphQL API services, which includes two main contributions. The first contribution is that the performance evaluation of the two services is conducted in the real operation of a massive and intensively accessible management information system. The second contribution is the fair and independent performance evaluation results obtained for both API services. The performance evaluation was studied using basic measures of QoS, including response time, throughput, CPU load, and memory usage. The results show that REST is still faster in response time and throughput, while GraphQL is very efficient in resource utilization, i.e., CPU load and memory utilization. Therefore, GraphQL is the right choice when data requirements change frequently and resource utilization is the most important consideration. REST is used when some data is frequently accessed called by multiple requests.