Layne Sadler created ZEPPELIN-4271:
--------------------------------------
Summary: Vision: become the modern realtime webapp front end
Key: ZEPPELIN-4271
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4271
Project: Zeppelin
Issue Type: New Feature
Reporter: Layne Sadler
In presenting a language-agnostic way edit and render *interactive content
(potentially realtime)* content... Zeppelin notebooks have the potential to
replace (abstract) today's front end frameworks all together. Django/Flask,
Rails, and Laravel desperately need an easier way for backend programmers to
render their content. The fullstack skillset needed to maintain an API/backend
layer and a realtime js *front end framework* (representing the transition from
webapp templates \{{jinja}} to javascript) is just too wide and lacks
standardization.
I run my Django app in a Python env... I then activate that Python env in a
Zeppelin notebook... giving my Zeppelin code complete access to my models and
controller (MVC) of my app. AKA Zeppelin **is** already the front end (the +*V
in MVC*+) for my app without the need for authentication or an API/SDK layer. I
can rearrange the tiles in a responsive grid... show users tables of content...
and render graphics.
Because the Python kernel/env is shared between my front end (zepl) and my
backend (django)... this essentially is *full-stack Python.* However, this is
not limited to Python, it would work with *any language*/ interpreter such as
Ruby on Rails, Elixir, Graphql-based frameworks.
Although Zeppelin paragraphs can already be embedded. What is needed is logic
layer support in the web-app frameworks like `djangorestframework's APIView` to
*bridge the gap between the V and the C in the MVC model*. Something like
NotebookResponse in addition to JsonResponse and TemplateResponse.
This would turn Zeppelin into an `*Application Browser*` competitor to the
`Webpage Browser`. Aka... Zepl (change it back to ZeppelinHub) would become the
iTunes/AppStore/HTML of it's day.
Once this *application building ecosystem* takes off, introduce a Kafka-based
OpenAPI network using OAuth2.0 authentication to enable applications to fluidly
share data in an operating system manner... to become the new internet/ replace
layer 5 in the OSI model.
---
P.S. 1
Additionally, Zeppelin's integration with pyspark could make Spark the default
execution engine for Django querysets aka backend.
P.S. 2
I was surprised not to be able to change the Zeppelin window style (dark theme)
from the 8080 UI. Making sure the ecosystem can customize this will be
important for branding/ white labeling.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
