Spelling suggestions: "subject:"[een] CLOUD API"" "subject:"[enn] CLOUD API""
1 |
[en] DEPLOYMENT OF DISTRIBUTED COMPONENT-BASED APPLICATIONS ON CLOUD INFRASTRUCTURES / [pt] IMPLANTAÇÃO DE APLICAÇÕES BASEADAS EM COMPONENTES DISTRIBUÍDOS SOBRE INFRAESTRUTURAS NA NUVEMEDWARD JOSE PACHECO CONDORI 07 November 2014 (has links)
[pt] A implantação de aplicações baseadas em componentes distribuídos é composta por um conjunto de atividades geridas por uma Infraestrutura de Implantação. Aplicações atuais estão se tornando cada vez mais complexas, necessitando de um ambiente alvo dinâmico e multi-plataforma. Assim, a atividade de planejamento de uma implantação é o passo mais crítico, pois define a configuração da infraestrutura de execução de forma a atender os requisitos do ambiente alvo de uma aplicação. Por outro lado, o modelo
de serviço na nuvem chamado Infraestrutura como Serviço(IaaS) oferece recursos computacionais sob demanda, com características dinâmicas, escaláveis e elásticas. Nesta dissertação nós estendemos a Infraestrutura de Implantação para componentes SCS de forma a permitir o uso de nuvens privadas ou públicas como o ambiente alvo de uma implantação, através do uso de uma cloud API e políticas flexíveis para especificar um ambiente alvo personalizado. Além disso, hospedamos a infraestrutura de implantação na nuvem. Isto permitiu-nos usar recursos computacionais sob demanda para instanciar os serviços da Infraestrutura de Implantação, produzindo uma Plataforma como Serviço(PaaS) experimental. / [en] Deployment of distributed component-based applications is composed of a set of activities managed by a Deployment Infrastructure. Current applications are becoming increasingly more complex, requiring a
multi-platform and a dynamic target environment. Thus, the planning activity is the most critical step because it defines the configuration of the execution infrastructure in order to satisfy the requirements of
the application’s target environment. On the other hand, the cloud service model called Infrastructure as a Service (IaaS) offers on-demand computational resources with dynamic, scalable, and elastic features. In this work we have extended the Deployment Infrastructure for SCS componentes to support private or public clouds as its target environment, through the use of a cloud API and flexible policies to specify a customized target environment. Additionally, we host the Deployment Infrastructure on the cloud, which allow us to use on-demand computational resources to instantiate Deployment Infrastructure services, creating an experimental Platform as a Service (PaaS).
|
2 |
An analysis of API usability and Azure API managementBlommendahl, Simon January 2016 (has links)
In today’s computer environments the systems are getting bigger and more complex for each day that passes by. The motivating factor for this is that the customer wants to achieve more and more with their computer systems than before. The only way to really solve this task is to use even more APIs (Application program interfaces) in their systems. When using more APIs in a system, there is a chance that the specific system provides the same type of API twice, which of course, is a waste of storage and resources. In addition, the more APIs a system contains, the bigger the risk is for mismanagement of these APIs. In the worst case, this can result in security breaches or data leaks. This thesis investigates specific APIs provided for a customer of Sigma IT Consulting. The aim is to evaluate and organize the APIs according to their usability criteria. The main focus of the evaluation is the available documentation which will be evaluated by a questionnaire survey distributed to senior software developers at Sigma IT Consulting in Växjö. Conclusions will then be drawn depending on the result from the survey, and we can then see if Azure API management (which is a service to make a system more user – friendly) is accurate in its way of organizing with the API usability as the main focus! Unfortunately, Azure API management did not have any possibility what so ever to customize the API placement in a system, and the only way the APIs are organized is in alphabetical order. Therefore, a prototype with even more sorting functionality than Azure API management will also be presented in this thesis.
|
Page generated in 0.0477 seconds