This session prepares us for tomorrow problems and needs by trying to present a world where serverless can coexist with microservices and even traditional systems. We discover an architecture approach that can solve today problems with tomorrow technologies – in the end; it is a tradeoff that we need to make to resolve current business problems in a limited period with a realistic budget.

1. A hybrid approach of
the Serverless world
Radu Vunvulea
@RaduVunvulea

2. GOLD
SILVER
PARTNERS
PLATINUM
POWERED BY

3. legacy systems
successful
enough to last this long

4. Dreamer, Technology Enthusiast, Speaker, Trainer, People 1st, Microsoft Azure MVP, Crafter, Endava, Dreamer

10. Loosely coupled
Deployable
independently
High maintainable
and testable
Organized on top
of business needs
and capabilities

14. Writing a function that incorporates a business logic and deploy it
Event triggered Ephemeral
No infrastructure
to manage
Pays per
execution

15. Operating system
Maintenance and support
(e.g. operation system updates,
security patches)
Monitoring of the OS
Deployment mechanism
App Deployment & Configuration
Infrastructure management
K8 Cluster

16. Operating system
Maintenance and support
(e.g. operation system updates,
security patches)
Monitoring of the OS
Deployment mechanism
App Deployment & Configuration
Infrastructure management
Need to use external
services to be able to deliver
the same functionality
Overcome the limitations of disk
space, RAM and execution
duration
Legacy dependencies to different
stacks or systems

25. Response time Throughput
Resource
utilization
Workload Availability Scalability
Security Maintenability Interoparability

31. Value proposition:
“REAL TIME STOCK”
B2C & B2B

40. Power Flower – “Eureka!!!”

41. Flavors

49. Hybrid App
Microservices Serverless
Proxy
Emit Request

50. containerized
inside K8s

52. Hybrid App
ServerlessMicroservices
Proxy
Emit Request

54. Hybrid App
Microservices Serverless
Proxy
Emit Request

55. Hybrid App
Microservices Serverless
Proxy
Emit Request

56. Hybrid App
Serverless Serverless
Proxy
Emit Request

59. Until then (now) we need to
understand how…

60. Understand how to connect multiple
functions to fulfil a business
requirement

61. Collection of functions shall be seen
as individual projects with their own
team, pipeline and lifetime

62. Middleware and internal
communication vs speed and
performance

63. To sum up

64. To sum up

65. To sum up
In how many s|f shall I divide
the business capabilities?
Data partitioning across s|f?
How much should I
replicate/local redundancy?
How should sync data across
s|f for local redundancy?
Data consistency? Strong vs
eventual consistency
Technologies and tools for s|f
Cost control vs NFRs (Security,
Reliability, Performance, and
Efficiency)
Code sharing (NPM) and
versioning
Process and teams setup
around s|f blocks
Select right interface,
middleware and channel for
communication…

67. Thank you!
@RaduVunvulea
vunvulearadu.blogspot.com
https://www.linkedin.com/in/raduvunvulea/
vunvulear@outlook.com