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.

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

3. legacy systems
successful
enough to last this long

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

5. 94% OF COMPANIES ARE
ON THE CLOUD

6. CLOUD DATA CENTERS WILL PROCESS 94% OF
WORKLOADS IN 2021

7. 89% OF COMPANIES USE
SAAS

8. THE REVENUE FROM SAAS IS EXPECTED TO
REACH $85.1 BILLION IN 2019

9. 75% OF ALL CLOUD WORKLOADS AND
COMPUTE INSTANCES WILL BE SAAS BY 2021
HOW CAN WE ACHIEVE SAAS IN A SCALABLE
AND RELIABLE WAY?

10. SERVERLESS
MICROSERVICES

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

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

19. PRICE, EXECUTION TIME, TECHNOLOGY
STACK, CONFIGURATION & SETUP,
ENVIRONMENT, SCALING

20. 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
MICROSERVICES
Operating
system
Maintenance and
support
Monitoring of
the OS
Deployment
mechanism
App
Deployment
&
Configuration
Infrastructure
management
SERVERLESS

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

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

44. POWER FLOWER – “EUREKA!!!”

45. FLAVORS

53. Hybrid App
Microservices Serverless
Proxy
Emit Request

54. CONTAINERIZED INSIDE K8S

56. Hybrid App
Microservices Serverless
Proxy
Emit Request

57. Hybrid App
Microservices Serverless
Proxy
Emit Request

58. Hybrid App
Serverless Serverless
Proxy
Emit Request

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

61. How to connect multiple functions to
fulfil a business requirement

62. Set of functions to be seen as individual
projects with their own team, pipeline
and lifetime

63. Middleware and internal communication
vs speed and performance

64. 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…

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