In April 2017 we had announced work on an open marketplace for cloud functions, lambdas and other serverless application artefacts and launched a first static website at Github Pages. The project was sidelined, but in January 2018 we made the implementation called Function Hub publicly available and have since been running a stateless dynamic demo instance with the backend running Snafu in passive mode in our APPUiO Swiss Container Platform account. You can use any deployment tool (awscli, wsk, gcloud) to submit your cloud functions and make them available globally.
It took Amazon a bit longer until February 2018 to announce their AWS Serverless Application Repository but of course there it is now with, at the time of writing, 181 entries. We assume that it will grow rapidly and developers will very much rely on it in the future, similarly to how Docker Hub has become an essential ingredient for modern application development, and see the need for researchers to (1) gain insight into cloud function marketplace usage, (2) propose superior designs, and (3) from an applied perspective of strengthening the economies of souvereign countries, assist in developing viable alternatives. This blog post therefore briefly discusses our state of function hub design and prototypical architecture which is shared work with the Distributed Systems and Parallel Computing research group at Itaipu Technology Park, Paraguay.
Ever since the inception of cloud computing as a widespread phenomenon over a decade ago, the issue of API and data structure variety across providers has become a major hurdle to multi-cloud applications. Even in the most recent services such as Function-as-a-Service (FaaS) offerings to build so-called serverless applications, the issue repeats itself with each provider pushing for their own management interfaces and accepted function definitions.
Yessica Bogado and Walter Benítez from Itaipu Technology Park, currently visiting the Service Prototyping Lab at Zurich University of Applied Sciences, are among the active researchers who tackle such practical problems from the perspective of engineering software applications based on microservices. In the park’s distributed systems and parallel computing research team led by Fabio López Pires, they are witnessing first hand the increasing issues of local software and service providers to keep up with cloud trends. Appropriate tooling can therefore help to alleviate the issues. This blog post describes one such tool, the FaaS converter, which has emerged from their applied research. Continue reading
Maciej Malawski from AGH University of Science and Technology in Kraków, Poland, visited us today to give a colloquium talk titled «Can we use Serverless Architectures and Highly-elastic Cloud Infrastructures for Scientific Computing?» and to discuss research around the wider topics of workflows and cloud function compositions. This post summarises the talk and the subsequent discussion mixed with further general reflections on the state of serverless applications.
Following up on the previous visit from Service Prototyping Lab (SPLab) at Zurich University of Applied Sciences in Switzerland to Itaipu Technology Park (PTI) in Paraguay, two young investigators from PTI’s Centre of Information and Communication Technology (CTIC) with support from CONACYT are now visiting us at the SPLab and more generally in Switzerland.
Yessica Bogado and Walter Benítez will spend some weeks to get to know the local research and development situation, get information about our ongoing research initiatives, dive into solving some hard questions, and discuss ideas for future collaboration. Furthermore, they will explore novel research methods and prototypes specifically in emerging technology areas such as cloud-native applications and serverless applications, as well as upcoming hybrid container/cloud function applications.
Walter Benítez, Yessica Bogado and the host Josef Spillner
Our own researchers Piyush and Josef are in Austin, the capital of the lone star state Texas to attend the current iteration of IEEE/ACM International Conference on Utility and Cloud Computing which takes place in conjunction with the International Conference on Big Data Computing, Applications and Technologies. ICCLab’s and SPLab’s recent research results have been accepted as multiple peer-reviewed workshop papers and a tutorial presented on the first day and a work in progress poster which will be presented in the next days.
In this series of blog posts, starting with this one, we will present our views and analysis of the results that will be presented at this event by cloud researchers from around the world.
As the trend continues to move towards Serverless Computing, Edge Computing and Functions as a Service (FaaS), the need for a storage system that can adapt to these architectures grows ever bigger. In a scenario where smart cars have to make decisions on a whim, there is no chance for that car to ask a data center what to do in this scenario. These scenarios constitute a driver for new storage solutions in more distributed architectures. In our work, we have been considering a scenario in which there is a distributed storage solution which exposes different local endpoints to applications distributed over a mix of cloud and local resources; such applications can give the storage infrastructure and indicator of the nature of the data which can then be used to determine where it should be stored. For example, data could be considered to be either latency-sensitive (in which case the storage system should try to store it as locally as possible) or loss sensitive (in which case the storage system should ensure it is on reliable storage). Continue reading
The discourse on cloud functions focuses heavily on diverse use cases: Standalone functions to perform a certain functionality, compositions of functions into complete applications, and functions as plumbing between separate application parts. This blog post intends to explore the use of cloud functions as extensibility mechanism for existing applications. It exemplifies the interaction between a function, a website and a login-protected web application and furthermore discusses implementation aspects and the notion of caching data in function instances.
Among the lectures offered by the Service Prototyping Lab is Scripting. Aimed at students of advanced studies, it teaches essential practical programming skills and conveys approaches how to automate the exploration of data retrieved from the Internet. Python is taught as programming languages and consequently a Python (Django) web application has thus far been used to automatically score the results submitted by students of a particular advanced task towards the end of the lecture. There’s nothing wrong with Django per se, but its roots have evidently been in the era of monolithic web applications. Armored with our Function-as-a-Service experience we decided to drop it and go purely serverless. In production.
Introducing selective Lambdafication
“Lambdafication” is the automated transformation of source code to make it run on AWS Lambda. It is a provider-specific flavour of generic “FaaSification” which is our ultimate research goal. With our Lambdafication tooling, we offer application engineers today the possibility to step into the serverless world without much effort, and leave the more challenging research tasks for the summer time.
PyParis is a community-organised conference on all topics around the Python programming language. The expected target group are primarily practitioners and researchers in the greater capital region of France, but also international engineers and language advocates. At Zurich University of Applied Sciences, Python is taught as automation and statistics application language to more than 200 business engineering, aviation and traffic engineering undergraduates per year. It is furthermore used a lot in research, including several prototypes resulting from the Service Prototyping Lab. Therefore, it was consequential for us to attend the conference and to contribute an in-depth tutorial on one of our research topics, Function-as-a-Service, to its attendees.