This document discusses microservices architecture and digital transformation solutions using microservices. It begins with an overview of monolithic versus microservices application architectures, noting that microservices allow for small, independent teams and continuous delivery of new features through loose coupling and fine-grained scaling. Pub-sub is discussed as an asynchronous communication pattern well-suited for microservices. Finally, examples of enterprise applications and digital transformation solutions built using a microservices architecture with technologies like Kafka, C*, Kudu, and Spark are presented.

1. Emergent,
choreographed,
microservices …
FTW
Syed Affan Ahmed • 11-Oct-2019
@aintiha
Analog Excellence
Microservices using
the pub-sub pattern

2. About myself
PhD. in CS, from USC --- Underwater Sensor Networks
Associate Prof. and Director of SysNet Lab (FAST-ISB)
Director Engineering at PLUMgrid
Head of Engineering at AN10
Member National Steering Committee for NCBC
Heading the OpenStack Pakistan User group

3. Overview
- Monolithic vs Microservices
- Flavors of Microservice Arch.
- High Level Arch for Orion and
Digital Transformation Solution

4. Application Architectures:
Monolithic vs
Microservices

11. Monolithic Applications
Single code base/language
Single Team
Change cycles are coupled, long testing cycle => difficult for
CI/CD
Full application, coarse-grained scaling

12. Why the Microservices push?

13. Why the Microservices push?
Small teams, independent decisions, loosely coupled
Continuous delivery of new features
Fine grained scaling

14. Why the Microservices push?
Small teams, independent decisions, loosely coupled
Continuous delivery of new features
Fine grained scaling
Benefits

15. Why the Microservices push?
Small teams, independent decisions, loosely coupled
Continuous delivery of new features
Fine grained scaling
Benefits

16. Why the Microservices push?
Small teams, independent decisions, loosely coupled
Continuous delivery of new features
Fine grained scaling
Benefits

17. Why the Microservices push?
Small teams, independent decisions, loosely coupled
Continuous delivery of new features
Fine grained scaling
Benefits

18. The Flavors of
Microservice Architecture

19. How the interconnection is implemented!

20. Pub-Sub and Microservices
● Asynchronous model, no polling for information
● Streaming processing, naturally
● Scaling producer/consumers easy*
● Easily handles event spikes
● Program flow is an emergent behavior = choreography
* With certain messaging systems, like Kafka
Practically, a hybrid
model works best.

29. Order tracking

30. Microservices… and sliced bread!

31. Microservices… and sliced bread!

32. Microservices… and sliced bread!

34. Enterprise Applications
built using microservices

35. Application-Data decoupling
● Data storage and availability
decoupled from Application logic
● Protocol Adapters for interfacing
with INX or 3rd party devices

36. Scalability and Data Ingestion
C*, Kudu, Spark, and ELK:
Big Data Technologies
● Multi-node
● Cluster-based and scalable
● Fast visualizations
Kafka as messaging
Queue
● High performance ingestion
● Enable Micro-service
Architecture

37. Streaming Data Processing
Power of the platform through Streaming workers
Each worker has some “powers” , configured via rules
Result of worker output can be accessed via endpoints
Each worker, is built as a
microservice
Each microservice is a
platform feature

38. Digital Transformation
using WFE
Transforming Digital Operations
Executable WFE
Empowers C-level management
SOA architecture
https://www.linkedin.com/pulse/digital-transformation-journey-how-iot-becomes-ioe-affan-syed/

39. Ask away !!

40. Supplementary slides

41. Kafka based pub-sub

42. Consumer Groups for scaling