Microservices and Containers in the Middleware World

Transcription

1 Microservices and Containers in the Middleware World April 2016 JPoint Moscow, Russia Kai Wähner Technology Evangelist LinkedIn /

2 Key Takeaways A cloud-native architecture enables flexible and agile development Modern middleware leverages containers and Microservices Just using Jenkins and Docker is not enough

3 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

4 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

5 The Digital Transformation cannot be stopped!

6 Evolving Demands from the Business AGILITY & SPEED WEB SCALE REDUCED CYCLE TIMES FAIL FAST LOWER COST

7 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

8 Middleware Middleware is computer software that provides services to software applications beyond those available from the operating system. It can be described as "software glue. Middleware makes it easier for software developers to implement communication and input/output, so they can focus on the specific purpose of their application. ( Wikipedia

9 Middleware - Buzzwords Keywords PAST: Application Integration, EAI, Broker, Process, Application, Integration, Enterprise, Hub and Spoke, Backbone, Scalability, Platform, Batch Keywords PRESENT: Service Integration, Bus, SOA, BPM, Service, ESB, Flexibility, Distribution, Events, EDA, Real Time, Event Correlation, Open, Standards, Extensibility Keywords FUTURE: Integration of Everything, Gateway, ibpms, Cloud, IoT, Microservice, API, Continuous Delivery, Self-Service, Prediction

10 Middleware The Double Burden?... ESB frameworks are generally characterized as heavyweight complex, centralized and difficult... Electronic Services: Concepts, Methodologies, Tools and Applications, Information - Science Reference (15. Juli 2010)

11 Middleware Example: Enterprise Service Bus (ESB) An enterprise service bus (ESB) is a software architecture model used for designing and implementing communication between mutually interacting software applications in a serviceoriented architecture (SOA). Its primary use is in enterprise application integration (EAI) of heterogeneous and complex landscapes. (Wikipedia, 2016)

12 Is the ESB dead? #NoESB Akana (former SOA Software) Gartner

13 Definition of the Term ESB in 2016 What to use an ESB for? Integration, orchestration, choreography, routing, (some kinds of) event processing / correlation / business activity monitoring Legacy Integration (e.g. with a powerful SAP or Mainframe connector) API and REST integration and business services Messaging (WebSockets, MQTT, AMQP, ) Internet of Things Deploy these services independently from each other with a standardized interface to a scalable runtime platform; automatically.

14 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

15 Microservices Suite of small services running in its own process Communication via lightweight mechanisms Built around business capabilities Independently deployable, written in different languages and using different data stores Bare minimum of centralized management Shorter time to results and increased flexibility

16 Various Forms of Microservices API Gateway Integration Service Integration Service SaaS Service BPM Service Service Service Service Service Monolith application SOA

17 How to deploy independent Microservices? == The Momentum of Containers Garden / Warden

18 Why Containers?

19 Build, Ship, and Run Any App, Anywhere andersjanmyr/ docker-the-future-of-devops

20 An Open Standard for Containers...

21 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

22 Cloud Native enables... scalable services resiliency automatic load balancing and failover DevOps usage public cloud platforms, but also private or hybrid vendor-agnostic deployment focus on business problems

23 Cloud-Native Architecture Microservices and Containers are just the Foundation!

24 Requirements for a Cloud-Native Architecture Microservices and Containers [as discussed ] Continuous Integration and Continuous Delivery Scripting / Automatic Test and Deployment Service Discovery Dynamic Distributed Configuration Management Scalability and Failover Cluster Management (Scheduling and Orchestration) Load Balancing (Server-side and Client-side) Cloud Native Platform Self-Service Agile Infrastructure Private / Public / Hybrid PaaS

25 Continuous Integration and Continuous Delivery Scripting / Automatic Test and Deployment BENEFITS Accelerated Time to Market Building the Right Product Improved Productivity and Efficiency Reliable Releases Improved Product Quality Improved Customer Satisfaction Build Management Ant, Maven, Gradle, Continuous Integration Jenkins, Bamboo, Continuous Delivery Chef, Puppet, Salt,

26 Continuous Integration and Continuous Delivery Internal Service Discovery for a Scalable Runtime Service Registry Eureka Apache Zookeeper Consul Etcd Cluster Frameworks with implicit Service Registry Kubernetes Mesos Marathon Amazon AWS ELB PaaS Cloud Platforms reusing an existing Service Registry Pivotal Cloud Foundry is based on Eureka

27 Continuous Integration and Continuous Delivery External Service Discovery for an Open API Examples for API Management: JBoss apiman, Apigee, Akana, TIBCO Mashery, Layer7

28 Continuous Integration and Continuous Delivery Dynamic Distributed Configuration Management Features Effect changes dynamically at runtime Change multi-dimensional properties based on a complex request or deployment context Use Cases Enable / disable features based on request context Change UI presentation logic Override behaviors of patterns (e.g. Circuit Breaker) Change log level after observing issues in a service Examples Netflix Archaius, Spring Cloud Config

29 Scalability and Failover Cluster Management (Scheduling and Orchestration) Features Orchestrate the combination of container scheduling and managing hosts Select relevant hosts (applying rules and constraints) Load containers onto the specific hosts Start, stop, and manage the life cycle of the process Designed to be fault-tolerant and scalable Examples Swarm (Docker-native) Fleet (CoreOS low-level framework) Kubernetes (open source d by Google) Adopted by others (IBM, Red Hat, Microsoft ) Mesos Marathon (most powerful and complex) For large scale; multi-use (e.g. Containers, Hadoop)

30 Scalability and Failover Server-side and Client-side Load Balancing (LB) Features Distributes network or application traffic across a number of servers Used to increase capacity (concurrent users) and reliability of applications Server-Side External Load Balancing ( Edge Services ) Client-Side Internal Load Balancing ( Mid-Tier Services ) Why also Client-Side LB? Inter-Service-Communication (1 hop instead of 2 hops) Implicit LB, no need for an external LB Traditional LB with IP addresses and host names not sufficient Registering and de-registering servers with load balancer on the fly No restrictions on the protocol or method of communication Examples F5 internal / DMZ, server-side Netflix Ribbon internal / within cloud platform, client-side AWS ELB (Elastic Load Balancer) public cloud, server-side

31 Cloud Native Architecture What Cloud Native Solutions are available?

32 Cloud Native Platform (Infrastructure-as-a-Service) IaaS Choose your IaaS Servers Storage Private or Hybrid Cloud Network Reduced costs of Infra Self-hosted & Controlled Env

33 Cloud Native Platform (Platform-as-a-Service) Choose your PaaS / Container Cloud-Native App Dev OS & Containers Scalability Self-service agile infrastructure Routing Logging / Monitoring Elasticity & Scalability PaaS

34 Cloud Native Platform IaaS Servers Storage Network Choose your IaaS Choose your PaaS / Container Private or Hybrid Cloud Cloud-Native App Dev Reduced costs of Infra Self-service agile infrastructure Self-hosted & Controlled Env Elasticity & Scalability OS & Containers Scalability Routing Logging / Monitoring PaaS

35 PaaS Platforms on top of IaaS in 2016 What container and PaaS tools are used to manage OpenStack applications? OpenStack Survey, April 2016:

36 Cloud Foundry

37 Kubernetes (K8S)

38 Kubernetes on Google Cloud Platform

39 Apache Mesos

40 SaaS The Other Cloud Native Alternative you have no control! You just use the service!

41 Container-as-a-Service Containers as a service (CaaS) is a form of container-based virtualization in which container engines, orchestration and the underlying compute resources are delivered to users as a service from a cloud provider. The basic resource for CaaS is a container, rather than a virtual machine (VM) or a bare metal hardware host system

42 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

43 Microservices and Containers in the Middleware World Some Middleware examples Integration Services / APIs, Integration, Orchestration API Management Publish and Monetize Microservices (internal, partner, public) Log Management Monitor distributed Microservices in a central way Event Processing Correlation of Microservices events in real time All the above Middleware components control and leverage other Microservices have to support Microservice characteristics itself (Containers, CI / CD, Elastic Scalability, etc.) to fit into a cloud-native architecture

44 Integration PaaS PaaS Integration Platform Omnichannel client apps Integration Apps & Services Build consumable Web APIs out of backend web services like SOAP, SAP, Oracle, IBM MQ, etc. API Choreography Microservices Microservices Microservices (Node/Java/Python) (Node/Java/Python) (Node/Java/Python) Functional Microservices Functional Microservices Build focused business functionality-oriented apps without getting into code complexity Integration Apps & Services ESB & Common Services API Choreography Visually choreograph APIs leveraging the PaaS Integration Tooling (e.g. data mapper, connectors) Backend Legacy Apps

45 SaaS Integration Solution Web-based Integration Edge-Services Citizen Developer

46 API Creation API Packaging and Distribution API Management API Management PORTAL ANALYTICS API PACKAGER TRAFFIC MANAGEMENT SECURITY APIs API Gateway ADVANCED SECURITY TRAFFIC MANAGEMENT TRANSFORM

47 Sensors Application Logs Transactions Monitoring Configuration Messaging Data Discovery Streaming Analytics Log Management WEB UI WS API Analysis Tools Operational Intelligence Platform Centralize and Store of Record Search, Auto-id, OOTB Parsing, Correlation Forensics and Alerts Reports

48 Event Processing Temporal analytic: If vibration spike is followed by temp spike then voltage spike [within 12 minutes] then flag high severity alert. Voltage Temperature Vibration Correlation of Microservice Events in Real Time Device history

49 Agenda 1) Digital Transformation 2) Middleware 3) Microservices and Containers 4) A Cloud-Native Architecture 5) Cloud Native Middleware 6) Live Demo

50 Cloud Native Architecture for the Live Demo Partner App.com Web App Android App iphone App ROUTER HEALTH MGR LOGGING CONTROLLER NATS SVC BROKER SaaS Gateway App Gateway App BW CE App BW CE App MongoDB PaaS BW CE App Node App Spring App Java App Cloud Foundry Legacy TIBCO ESB eftl EMS BW6

51 Live Demo Cloud-Native Microservices with Pivotal Cloud Foundry, Docker, Kubernetes, TIBCO BusinessWorks Container Edition, TIBCO Mashery and Papertrail Cloud (PaaS, Microservices, Container) IDE (REST, APIs, Integration) Administration (Deployment, Versioning) Operations (Failover, Scalability, Log Management) Log Management (Distributed Search and Correlation) Open API (Packaging, External Discovery)

52 Key Takeaways A cloud-native architecture enables flexible and agile development Modern middleware leverages containers and Microservices Just using Jenkins and Docker is not enough

53 Questions? Kai LinkedIn / Xing Please connect!