The Fortune 500 has thousands of line-of-business applications that do not easily port to a cloud-native architecture. In order to deliver next-generation cloud-native apps to market, developers typically need to coordinate between various siloed groups. Here we explain a framework for a PaaS that supports both cloud-native and existing applications in the enterprise.

1. Orchestrating
Cloud-­‐Native
and
Traditional
Application
Architectures
Sinclair
Schuller,
CEO
sschuller@apprenda.com

2. A PPRENDA.COM
Let’s
Start
With
Some
Facts

3. A PPRENDA.COM
Existing
investments
in
enterprise
IT
aren’t
going
anywhere
FAC T
# 1

4. A PPRENDA.COM
Apps
can
be
cloud
native,
enterprise
IT
IS
NOT
FAC T
# 2

5. A PPRENDA.COM
Most
cloud
native
apps
written
in
the
enterprise
WILL
HAVE non-­‐cloud
native
dependencies
FAC T
# 3

6. A PPRENDA.COM
What
do
we
mean
when
we
say
“traditional”
application
architectures?

7. A PPRENDA.COM
• Apps
are
monolithic
• Dependencies
on
“heavy”
non-­‐volatile
tech
• Configuration
is
embedded
and
static
• Infrastructure
specificity
is
everywhere
• Lack
of
decomposed
deployability
• Lack
of
portability
RDBMS RDBMS Mainframe
Data
Tier Adapter
Business
Logic
Tier
UI
Tier

8. A PPRENDA.COM

9. A PPRENDA.COM
Decompose
all
existing
enterprise
apps
into
microservices
O P T IO N
# 1

10. A PPRENDA.COM
O P T IO N
# 1
Decompose
all
existing
enterprise
apps
into
microservices

11. A PPRENDA.COM
Leverage
CI/CD
tooling
and
platforms
with
hybrid
architecture
capabilities
O P T IO N
# 2

12. A PPRENDA.COM
Leverage
CI/CD
tooling
and
platforms
with
hybrid
architecture
capabilities
O P T IO N
# 2

13. A PPRENDA.COM
Let’s
Look
at
this
Option
via
an
UrbanCode
Demo

14. A PPRENDA.COM
Hybrid
Application
and
Team
Structure
APPR E ND A
D E PLOYME NT
• Back
end
.NET
API
service
used
by
multiple
applications
• Customer
and
inventory
data
in
SQL
Server
• Leverages
Apprenda REST
APIs
K UB E R NE TES
D E PLOYME NT
• Front
end
(UI)
Flask
application
• Services
integration
• Leverages
Kubernetes API
• Connects
to
Apprenda .NET
back
end
UrbanCode
Application
Apprenda
Components Kubernetes
Components
DEV
TEAM
#1
(.NET) DEV
TEAM
#2
(PYTHON)

15. A PPRENDA.COM
App
Architecture
for
the
Demo
Google
Service
Google
Service
eCommerce Frontend
.NET
Web
API
Sales
Portal
Databases
Enterprise
Add-­‐ons
Additional
Upstream
and
Downstream
Enterprise
Applications
and
Services
(via
REST)
(via
REST)
.py flask
Microsoft
.NET

16. A PPRENDA.COM
What’s
Missing?
• Sturdiness
– Orchestration
is
“task
driven”
and
not
inherent
• Safe
– No
policy
enforcement
(security,
runtime
expectations)
• Deterministic
dependency
behavior
– Big
&
slow
vs
fast
and
small
• Dynamic
runtime
change
– Lack
of
ability
to
react
to
operating
context
• Easy
data
access
– Lack
of
ability
to
readily
access
state
data

17. A PPRENDA.COM
Leverage
a
platform
that
understands
the
mechanics
of
“mixed
era”
apps
O P T IO N
# 3

18. A PPRENDA.COM
O P T IO N
# 3
Leverage
a
platform
that
understands
the
mechanics
of
“mixed
era”
apps

19. A PPRENDA.COM
Kubernetes
as
Part
of
a
Mixed
Mode
Architecture

20. A PPRENDA.COM
Why
Kubernetes?
TECH
10
years
of
Google
R&D
in
container
orchestration
COMMUNITY
Cannot
buy
network
effect
Largest
community
Not
built
for
single
vendor
MARKET
Most
Fortune
500
Wins
search
volume
Growing
vendors

21. A PPRENDA.COM
Understanding
Apprenda
ü Platform
for
cloud
native
(via
docker)
and existing
apps
ü Excels
at
“heavy,
non-­‐volatile”
app
servers
like
JBoss,
WebSphere,
IIS
ü Strong
Windows
support
(.NET,
Windows
Services,
etc.)
ü Scheduler
understands
“warm
&
waiting”
servers
that
receive
workloads

22. A PPRENDA.COM
Allow
trivial
co-­‐habitation
and
composition
of
“mixed
era”
applications
Goal
End
State

23. A PPRENDA.COM
Apprenda Scheduler
Policy
Context
NodeNV
Node
(Apprenda Native)
Kubelet
Pod Pod
Proxy
Container Container
Container
Manager
“Hot”
Managed
Server
Instance
App
1
Instance
App
n
Instance
Dependency
Manager
(Bindings
&
Runtime)
Decomposer K8S
SchedulerMapper
Service
Catalog
&
ProxyShared
Base
Services
Apprenda Archive
INJ ECTIONS INJ ECTIONS

24. A PPRENDA.COM
Community
Participation
• Simplifying
post-­‐compile
extensibility
of
Kubernetes
• Windows
support
• Enterprise
readiness
• Integrations
with
popular
enterprise
subsystems

25. Questions?