A pattern language for metadata-based frameworks

Guerra, Eduardo; Souza, Jerffeson; Fernandes, Clovis Torres

doi:10.1145/1943226.1943230

Cited by 23 publications

(32 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This section is based on a pattern language that studied several metadata-based frameworks and identifi ed recurrent solutions on them [ 1 ]. The practices presented focus mainly on metadata reading and processing, providing alternatives to extend behaviour on each mechanism.…”

Section: Internal Structurementioning

confidence: 99%

“…This section presents the two different types of hot spots that respectively use inheritance and composition to enable the application to add behaviour. New approaches in framework development can use other kinds of hot spots, such as refl ective method invocation [ 14 ] and metadata defi nition [ 1 ].…”

Section: Framework Conceptsmentioning

confidence: 99%

“…Metadata-based frameworks can be defi ned as frameworks that consume custom metadata from application classes to customize its behaviour [ 1 ]. Common approaches for metadata defi nition are XML documents, code annotations, code conventions and even databases.…”

Section: Introductionmentioning

confidence: 99%

“…Google Guice [ 8 ] uses metadata to inject dependencies from cloud services into application classes. It allows implementation classes to be programmatically bound to an interface and then injected into constructors, methods or fi elds using the @Inject annotation.Metadata-based frameworks can be defi ned as frameworks that consume custom metadata from application classes to customize its behaviour [ 1 ]. Common approaches for metadata defi nition are XML documents, code annotations, code conventions and even databases.…”

mentioning

confidence: 99%

“…The second is to enable an application to be built independently from the cloud providers, allowing each one to adapt the implementation according to its infrastructure. And fi nally, the third is to enable the evolution of the cloud services without affecting the deployed applications.This section is based on a pattern language that studied several metadata-based frameworks and identifi ed recurrent solutions on them [ 1 ]. The practices presented focus mainly on metadata reading and processing, providing alternatives to extend behaviour on each mechanism.…”

mentioning

confidence: 99%

See 4 more Smart Citations

Metadata-Based Frameworks in the Context of Cloud Computing

Guerra

Oliveira

2013

Computer Communications and Networks

View full text Add to dashboard Cite

In the context of cloud computing, one server is usually responsible to run multiple applications and a single application is spread across multiple servers. On the one hand, the applications need to be able to determine how the cloud environment should handle its execution, or even the execution of each one of its components. Yet, on the other hand, the applications should be decoupled from the middleware that executes them, enabling each one to evolve independently. Based on this scenario, it is possible to state that metadata-based frameworks are a suitable option for the interaction between the application and the services provided by the cloud, since it decouples the application from the environment and allows a transparent individual confi guration of each class. The goal of this chapter is to describe the essence of metadata-based frameworks and how they can be applied to cloud computing. It brings several examples of cloud computing frameworks and describes some design practices for the framework structure, scenarios that are suitable for the metadata-based approach and best practices for metadata confi guration. As a result, after reading this chapter, the reader should be able to understand the basic functioning of a metadata-based framework and why it is suitable for cloud applications. Keywords IntroductionCloud computing applications are executed across multiple servers, and this fact should be transparent to the developers, especially when the platform is provided as a service. Additionally, the application should interact with some cloud services, such as persistence and session management. To allow this transparency, the application should be decoupled from the cloud environment services. Since servers also execute many applications, another important requirement is to enable each application, or even each component, to confi gure how it should be handled by the cloud. Combining these two requirements, it is possible to conclude that the cloud provider should provide frameworks that, at the same time, abstract the cloud environment and allow a fl exible confi guration of how each application class should be handled.Many frameworks for developing cloud applications, such as Gaelyk [ 5 ], Objectify [ 6 ], Play Framework [ 7 ] and Guice [ 8 ], use metadata to allow a fi ne-grained confi guration of the application classes in the cloud environment. Gaelyk is a Groovy toolkit for web application development for Google App Engine (GAE) [ 5 ], which makes a classic use of metadata to map classes to persistent entities. Objectify implements the same mapping, but covering all features of the Google App Engine Datastore, using metadata also to defi ne entities, relationships and listeners.Another very interesting use for metadata can be found in Play Framework [ 7 ] where a web framework is deployed in GAE. It uses an annotation to schedule asynchronous jobs, which can run periodically or in an instant defi ned by expressions. Google Guice [ 8 ] uses metadata to inject dependencies from cloud serv...

show abstract

Section: Internal Structurementioning

confidence: 99%

Section: Framework Conceptsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 3 more Smart Citations