AzureConf 2014 - Azure hybrid connections (Sam Vanhoutte)

The document discusses various service mesh options including Linkerd, Consul Connect, Istio, and AWS App Mesh. It provides an overview of each solution, describing their key features and strengths/opportunities. It emphasizes that the service mesh approach is useful for managing inter-service communication and that implementations are still evolving. It recommends starting simply and iteratively adopting capabilities to match needs.

WSO2 Integration Platform allows users to integrate with on-premise as well as cloud based systems. It provides deployment options on cloud, on-premise or as a hybrid deployment.

Multisite DirectAccess allows administrators to place servers in multiple physical locations to reduce crucial single points of failure in their DirectAccess architecture. When multisite DirectAccess is configured, Windows 8.x/10 clients are aware of all deployed entry points in the organization and will automatically select the entry point closest to them. The native site selection process is very basic and often yields unexpected results.

In this talk we share our experience @ Sixt of building a highly secure and PCI-DSS Level 1 compliant environment on top of AWS.

Presentation in IBM Cloud Meet-up of Toronto https://www.meetup.com/IBM-Cloud-Toronto/events/253903913/?_xtd=gatlbWFpbF9jbGlja9oAJGU3NmM3ZjdmLWE2NzgtNGVlNC1iNGZiLTBlZGE5ZWM0NDZjOQ

At the Linux Foundation's 2018 Open Source Networking Days, Syed Ahmed compared service mesh options (Istio, Linkerd, and Consul Connect) and spoke about how they diverge from many complications traditionally found in monolithic applications.

Modern application architectures are embracing public clouds, microservices, and container schedulers like Kubernetes and Nomad. These bring complex service-to-service communication patterns, increased scale, dynamic IP addresses, ephemeral infrastructure, and higher failure rates. These changes require a new approach for service discovery, configuration, and segmentation. Service discovery enables services to find and communicate with each other. Service configuration allows us to dynamically configure applications at runtime. Service segmentations lets us secure our microservices architectures by limiting access. In this talk, we cover these challenges and how to solve them with Consul providing as a service mesh.

Distributed applications like microservices shift some of their complexities into the interaction of services. Such a service mesh, which can have hundreds of runtime instances, is very difficult to manage. You will be concerned with some of the following questions: Which service will be requested by which other services in which version and how often depending on the request content? How can you test the interaction and how can you replace single services with new ones? These and other questions will be discussed in this session. Tools to make your live easier with a service mesh will also be introduced.

In this talk we discuss key architecture patterns for designing authentication and authorization solutions in complex microservices environments. We focus on the key advantages and capabilities of AWS Cognito User Pools and Federated Identities and explore how this service can address the challenges of implementing client to service, service to service and service to infrastructure auth. In addition, we discuss patterns and best practices around building a highly available and resilient decentralised authorization solution in a microservices environment based on fine-grained permissions and end to end automation.

Distributed microservices introduce new challenges: failure modes are harder to anticipate and resolve. In this session, we present a “Chaos Debugging” framework enabled by three open source projects: Gloo Shot, Squash, and Loop to help you increase your microservices’ “immunity” to issues. Gloo Shot integrates with any service mesh to implement advanced, realistic chaos experiments. Squash connects powerful and mature debuggers (gdb, dlv, java debugging) to your microservices while they run in Kubernetes. Loop extends the capability of your service mesh to observe your application and record full transactions for sandboxed replay and debugging. Come to this demo-heavy talk to see how together, Squash, Gloo Shot, and Loop allow you to trigger, replay, and investigate failure modes of your microservices in a language agnostic and efficient manner without requiring any changes to your code.

If you have an existing Java monolith, you know you must take care making changes to it or altering it in any negative way. Often times these monoliths are very valuable to the business and generate a lot of revenue. At the same time, since it’s difficult to make changes to the monolith it’s desirable to move to a microservices architecture. Unfortunately you cannot just do a big-bang migration to a greenfield architecture and will have to incrementally adopt microservices. In this talk, we’ll look at using Gloo proxy which is based on Envoy Proxy and GraphQL to do surgical, function-level traffic control and API aggregation to safely migrate your monolith to microservices and serverless functions.

Service mesh abstracts the network from developers to solve three main pain points: How do services communicate securely with one another How can services implement network resilience When things go wrong, can we identify what and why Service mesh implementations usually follow a similar architecture: traffic flows through control points between services (usually service proxies deployed as sidecar processes) while an out-of-band set of nodes is responsible for defining the behavior and management of the control points. This loosely breaks out into an architecture of a "data plane" through which requests flow and a "control plane" for managing a service mesh. Different service mesh implementations use different data planes depending on their use cases and familiarity with particular technology. The control plane implementations vary between service-mesh implementations as well. In this talk, we'll take a look at three different control plane implementations with Istio, Linkerd and Consul, their strengths, and their specific tradeoffs to see how they chose to solve each of the three pain points from above. We can use this information to make choices about a service mesh or to inform our journey if we choose to build a control plane ourselves.

This document discusses various Azure integration patterns for connecting on-premises systems and data to the cloud. It outlines networking options like virtual networking and ExpressRoute. It also covers data integration using Azure Storage and SQL Database/Data Sync. Application integration techniques like Service Bus, BizTalk Services, and hybrid connections are presented. Examples are given for different scenarios around synchronizing data, connecting applications, and moving integration solutions to the cloud.

The document discusses various integration solution patterns including enterprise integration patterns (EIPs), implementation of EIPs using WSO2 Enterprise Service Bus (ESB), and high-level integration patterns like API gateway, service broker, and dual channeling. It describes how functional components of WSO2 ESB like mediators and sequences can be used to implement EIPs. Overall it provides an overview of best practices, approaches and strategies for designing integration solutions using patterns.

In a world of disaggregated API-based architectures, developers are increasingly adopting microservices — and Service Mesh is being used to control many service-to-service communications. But Service Mesh is not addressing the concern of how the exploding number of APIs can be exposed in a controlled and secure manner to their API consumers. In this meetup, we will discuss how to augment service mesh functionality with API management capabilities, so you can create an end-to-end solution for your entire business functionality — from microservices to APIs, to end-user applications.

Consul is a Service Networking tool designed to connect applications and services across a multi-cloud world. With Consul, organizations can manage service discovery and health monitoring, automate their middleware and leverage service mesh to connect virtual machine environments and Kubernetes clusters.

In this presentation, Łukasz explains what exactly API Gateway is and debates about many problems that it actually can solve. He uses AWS API Gateway as an example.

by Sam Vanhoutte In the new scenarios where cloud is getting used, integration becomes very important. Luckily, the Windows Azure platform provides a lot of different capabilities and services to make a secure link between your local systems and the Windows Azure services or machines. In this session, an overview will be give of the different technologies and the scenarios to which these technologies are best applicable. The following technologies will be demonstrated and discussed: •Messaging: Service Bus Messaging, BizTalk Services •Services: Service Bus Relay •Mobile: Service Bus Notification Hubs, SignalR •Data: SQL Data Sync •Networking: Windows Azure Virtual Networking •Security: Active Directory integration

This document discusses options for integrating on-premises systems with Azure-based applications. It describes network-based options like virtual networks and non-network options like Azure Relay and the On-Premises Data Gateway. Azure Relay offers WCF Relay and Hybrid Connections. Hybrid Connections use port forwarding while WCF Relay relies on WCF. The document also provides examples of how to connect web/mobile apps, VMs, and SaaS services to on-prem resources and compares different approaches.

Organisations are increasingly becoming aware of the immense power afforded by hybrid application architectures. Enterprise businesses can now leverage the scale, elasticity, economy and global reach afforded by Microsoft Azure whilst still retaining the investment and security of their on-premises LOB systems, helping them to maintain a competitive edge in a world where businesses are no longer constrained by geographic boundaries. Yet with so many options available for connecting systems, which one should you choose? In this session we will discuss the various Microsoft offerings for hybrid connectivity including Hybrid Connections, the On-Premises Data Gateway, Virtual Private Network, Service Bus WCF Relay and the new Azure Relay – and when best to use which.

This document provides an overview of Microsoft Azure services for enabling digital enterprises, including Hybrid Connections which allow applications running on Azure to securely access on-premises resources. It describes how Hybrid Connections work and their pricing tiers. A variety of Azure services and connectors that can be used with Hybrid Connections are also listed such as Web Apps, Mobile Services, BizTalk Services, and API connectors.

Slide deck related to 15 Factor App. Covers all the aspects related to Cloud Native application development using 15 Factor App methodology.

The document announces an Azure event in Toronto from May 5-7th that Microsoft is sponsoring. It provides information about accessing Microsoft documentation and training resources. It also introduces the speaker, Callon Campbell, who is a Microsoft MVP in Azure and consultant specializing in app migration, modernization and Azure. The agenda covers what serverless means, demos of building serverless APIs with Azure Functions and API Management, and hosting Function apps.

Using Cisco Jabber Guest, organizations can connect with customers or other public users (guests) through their website or mobile application using instant-on, real-time voice and video. Guests in queue can watch videos about products and then talk with subject-matter experts. They can see shared content, ask questions and get them answered in real time. And they can do so from the device they prefer - tablet, computer, or smart phone. As a developer, you can create custom experiences using Jabber Guest within a Web app on Windows and Mac or a mobile app on iOS and Android. In this session you'll learn how simple, straightforward, and welcoming the integration can be … for both the developer / organization implementing Jabber Guest integration, and for the guests themselves.

This document discusses drivers and barriers to cloud migration as well as common issues organizations face. It proposes that F5 and VMware solutions can help by automating network changes, enabling live application migration between data centers, and providing a hybrid cloud architecture. F5 solutions such as BIG-IP can optimize performance, maximize availability, simplify management, and accelerate desktop virtualization deployments. The plug-in for VMware vSphere aims to simplify management by integrating F5 solutions directly into the vSphere client user interface.

Cloud Services spur enterprises to seize new opportunities. This presentation from #vForum highlights common use cases accelerating the adoption of vCloud Air across companies.

This document outlines an agenda for a .NET cloud-native bootcamp. The bootcamp will introduce practices, platforms and tools for building modern .NET applications, including microservices, Cloud Foundry, and cloud-native .NET technologies and patterns. The agenda includes sessions on microservices, Cloud Foundry, hands-on exercises, and a wrap up. Break times are scheduled between sessions.