MuCon 2015 - Microservices in Integration Architecture

This document provides an introduction to microservices architecture. It discusses why companies adopt the microservices style, how to design microservices, common patterns, and examples from Netflix. The key points are: 1) Microservices architecture breaks applications into small, independent services that communicate over well-defined interfaces. This improves modularity, scalability, and allows independent deployments. 2) When designing microservices, services should be organized around business capabilities, have decentralized governance and data, and be designed to fail independently through patterns like circuit breakers. 3) Netflix is a leader in microservices and has open sourced many tools like Hystrix for latency handling and Eureka for service discovery that

Microservice architecture. Short intro into the world of microservices, the talk I gave in VilniusPHP meetup.

This document provides an introduction to Apache ActiveMQ. It discusses how ActiveMQ is a Java Message Service (JMS) and message-oriented middleware that provides asynchronous messaging. It supports cross-language clients and features high performance clustering of brokers for scalability and master-slave configurations for persistence and reliability. The document uses an example of sending a "Hello World" message to demonstrate basic usage of ActiveMQ.

This presentation outlines the benefits of implementing a Microservice over a monolithic architecture.

The ownership boundary of the typical enterprise now encompasses a much broader IT landscape. It is common to see that landscape stretch out to cloud native development platforms, software as a service, dependencies on external APIs from business partners, a mobile workforce and an ever growing range of digital channels. The integration surface area is dramatically increased and the integration patterns to support it are evolving just as quickly. These are the challenges we recognise as "hybrid integration". We will explore what a reference architecture for hybrid integration might look like, and how IBM's integration portfolio is growing and changing to meet the needs of digital transformation. This deck comes from the following article http://ibm.biz/HybridIntRefArch and is also described in this video http://ibm.biz/HybridIntRefArchYouTube

This document provides an overview of API gateways and their role in microservice architectures. It begins with a brief history of monolithic architectures and how microservices emerged as a solution. It then defines key concepts like APIs, gateways, and how they relate. The main points are: 1) An API gateway acts as a single entry point and centralizes request routing, protocol translation, and provides cross-cutting features like authentication, monitoring and security for internal microservices. 2) Gateways help reduce complexity and overhead by encapsulating microservices and allowing transformations, while also improving reusability and security. 3) Examples of API gateway tools are provided, as well as a proposed activity, before concluding

This document provides an overview of microservice architecture using CQRS (Command Query Responsibility Segregation) and Event Sourcing patterns. It defines CQRS as separating the write and read functions of an application. Event Sourcing records all state changes as a series of events rather than just the current state. The benefits include scalability, simplicity, flexibility and a business focus. Popular companies using this architecture include those needing cost-effective scaling like microservices. The author provides resources and advocates for CQRS and Event Sourcing to solve common architectural challenges.

Comparing Service-Oriented Architecture (SOA), Microservices and Service-Based Architecture (SBA - SOA and Microservices Hybrid) patterns. Also discussing coupling and cohesion concepts in relation to the systems design.

The microservice architecture is growing in popularity. It is an architectural style that structures an application as a set of loosely coupled services that are organized around business capabilities. Its goal is to enable the continuous delivery of large, complex applications. However, the microservice architecture is not a silver bullet and it has some significant drawbacks. The goal of the microservices pattern language is to enable software developers to apply the microservice architecture effectively. It is a collection of patterns that solve architecture, design, development and operational problems. In this talk, I’ll provide an overview of the microservice architecture and describe the motivations for the pattern language. You will learn about the key patterns in the pattern language.

1) Event-driven microservices involve microservices communicating primarily through events published to an event backbone. This loosely couples microservices and allows for eventual data consistency. 2) Apache Kafka is an open-source streaming platform that can be used to build an event backbone, allowing microservices to reliably publish and subscribe to events. It supports streaming, storage, and processing of event data. 3) Common patterns for event-driven microservices include database per service for independent data ownership, sagas for coordinated multi-step processes, event sourcing to capture all state changes, and CQRS to separate reads from writes.

Should you choose a microservices architecture over a monolith? What are the pros and cons in reality.

Microservices architectures are changing the way that organizations build their applications and infrastructure. Companies can now achieve new levels of scale and efficiency by disaggregating their large, monolithic applications into small, independent “micro services”, each of which perform different functions. In this session, we’ll introduce the concept of microservices, help you evaluate whether your organization is ready for microservices, and discuss methods for implementing these architectures. We’ll also cover topics such as using API gateways, enabling self-service infrastructure provisioning, and ways to manage your microservices.

Apache Kafka is a publish-subscribe messaging system that can be used to build a pub-sub model. It uses a log-structured approach where messages are appended sequentially to files. Messages are categorized into topics which are divided into partitions. Producers create and publish messages to topics, while consumers subscribe to topics and read messages. Brokers receive messages from producers and serve them to consumers. Kafka is scalable, supports multiple producers and consumers, retains messages on disk, and provides high performance even under heavy loads. To build a pub-sub model with Kafka, producers publish messages to topics and consumers subscribe to topics to receive messages.

A introduction to Microservices Architecture: definition, characterstics, framworks, success stories. It contains a demo about implementation of microservices with Spring Boot, Spring cloud an Eureka.

This is the video capture of the meetup described at https://www.meetup.com/lifemichael/events/287981390/ This video includes the two talks the meetup included. The first one is an introductory talk for the topic. The second one covers the SAGA design pattern.