Abstract
The increasing availability of edge and IoT infrastructure-as-a-service allows us to develop lightweight IoT components and deploy them into edge/IoT infrastructures, enabling edge analytics and controls. This paper introduces the development of service contracts for IoT microservices from DevOps perspectives. We analyze stakeholders and present our methods to support stakeholders to program IoT service contracts. We address the diversity of service contracts by using common languages for IoT data and programming. We integrate the development and operation lifecycle of IoT contracts with IoT software components and with supporting DevOps services. To illustrate our approach, we use a real-world Base Transceiver Station maintenance application with Raspberry Pi, Java, JavaScript, JSON and other microservices.
Highlights
The rise of IoT device-as-a-service, IoT infrastructure-as-a-service and edge infrastructure-as-a-service [1] has created several challenges for software development
Little effort has been spent for examining service contracts along existing phases of the IoT software development in the context of IoT-as-a-service, where IoT and edge infrastructures can be provided under on-demand, pay-per-use principles
As we use JSON to specify contract terms and contracts, which are available in the registry, one can consider such terms/contracts as artifacts associated with IoT services, e.g., like configuration information for software components
Summary
The rise of IoT device-as-a-service, IoT infrastructure-as-a-service and edge infrastructure-as-a-service [1] has created several challenges for software development. We consider the case in which one will develop IoT software service – called IoT (micro)services – from various components – called IoT units – and deploy such services in IoT infrastructure-as-a-service. The challenges for contracts in IoT are due to diverse underlying APIs for data and control that need to be integrated well with the development and operation of IoT units/services. While we can leverage quite common structures and categories of contracts from the related work, it is not enough to start the integration and development of contract only when deploying IoT components to the infrastructure. In this paper we examine the following key question: if a developer follows DevOps for IoT units/microservices, what would be steps/methods to do w.r.t services contracts for such IoT software?.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
