Challenges & opportunities for cloud-native applications
Current technology landscape for cloud-native apps is evolving and Platform-as-a-Service (PaaS) solutions are constantly changing to meet the demands such architecture. As customers need flexibility and openness in terms of choosing PaaS solution (without any vendor or technology lock-in), a key need is to provide a neutral view in terms of:
- Which PaaS solution is the right fit for my enterprise (considering unique opportunities and challenges in each enterprise)?
- How does it help in realizing the vision of migrating toward cloud-native apps (with microservices as an architectural style of business services)?
The overarching problem of choosing the right technology solution & partner towards enterprise-level cloud-native apps creates an opportunity for all of us to innovate, build and implement the right-fit solution in a progressive manner.
Capabilities of Platform as a service for cloud-native applications
A reference architecture outlined below denotes the key set of capabilities required for building cloud-native apps and helps in choosing the right platform offering these capabilities:
Key platform as a service (PaaS) solution options
Considering current market landscape with both serverless and other emerging trends, current PaaS solutions can be visualized as below (there are many variations coming out of options shown here by different vendors):
Cloud-native apps development is an evolving field and considering the novelty of the solution, industry players and standards bodies (such as IEEE) are still firming up standards and best practices. As there is no silver bullet in choosing any solution and enterprise context, governance and required capabilities drive the recommended platform as a service (PaaS) solution in supporting cloud-native applications.
|Published on Java Code Geeks with permission by Ankur Kumar, partner at our JCG program. See the original article here: Emerging role of PaaS (Platform as a service) in building cloud-native applications
Opinions expressed by Java Code Geeks contributors are their own.