Multi-Hosting Application & Balloon Services: A Novel Cloud Native Architecture & Its Ecosystem

By Aaron Ran

This book proposed a novel cloud native architecture, the multi-hosting application, that expand the software resource reuses and enables rapid production. Such applications run on a kind of uniquely designed services, the balloon services, that only live on the cloud platform. In addition to the boosted productivity, it creates a new business model and will eventually give the birth of a new cloud ecosystem.

• Language: English
• Publisher: Aaron Ran
• Release date: Jun 8, 2022

Aaron Ran

Aaron Ran is senior architect at IBM, awarded distinguished architect at The Open Group. For twenty years at IBM, he has engaged in the informationization transformation and innovation of many critical systems worldwide, traveling to almost forty countries. Besides information technology, he is passionate about culture, history, and political studies.

Book preview

Multi-Hosting Application

& Balloon Services

A novel cloud native architecture & its ecosystem

Revision 1.0

By Aaron Ran

[e-mail]

Copyright 2022 Aaron Ran

Table of Contents

Chapter 1.      Sisyphus as a Developer

Chapter 2.      It’s the Data

Chapter 3.      Every Problem Has a Solution

Chapter 4.      Dancing in the New Shoes

Chapter 5.      The Dance Floor

Chapter 6.      A Tropical Cloud

For those dear readers not familiar with Greek mythology, Sisyphus was the king of Ephyra. For escaping the fate of death, he cheated Hades, the god of the death rules the underworld, eventually was punished for his trickery.  As the punishment, he must roll a huge boulder up a steep hill, but every time he almost made to the top, the boulder rolled away and back to the bottom, then he had to repeat this hopeless effort forever.

During my years in the IT industry, I saw Sisyphus in many fellow co-workers. I once had a conversation with a senior developer in a banking system project. He was assigned to create a complex module that would typically cost several person-weeks of effort. When he gave me the work estimation, he promised that the deviation would be no more than a few person-hours. I was impressed by his confidence in the accuracy, and he told me, It’s only because I’ve built this same feature so many times!

This reveals a fact: across projects, many standard features, e.g., user authentication, query & pagination, billing, payment, incident management, etc., despite being reinvented millions of times, are still costing development efforts again and again. Eliminating this repetition can prevent this vast waste; apparently, reuse is the answer--wherever the existing software resources (source code, binary, services) are utilized, the money and time for building them are saved.

Software resource reuse benefits not only the financial but also the