Event Bus as Backbone for Decoupled Microservice Choreography (Oracle Code, April 20th 2017, London, UK)

AMIS Oracle OpenWorld 2015 Review – part 3- PaaS Database, Integration, Identity Mgt, IT Ops and DevOps

This presentation (part of the year AMIS Oracle OpenWorld Review session) discusses the main themes for this year's conference and introduces the all encompassing cloud strategy. It highlights some major changes at Oracle Corporation. It lists the major announcements, the hot terminology and the product roadmaps.

The document provides an overview and review of Oracle's OpenWorld 2015 conference, focusing on Infrastructure as a Service offerings. Key topics covered include: Always-On Security in Silicon; Exadata Cloud Service; ExaLogic On-Premise Cloud Service; Compute Cloud Service; Storage Cloud; Oracle VM; Linux; Docker; WebLogic Server 12cR2; WebLogic Multitenancy; WebLogic Continuous Availability; Automated Elasticity for Dynamic Clusters; REST Management; and Coherence Federated Caching.

The Marketplace data team at Uber has built a scalable complex event processing platform to solve many challenging real-time data needs for various Uber products. This platform has been in production for more than a year and supports over 100 real-time data use cases with a team of 3. In this talk, we will share the detail of the design and our experience, and how we employ Siddhi, Kafka and Samza at scale.

Adoption of the cloud will not start with the core enterprise applications. There are several ways to start the adoption. One is to move in from training environments through development and test to production. Another takes the importance of applications into consideration, starting with secondary, supporting systems. The approach discussed in this session is to start with edge systems that are already in the DMZ, on the fringes of an enterprises, where they engage in interaction with the outside world. Systems on the edge of an enterprise have special challenges regarding availability, scalability, security and external interactions with systems or people. This applies for example to external portals, B2B interactions, workflows that involve external actors, mobile APIs and integrations with SaaS instances. These systems are obvious candidates to move to a public cloud - and handle these special requirements on the PaaS platform. This session discusses and demonstrates a number of Oracle PaaS Cloud Services, their mutual interaction and how they can be leveraged to move these systems over the edge and into the cloud: Java Cloud Service, Integration Cloud Service, Process Cloud Service, IoT CS, Mobile Cloud Service, SOA Suite Cloud Service and Message Cloud Service. We will go over a number of scenarios for moving edge systems from on premises to the public cloud. Essential in this discussion is of course the integration from the edge system in the Oracle Public Cloud to the on premises backend systems.

AMIS Oracle OpenWorld 2015 Review – part 4- PaaS Application Development, JavaOne, Mobile, Collaboration and SaaS and User Experience

Fast data arrives in real time and potentially high volume. Rapid processing, filtering and aggregation is required to ensure timely reaction and actual information in user interfaces. Doing so is a challenge, make this happen in a scalable and reliable fashion is even more interesting. This session introduces Apache Kafka as the scalable event bus that takes care of the events as they flow in and Kafka Streams and KSQL for the streaming analytics. Both Java and Node applications are demonstrated that interact with Kafka and leverage Server Sent Events and WebSocket channels to update the Web UI in real time. User activity performed by the audience in the Web UI is processed by the Kafka powered back end and results in live updates on all clients. This presentation includes a demonstration of remote database synchronization through Twitter.

Find out why hosting service providers choose Jelastic for their cloud business and what technologies they offer to the users based on this PaaS and CaaS solution.

Michel Schildmeijer gave a keynote at the Oracle Middleware Summit on January 9th, 2019. He discussed the history and evolution of Oracle Fusion Middleware from traditional middleware to more modern, cloud-native approaches. He outlined Oracle's focus on containers, Kubernetes, and microservices and how WebLogic and other FMW products are adapting to these trends, including new options like Helidon for developing microservices. Schildmeijer concluded that WebLogic will still be foundational but the focus is shifting to hybrid cloud-native solutions.

Alfresco DevCon 2018 (Lisbon) - https://devcon.alfresco.com/ Alfresco provides a rich set of options for integrating third-party systems with services across the Digital Business Platform. We will deep-dive into the architecture of the new Alfresco Integration Services framework – a set of event-driven micro-services that can be easily deployed & scaled. https://www.youtube.com/watch?v=TyB-t7wsDEE

This document provides an overview of Weblogic multitenancy including key concepts, components, isolation, consolidation benefits, portability for DevOps, and the Java Cloud Service. It discusses how multitenancy allows optimal use of resources by consolidating applications into partitions within a single Weblogic domain rather than separate domains. Isolation is achieved through mechanisms like dedicated JNDI trees and pluggable databases. Portability is enabled by exporting and importing partitions between environments. The Java Cloud Service supports Weblogic multitenancy with minimal Enterprise edition features.

Extreme performance with Oracle SOA Suite 12.2, Coherence and Exalogic can be achieved by configuring the platform to take advantage of the Exalogic infrastructure and optimizing SOA Suite and Coherence settings. Key aspects include using Coherence caching to minimize database transactions, configuring optimal WebLogic and JDBC settings for InfiniBand networking, and tuning SOA Suite dehydration and caching properties. This provides significant performance gains over a traditional architecture.

This document provides an overview of a presentation given at CamelOne 2013 in Boston on June 10-11, 2013 about the internals of Apache ActiveMQ. The presentation covered the major subcomponents of ActiveMQ including transports, the broker core, persistence adapters, and networking brokers. It provided details on architecture, configuration, and implementation of these different aspects of ActiveMQ.

The document discusses strategies for transitioning from monolithic architectures to microservice architectures. It outlines some of the challenges with maintaining large monolithic applications and reasons for modernizing, such as handling more data and needing faster changes. It then covers microservice design principles and best practices, including service decomposition, distributed systems strategies, and reactive design. Finally it introduces Lagom as a framework for building reactive microservices on the JVM and outlines its key components and development environment.

Containers are increasingly popular to package, ship and run applications or microservices with their completely configured runtime environment including platform components such as application server and data store.Continuous Delivery and automated DevOps hinge on containers. Docker Containers are widely used and Oracle has long been involved in the Docker community.This session introduces the Docker Container images published by Oracle for flagship products such as Database, WebLogic, Linux and Java and demonstrates how these can be used in environment provisioning, automated delivery pipelines and microservices architectures. The session shows how containers are built, shipped and run based on these images and shows the Oracle Container Cloud, as well as Wercker Cloud (for automated build and delivery pipelines) and Oracle Cloud Engine - the managed Kubernetes cloud service..

This document provides an overview of using Node.js for backend integration. It discusses how Node.js uses a single thread model with asynchronous and non-blocking I/O to provide high performance. Common Node.js frameworks like Express and Hapi are presented. The document also covers integrating Node.js with databases like Oracle NoSQL and MongoDB using modules like node-oracledb and mongoose. It provides examples of calling PL/SQL functions and using connection pooling with Node.js and Oracle Database. Finally, it introduces Application Container Cloud as providing capabilities beyond what Node.js alone offers like high availability, management, and support.

Find out what Jelastic is, where we are at the cloud market and what technical and business benefits we offer.

Microservices are independent, encapsulated entities that produce meaningful results and business functionality in tentative collaboration. Events and pub/sub are great for allowing such decoupled interaction. Using Apache Kafka as robust, distributed, real-time, high volume event bus, this session demonstrates how microservices packaged with Docker and implemented in Java, Node, Python and SQL collaborate unknowingly. The microservices respond to social (media) events - courtesy of IFTTT - and publish results to multiple channels. The event bus operates across cloud services and on premises platforms such as Kubernetes: both the bus and the microservices can run anywhere. A microservices platform is discussed with generic capabilities. The resources for the accompanying workshop are in GitHub: https://github.com/lucasjellema/workshop-event-bus-microservice-choreography-may-2018

IT needs to run in production in order to generate business value. DevOps is among other things a way of thinking focusing on production software. A business application requires a tailor made platform to generate business value. The combination of application and its platform is a DevOps product. The DevOps team has full responsibility for that product through its entire lifecycle. The microservices architecture promises flexibility, scalability, and optimal use of compute resources. Via independent components with well-defined scope and responsibility, interface, and ownership that are evolved and managed in an automated DevOps process, this architecture leverages current technologies and hard-learned insights from past decades. This session defines the objectives of Business with IT, of microservices and DevOps and introduces Containers and the container platform Kubernetes as crucial ingredients for making DevOps happen.

Nowadays "cloud" and "microservice" terms are used all the time, even overused. Does any system must be the "microservices" deployed in the "cloud"? Definitely not! However once you see that your system may benefit from that architecture, the next question is how to get there - how to fly to the clouds? Spring was always about simplifying the complicated aspects of your enterprise system. Netflix went to microservice architecture long before this term even was created. Both are very much contributed to open source software. How can you benefit from joint forces of the both?

Nowadays "cloud" and "microservice" terms are used all the time, even overused. Does any system must be the "microservices" deployed in the "cloud"? Definitely not! However once you see that your system may benefit from that architecture, the next question is how to get there - how to fly to the clouds? Spring was always about simplifying the complicated aspects of your enterprise system. Netflix went to microservice architecture long before this term even was created. Both are very much contributed to open source software. How can you benefit from joint forces of the both?

This document provides an overview of microservices in the enterprise. It discusses factors driving the rise of microservices like SOA fatigue and the need for faster innovation. Examples of microservice architectures from companies like Netflix, Twitter and Gilt are presented. Key capabilities for building enterprise-ready microservices are described, including service discovery, description, deployment isolation using containers, data/verb partitioning, lightweight middleware, API gateways and observability. Open source technologies that support implementing these capabilities are also outlined. The document concludes that microservices are the future of distributed systems and enterprises should implement solutions from first principles using inspiration from internet companies.

This document provides an introduction to microservices, including: - The benefits of microservices compared to monolithic architecture like independent deployability and scalability. - Microservices are small, independently deployable services that work together and are modeled around business domains. - Implementing microservices requires automation, high cohesion, loose coupling, and stable APIs. - Potential downsides include increased complexity in testing, monitoring, and operations. Microservices are best suited to problems of scale.

Presentation on Serverless and OpenWhisk at Haifa Cloud meetup, 7/2/2017 https://www.meetup.com/Haifa-Cloud/events/236843362/

Lino Telera gave a presentation on serverless computing. He began with introductions and background. The presentation covered serverless concepts like Function as a Service, demonstrated building a simple microservice using AWS Lambda that interacts with S3, and discussed integrating functions with services like S3 using Boto. It also showed how functions can be called from devices using skills and discussed running serverless on-premise using OpenFaaS or Pivotal Container Service. The presentation concluded with a Q&A and thanks to sponsors.

New architecture patterns are rapidly influencing many organizations. The march to the cloud is taking place. DevOps and microservices for true agility and containers as vehicle for delivery, testing and management. During Oracle OpenWorld 2017 - Oracle presented its vision and roadmap in the area of cloud native computing (which is based on container native) and announced its application server platform (container management runtime) of the future. This presentation summarizes that picture painted by Oracle.

“Microservices” have become a trendy development strategy. Hosting and running such services used to be pretty painful... but here comes Service Fabric! Let’s take a closer look at this platform, its different development models and all the features it offers, and not only for microservices!

This document summarizes a presentation about building microservices with WSO2 technologies. It introduces the microservices architecture and framework MSF4J, which allows developing microservices in Java using annotations. MSF4J provides high performance, metrics collection, and integration with Kubernetes for deployment. Hands-on examples are provided to demonstrate creating a sample stock quote microservice with MSF4J and deploying it to Kubernetes. The presentation also covers the WSO2 Application Server and its transition to being based on Tomcat rather than Carbon for improved performance and classloading.

The document outlines an infrastructure 2.0 approach based on cloud native technologies. It advocates for infrastructure as code, test-driven deployments, open source tools, and seamless developer workflows. The approach uses microservices, containers, service meshes, and orchestration with Kubernetes. It recommends tools like Terraform, Jenkins, Kubernetes, Istio, Prometheus, Elasticsearch and Airflow for infrastructure provisioning, CI/CD, container management, service mesh, monitoring, logging, and job scheduling. It also discusses Docker, data pipelines, and processes for onboarding new applications.

Microsoft AppFabric provides services for building and managing composite applications at scale, including workflows, caching, and hosting services. It allows sharing of data and workflows across machines. Windows Server AppFabric provides service and workflow management capabilities while Azure AppFabric focuses on access control and a service bus in the cloud. The presentation discussed architectural choices using these technologies like caching sessions, hosting services, and a real-world example architecture integrating caching, hosting, and messaging.

This document discusses building event-driven, fault-tolerant microservices. It begins by discussing lessons learned from SOA architecture and defining microservices. It emphasizes that microservices need to be reactive and message-driven to achieve loose coupling and fault tolerance. The document then outlines challenges in implementing microservices at scale before proposing a design using Spring Boot, Kafka, Docker, and Elastic Stack. It provides an in-depth look at these components and how they address scalability, isolation, fault tolerance and monitoring of microservices.

The document discusses converting a monolithic Node.js application into microservices and deploying them using Docker. It begins by defining microservices and their benefits. It then describes converting a sample pizza ordering application into independent microservices for handling messages, serving the frontend, and providing an API. Next, it covers patterns for networking microservices, including using an API gateway. It concludes by demonstrating how to deploy the microservices to Docker containers and use an orchestration tool like Kubernetes to manage them.

This document provides an agenda and overview of a workshop on microservices architecture. The agenda includes introductions to microservices architecture, WSO2 MSF4J, Kubernetes/Docker, and demonstrating MSF4J deployment with Kubernetes. It then discusses microservices architecture principles, inner and outer architecture, and the features and implementation of WSO2 MSF4J, a lightweight Java microservices framework. It covers developing microservices with MSF4J, deployment types, analytics and monitoring, security, and examples. The document concludes with discussions on production deployment with Kubernetes and Docker, and the current and future states of the WSO2 Application Server.