Service discovery in mesos
•
1 like•1,356 views
"Mesos uses zookeeper as service discovery but sometimes your applications don't support zookeeper for service discovery, or you need to run some legacy applications that you cannot modify the source, for that I research and test different systems for service discovery in Mesos/Marathon system. I will explain the problems and advantages of the different current solutions that I tested."
Report
Share
Report
Share
Download to read offline
Recommended
Consul: Microservice Enabling Microservices and Reactive Programming
Consul is a service discovery system that provides a microservice style interface to services, service topology and service health.
With service discovery you can look up services which are organized in the topology of your datacenters. Consul uses client agents and RAFT to provide a consistent view of services. Consul provides a consistent view of configuration as well also using RAFT. Consul provides a microservice interface to a replicated view of your service topology and its configuration. Consul can monitor and change services topology based on health of individual nodes.
Consul provides scalable distributed health checks. Consul only does minimal datacenter to datacenter communication so each datacenter has its own Consul cluster. Consul provides a domain model for managing topology of datacenters, server nodes, and services running on server nodes along with their configuration and current health status.
Consul is like combining the features of a DNS server plus Consistent Key/Value Store like etcd plus features of ZooKeeper for service discovery, and health monitoring like Nagios but all rolled up into a consistent system. Essentially, Consul is all the bits you need to have a coherent domain service model available to provide service discovery, health and replicated config, service topology and health status. Consul also provides a nice REST interface and Web UI to see your service topology and distributed service config.
Consul organizes your services in a Catalog called the Service Catalog and then provides a DNS and REST/HTTP/JSON interface to it.
To use Consul you start up an agent process. The Consul agent process is a long running daemon on every member of Consul cluster. The agent process can be run in server mode or client mode. Consul agent clients would run on every physical server or OS virtual machine (if that makes more sense). Client runs on server hosting services. The clients use gossip and RPC calls to stay in sync with Consul.
A client, consul agent running in client mode, forwards request to a server, consul agent running in server mode. Clients are mostly stateless. The client does LAN gossip to the server nodes to communicate changes.
A server, consul agent running in server mode, is like a client agent but with more tasks. The consul servers use the RAFT quorum mechanism to see who is the leader. The consul servers maintain cluster state like the Service Catalog. The leader manages a consistent view of config key/value pairs, and service health and topology. Consul servers also handle WAN gossip to other datacenters. Consul server nodes forwards queries to leader, and forward queries to other datacenters.
A Datacenter is fairly obvious. It is anything that allows for fast communication between nodes, with as few or no hops, little or no routing, and in short: high speed communication. This could be an Amazon EC2 availability zone, a networking environment like a subnet, or any private, low latency, high
Introduction to service discovery and self-organizing cluster orchestration. ...
Serf is a decentralized tool for service discovery, membership and failure detection that is lightweight and highly available. It can be used for use cases like clustering web servers and load balancers, clustering services like Memcached and Redis, triggering deployments, updating DNS records and providing simple observability. Consul is a service discovery and configuration tool that supports additional features like rich health checking, multi-datacenter support, key-value storage and requires centralized servers for coordination. Both tools emphasize treating infrastructure as code and easing scaling and recovery through service discovery.
Service Discovery in Distributed Systems
Service discovery allows services in distributed systems to find and connect with each other. Popular open-source service discovery solutions include ZooKeeper, Eureka, ETCD, and Consul. ZooKeeper uses consensus protocol ZAB for consistency but clients must handle load balancing. Eureka is eventually consistent and Netflix uses it for AWS. ETCD is inspired by ZooKeeper but clients also handle load balancing. Consul uses RAFT consensus and has a built-in DNS server, making it a comprehensive solution. The right service discovery solution depends on requirements like consistency needs and language integration.
Service discovery in a microservice architecture using consul
Presentation I gave at Nextbuild 2016. Gives an overview of how Consul can be used in microservice architecture. Accompanying examples and demo can be found here: https://github.com/josdirksen/next-build-consul
Consul and Consul Pusher
Consul is a tool that provides service discovery, configuration, and orchestration. It allows services to register themselves and discover other services via DNS or HTTP. Consul also supports health checking, multi-datacenter capabilities, and key-value storage. The core component is the Consul agent, which can run on every node in client or server mode. Servers are responsible for consensus and storing state while clients forward requests.
Service discovery with Eureka and Spring Cloud
The document discusses service discovery with Eureka and Spring Cloud. It introduces traditional applications where services have fixed locations versus modern applications where services are dynamic. It explains that service discovery with a service registry like Eureka allows services to find each other and load balance requests. The rest of the document demonstrates configuring Eureka as a service registry and client applications that can discover and consume services registered with Eureka.
Getting Started with Consul
This document provides an overview of getting started with Consul, including:
1. Consul is a tool for discovering and configuring services that is built on Golang and uses 3 basic ports for RPC, HTTP, and DNS.
2. It features service discovery, health checking, key/value storage, and multi-datacenter support.
3. Setup involves downloading the Consul binary, running the agent, and using commands like "consul members" and "consul join" to manage nodes.
Microservices with docker swarm and consul
This document discusses implementing microservices using Docker Swarm and Consul. It recommends programming languages and tools for orchestration, databases, load balancing, monitoring, and other functions. Docker Swarm allows clustering Docker hosts into a pool of resources. Consul provides service discovery, configuration, and failure detection across multiple datacenters. Consul-Template listens for Consul updates and configures applications. Registrator automatically registers and deregisters Docker services with Consul. An example scenario shows how services scale across nodes with this architecture.
Recommended
Consul: Microservice Enabling Microservices and Reactive Programming
Consul is a service discovery system that provides a microservice style interface to services, service topology and service health.
With service discovery you can look up services which are organized in the topology of your datacenters. Consul uses client agents and RAFT to provide a consistent view of services. Consul provides a consistent view of configuration as well also using RAFT. Consul provides a microservice interface to a replicated view of your service topology and its configuration. Consul can monitor and change services topology based on health of individual nodes.
Consul provides scalable distributed health checks. Consul only does minimal datacenter to datacenter communication so each datacenter has its own Consul cluster. Consul provides a domain model for managing topology of datacenters, server nodes, and services running on server nodes along with their configuration and current health status.
Consul is like combining the features of a DNS server plus Consistent Key/Value Store like etcd plus features of ZooKeeper for service discovery, and health monitoring like Nagios but all rolled up into a consistent system. Essentially, Consul is all the bits you need to have a coherent domain service model available to provide service discovery, health and replicated config, service topology and health status. Consul also provides a nice REST interface and Web UI to see your service topology and distributed service config.
Consul organizes your services in a Catalog called the Service Catalog and then provides a DNS and REST/HTTP/JSON interface to it.
To use Consul you start up an agent process. The Consul agent process is a long running daemon on every member of Consul cluster. The agent process can be run in server mode or client mode. Consul agent clients would run on every physical server or OS virtual machine (if that makes more sense). Client runs on server hosting services. The clients use gossip and RPC calls to stay in sync with Consul.
A client, consul agent running in client mode, forwards request to a server, consul agent running in server mode. Clients are mostly stateless. The client does LAN gossip to the server nodes to communicate changes.
A server, consul agent running in server mode, is like a client agent but with more tasks. The consul servers use the RAFT quorum mechanism to see who is the leader. The consul servers maintain cluster state like the Service Catalog. The leader manages a consistent view of config key/value pairs, and service health and topology. Consul servers also handle WAN gossip to other datacenters. Consul server nodes forwards queries to leader, and forward queries to other datacenters.
A Datacenter is fairly obvious. It is anything that allows for fast communication between nodes, with as few or no hops, little or no routing, and in short: high speed communication. This could be an Amazon EC2 availability zone, a networking environment like a subnet, or any private, low latency, high
Introduction to service discovery and self-organizing cluster orchestration. ...
Serf is a decentralized tool for service discovery, membership and failure detection that is lightweight and highly available. It can be used for use cases like clustering web servers and load balancers, clustering services like Memcached and Redis, triggering deployments, updating DNS records and providing simple observability. Consul is a service discovery and configuration tool that supports additional features like rich health checking, multi-datacenter support, key-value storage and requires centralized servers for coordination. Both tools emphasize treating infrastructure as code and easing scaling and recovery through service discovery.
Service Discovery in Distributed Systems
Service discovery allows services in distributed systems to find and connect with each other. Popular open-source service discovery solutions include ZooKeeper, Eureka, ETCD, and Consul. ZooKeeper uses consensus protocol ZAB for consistency but clients must handle load balancing. Eureka is eventually consistent and Netflix uses it for AWS. ETCD is inspired by ZooKeeper but clients also handle load balancing. Consul uses RAFT consensus and has a built-in DNS server, making it a comprehensive solution. The right service discovery solution depends on requirements like consistency needs and language integration.
Service discovery in a microservice architecture using consul
Presentation I gave at Nextbuild 2016. Gives an overview of how Consul can be used in microservice architecture. Accompanying examples and demo can be found here: https://github.com/josdirksen/next-build-consul
Consul and Consul Pusher
Consul is a tool that provides service discovery, configuration, and orchestration. It allows services to register themselves and discover other services via DNS or HTTP. Consul also supports health checking, multi-datacenter capabilities, and key-value storage. The core component is the Consul agent, which can run on every node in client or server mode. Servers are responsible for consensus and storing state while clients forward requests.
Service discovery with Eureka and Spring Cloud
The document discusses service discovery with Eureka and Spring Cloud. It introduces traditional applications where services have fixed locations versus modern applications where services are dynamic. It explains that service discovery with a service registry like Eureka allows services to find each other and load balance requests. The rest of the document demonstrates configuring Eureka as a service registry and client applications that can discover and consume services registered with Eureka.
Getting Started with Consul
This document provides an overview of getting started with Consul, including:
1. Consul is a tool for discovering and configuring services that is built on Golang and uses 3 basic ports for RPC, HTTP, and DNS.
2. It features service discovery, health checking, key/value storage, and multi-datacenter support.
3. Setup involves downloading the Consul binary, running the agent, and using commands like "consul members" and "consul join" to manage nodes.
Microservices with docker swarm and consul
This document discusses implementing microservices using Docker Swarm and Consul. It recommends programming languages and tools for orchestration, databases, load balancing, monitoring, and other functions. Docker Swarm allows clustering Docker hosts into a pool of resources. Consul provides service discovery, configuration, and failure detection across multiple datacenters. Consul-Template listens for Consul updates and configures applications. Registrator automatically registers and deregisters Docker services with Consul. An example scenario shows how services scale across nodes with this architecture.
Service Discovery 101
This document summarizes a presentation on service discovery for microservice architectures. It outlines the need for service discovery due to services dynamically scaling and failing. It discusses common discovery strategies like hardcoded IPs, DNS, and DNS with load balancers that don't scale well. The recommended approach is to use a service registry like Consul, which allows for automated service discovery and failure detection in a distributed system. The presentation concludes with a demo of Consul's service discovery capabilities.
Netflix0SS Services on Docker
1. The document describes a Docker implementation of NetflixOSS microservices on IBM SoftLayer.
2. Key aspects discussed include networking Docker containers across multiple SoftLayer datacenters, managing the Docker API across multiple hosts, and integrating Docker images with SoftLayer image management.
3. Lessons learned include the need for a proxy for the Docker remote API across multiple hosts, and approaches for keeping Docker advantages like image portability when integrating with an IaaS platform.
Spring Cloud and Netflix Components
This document outlines several Spring Cloud components: Hystrix for fault tolerance, Eureka for service discovery, Zuul for routing and filtering, Ribbon for load balancing, Feign for declarative REST clients, Spring Cloud Config for external configuration, and Spring Cloud Bus for distributed messaging between apps. It provides brief descriptions and configuration examples for each component.
How lagom helps to build real world microservice systems
This talk was given at the inaugural microservicesmanchester.com and gave an introduction to Lightbend's Lagom Framework (lightbend.com/lagom).
Container Orchestration with Docker Swarm and Kubernetes
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Consul: Service-oriented at Scale
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1A8pJF6.
Armon Dadgar presents Consul, a distributed control plane for the datacenter. Armon demonstrates how Consul can be used to build, configure, monitor, and orchestrate distributed systems. Filmed at qconsf.com.
Armon Dadgar has a passion for distributed systems and their application to real world problems. He is currently the CTO of HashiCorp, where he brings distributed systems into the world of DevOps tooling.
Service Discovery In Kubernetes
Service Discovery in kubernetes is all about how services of kubernetes get discovered internally and externally. How does a single POD communicate to another POD the within the cluster and how does a user request reach to a specific POD in the cluster? These are some questions that are answered by this TOPIC.
Architecting for Microservices Part 2
You can find the first part of this presentation here: https://www.slideshare.net/secret/pAvK8Qd9f07oa
This presentation takes a deep dive into how the Million Song Library, a microservices-based application, was built using the Netflix Stack, Cassandra and Datastax.
To learn more about Million Song Library and its components visit the project on GitHub: https://github.com/kenzanlabs/million-song-library
Lea
Building Microservices with Spring Cloud and Netflix OSS
Source code:
https://github.com/semihhakkioglu/spring-cloud-microservice-example
https://github.com/semihhakkioglu/spring-cloud-microservice-config
Consul in 5 minutes
Lightning talk about Consul showing the main features and explaining the basis of its acrchitecture. The code of the demo can be found on my github. https://github.com/toff63/consul-cluster
Container orchestration overview
In deploying apps that have been containerized, you have a lot to think about regarding what to use in production. There are a lot of things to manage, so orchestrators become a huge help. providing many services together such as scheduling, container communication, scaling, health, and more. There are major platforms to consider from Kubernetes, Swarm to ECS. In this talk we'll go through the overview of orchestrators and some of the differences between the big players. You should come out of the talk knowing where to go next in determining your orchestrator needs.
How Cloudify uses Chef as a Foundation for PaaS
As PaaS is becoming more prevalent than ever, most PaaS environments and frameworks are still strongly opinionated and allow for very limited control and extensibility.
Extending a PaaS framework requires deep understating of its internals at best, and in many cases in not even possible.
Cloudify, a new open source PaaS framework, has taken a different approach, by using recipes (As opposed to heavyweight coding and platform extension) as means to introduce new application stacks to the PaaS layer. You can think of it as extending the recipe model of Chef to support application level concerns, such as orchestration, dependency management, multi-tier and multi-host deployments, monitoring and autoscaling.
This presentation covers the foundations of Cloudify, and how it leverages Chef as a key enabler for an open PaaS framework.
Openstack Fundamentals by CloudZone @Back2School
Agenda:
What is OpenStack?
Components overview
Different flavors of OpenStack
Deploying methods
Architecture
Lessons learned migrating 100+ services to Kubernetes
TransferWise migrated over 150 services from bare metal servers to Kubernetes in AWS over the course of a year. They developed tools and processes to automate cluster creation with Terraform, service deployment through custom manifest generation from YAML definitions, and a network mesh with Envoy to enable service-to-service communication. Some lessons learned included not exposing Kubernetes complexity, choosing the right CNI plugin, and installing node local DNS to reduce errors. Future plans include using EKS for simplified upgrades, enabling developer environments, and implementing network policies and advanced deployment pipelines.
Building a Cloud Native Service - Docker Meetup Santa Clara (July 20, 2017)
In this talk, we share our experience of building up a cloud native service with Docker, Kubernetes, and CoreDNS. It is a customer-facing, multi-tenant, and globally available service that helps customers defending against various Internet attacks.
The global availability of the service is achieved through Anycast so that all customers only need to access one IP address across different regions. Deploying Anycast turns out to be a challenge because of the limitations on certain clouds. We overcome those limitations through containerization of different components with Docker.
We also share our experiences in container orchestration, container networking, load balancing, and service registration & discovery. We use a simplified architecture for container networking, and the service registration & discovery is done through CoreDNS. The overall design have helped our deployed service with improved elasticity, ease of use, and lowered maintenance cost.
fabric8 ... and Docker, Kubernetes & OpenShift
This presentation gives an Overview about Kubernetes and OpenShift, their differences and what fabric8 (fabric8.io) adds to the mix
Consul
Consul is a service discovery tool that allows services to register themselves and discover other services via a distributed key-value store. It provides service discovery, health checking, and distributed configuration management. Consul works by having Consul agents that gossip and use the Raft consensus protocol to maintain a consistent key-value store across datacenters. Clients can access services via HTTP endpoints to register services, discover health checks, and access the key-value store.
Pulsar Architectural Patterns for CI/CD Automation and Self-Service_Devin Bost
We examine real-world architectural patterns involving Apache Pulsar to automate the creation of function and pub/sub flows for improved operational scalability and ease of management. We’ll cover CI/CD automation patterns and reveal our innovative approach of leveraging streaming data to create a self-service platform that automates the provisioning of new users. We will also demonstrate the innovative approach of creating function flows through patterns and configuration, enabling non-developer users to create entire function flows simply by changing configurations. These patterns enable us to drive the automation of managing Pulsar to a whole new level. We also cover CI/CD for on-prem, GCP, and AWS users.
This is Part 2 of this presentation: https://www.youtube.com/watch?v=pmaCG...
In summary, we will cover:
CI/CD for on-prem, GCP, and AWS users
Automated creation of function flows by configuration
Automated provisioning of pub/sub users and topics
Architectural patterns and best practices that enable automation
Overstock has leveraged Pulsar as the backbone of a self-service data fabric, a unified data platform to enable users to publish and consume data across the company and integrate with other services. We utilized Pulsar to solve a data governance problem, and Pulsar has performed marvelously. To support our real-world production use cases, we have developed message flows, integrations, and architectural patterns to solve common use cases, maximize value, simplify ease-of-use, automate management, and unify company data and services around this new platform.
Cloud Foundry Summit 2015: Building a Robust Cloud Foundry (HA, Security and DR)
Speakers: Haydon Ryan, Pivotal; Duncan Winn, Pivotal
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Lagom in Practice
"It’s open source. It’s highly opinionated.
Build greenfield microservices and decompose your Java EE monolith like a boss."
Lightbend (formerly Typesafe) has come up with their own framework, Lagom, for architecting microservices based systems. With Lagom, Lightbend wants to take up the competition with the Spring Cloud stack.
Lagom is built upon Akka and Play and focuses on reactive and message-driven APIs, distributed persistence with Event Sourcing and CQRS and high developer productivity. On the 10th of March a first MVP version has been released with a Java API, the Scala API is being worked on.
This workshop acts as an introduction to Lagom during which we will have a look at developing and deploying Lagom microservices.
As a warm-up, you could check out the newest blogpost on the JWorks Tech Blog: https://ordina-jworks.github.io/microservices/2016/04/22/Lagom-First-Impressions-and-Initial-Comparison-to-Spring-Cloud.html.
Github repo with presentation: https://github.com/yannickdeturck/lagom-shop
Blogpost Lagom: First Impressions and Initial Comparison to Spring Cloud: https://ordina-jworks.github.io/microservices/2016/04/22/Lagom-First-Impressions-and-Initial-Comparison-to-Spring-Cloud.html
Podcast Lightbend Podcast Ep. 09: Andreas Evers test drives Lagom in comparison with Spring Cloud: https://www.lightbend.com/blog/lightbend-podcast-ep-09-andreas-evers-test-drives-lagom-in-comparison-with-spring-cloud
Docker in production: problems, fixes and beyond
This document discusses some problems encountered when using Docker in production and provides recommendations to address them. It recommends: (1) avoiding links and instead using service discovery like Consul; (2) avoiding port redirection due to potential memory leaks and compatibility issues, and using host networking instead; (3) not using the default storage driver and instead creating a partition with a thin pool to address storage issues; (4) avoiding large images to reduce deployment time and disk usage; and (5) not using Docker for databases or storage services due to data persistence challenges. The document aims to help users address common problems when adopting Docker in a production environment.
Service Discovery using etcd, Consul and Kubernetes
Overview of Service Discovery and Service Discovery using etcd, Consul, Kubernetes and Docker. Presented at Open source meetup, Bangalore(http://www.meetup.com/Bangalore-Open-Source-Meetup/events/229763724/)
More Related Content
What's hot
Service Discovery 101
This document summarizes a presentation on service discovery for microservice architectures. It outlines the need for service discovery due to services dynamically scaling and failing. It discusses common discovery strategies like hardcoded IPs, DNS, and DNS with load balancers that don't scale well. The recommended approach is to use a service registry like Consul, which allows for automated service discovery and failure detection in a distributed system. The presentation concludes with a demo of Consul's service discovery capabilities.
Netflix0SS Services on Docker
1. The document describes a Docker implementation of NetflixOSS microservices on IBM SoftLayer.
2. Key aspects discussed include networking Docker containers across multiple SoftLayer datacenters, managing the Docker API across multiple hosts, and integrating Docker images with SoftLayer image management.
3. Lessons learned include the need for a proxy for the Docker remote API across multiple hosts, and approaches for keeping Docker advantages like image portability when integrating with an IaaS platform.
Spring Cloud and Netflix Components
This document outlines several Spring Cloud components: Hystrix for fault tolerance, Eureka for service discovery, Zuul for routing and filtering, Ribbon for load balancing, Feign for declarative REST clients, Spring Cloud Config for external configuration, and Spring Cloud Bus for distributed messaging between apps. It provides brief descriptions and configuration examples for each component.
How lagom helps to build real world microservice systems
This talk was given at the inaugural microservicesmanchester.com and gave an introduction to Lightbend's Lagom Framework (lightbend.com/lagom).
Container Orchestration with Docker Swarm and Kubernetes
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Consul: Service-oriented at Scale
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1A8pJF6.
Armon Dadgar presents Consul, a distributed control plane for the datacenter. Armon demonstrates how Consul can be used to build, configure, monitor, and orchestrate distributed systems. Filmed at qconsf.com.
Armon Dadgar has a passion for distributed systems and their application to real world problems. He is currently the CTO of HashiCorp, where he brings distributed systems into the world of DevOps tooling.
Service Discovery In Kubernetes
Service Discovery in kubernetes is all about how services of kubernetes get discovered internally and externally. How does a single POD communicate to another POD the within the cluster and how does a user request reach to a specific POD in the cluster? These are some questions that are answered by this TOPIC.
Architecting for Microservices Part 2
You can find the first part of this presentation here: https://www.slideshare.net/secret/pAvK8Qd9f07oa
This presentation takes a deep dive into how the Million Song Library, a microservices-based application, was built using the Netflix Stack, Cassandra and Datastax.
To learn more about Million Song Library and its components visit the project on GitHub: https://github.com/kenzanlabs/million-song-library
Lea
Building Microservices with Spring Cloud and Netflix OSS
Source code:
https://github.com/semihhakkioglu/spring-cloud-microservice-example
https://github.com/semihhakkioglu/spring-cloud-microservice-config
Consul in 5 minutes
Lightning talk about Consul showing the main features and explaining the basis of its acrchitecture. The code of the demo can be found on my github. https://github.com/toff63/consul-cluster
Container orchestration overview
In deploying apps that have been containerized, you have a lot to think about regarding what to use in production. There are a lot of things to manage, so orchestrators become a huge help. providing many services together such as scheduling, container communication, scaling, health, and more. There are major platforms to consider from Kubernetes, Swarm to ECS. In this talk we'll go through the overview of orchestrators and some of the differences between the big players. You should come out of the talk knowing where to go next in determining your orchestrator needs.
How Cloudify uses Chef as a Foundation for PaaS
As PaaS is becoming more prevalent than ever, most PaaS environments and frameworks are still strongly opinionated and allow for very limited control and extensibility.
Extending a PaaS framework requires deep understating of its internals at best, and in many cases in not even possible.
Cloudify, a new open source PaaS framework, has taken a different approach, by using recipes (As opposed to heavyweight coding and platform extension) as means to introduce new application stacks to the PaaS layer. You can think of it as extending the recipe model of Chef to support application level concerns, such as orchestration, dependency management, multi-tier and multi-host deployments, monitoring and autoscaling.
This presentation covers the foundations of Cloudify, and how it leverages Chef as a key enabler for an open PaaS framework.
Openstack Fundamentals by CloudZone @Back2School
Agenda:
What is OpenStack?
Components overview
Different flavors of OpenStack
Deploying methods
Architecture
Lessons learned migrating 100+ services to Kubernetes
TransferWise migrated over 150 services from bare metal servers to Kubernetes in AWS over the course of a year. They developed tools and processes to automate cluster creation with Terraform, service deployment through custom manifest generation from YAML definitions, and a network mesh with Envoy to enable service-to-service communication. Some lessons learned included not exposing Kubernetes complexity, choosing the right CNI plugin, and installing node local DNS to reduce errors. Future plans include using EKS for simplified upgrades, enabling developer environments, and implementing network policies and advanced deployment pipelines.
Building a Cloud Native Service - Docker Meetup Santa Clara (July 20, 2017)
In this talk, we share our experience of building up a cloud native service with Docker, Kubernetes, and CoreDNS. It is a customer-facing, multi-tenant, and globally available service that helps customers defending against various Internet attacks.
The global availability of the service is achieved through Anycast so that all customers only need to access one IP address across different regions. Deploying Anycast turns out to be a challenge because of the limitations on certain clouds. We overcome those limitations through containerization of different components with Docker.
We also share our experiences in container orchestration, container networking, load balancing, and service registration & discovery. We use a simplified architecture for container networking, and the service registration & discovery is done through CoreDNS. The overall design have helped our deployed service with improved elasticity, ease of use, and lowered maintenance cost.
fabric8 ... and Docker, Kubernetes & OpenShift
This presentation gives an Overview about Kubernetes and OpenShift, their differences and what fabric8 (fabric8.io) adds to the mix
Consul
Consul is a service discovery tool that allows services to register themselves and discover other services via a distributed key-value store. It provides service discovery, health checking, and distributed configuration management. Consul works by having Consul agents that gossip and use the Raft consensus protocol to maintain a consistent key-value store across datacenters. Clients can access services via HTTP endpoints to register services, discover health checks, and access the key-value store.
Pulsar Architectural Patterns for CI/CD Automation and Self-Service_Devin Bost
We examine real-world architectural patterns involving Apache Pulsar to automate the creation of function and pub/sub flows for improved operational scalability and ease of management. We’ll cover CI/CD automation patterns and reveal our innovative approach of leveraging streaming data to create a self-service platform that automates the provisioning of new users. We will also demonstrate the innovative approach of creating function flows through patterns and configuration, enabling non-developer users to create entire function flows simply by changing configurations. These patterns enable us to drive the automation of managing Pulsar to a whole new level. We also cover CI/CD for on-prem, GCP, and AWS users.
This is Part 2 of this presentation: https://www.youtube.com/watch?v=pmaCG...
In summary, we will cover:
CI/CD for on-prem, GCP, and AWS users
Automated creation of function flows by configuration
Automated provisioning of pub/sub users and topics
Architectural patterns and best practices that enable automation
Overstock has leveraged Pulsar as the backbone of a self-service data fabric, a unified data platform to enable users to publish and consume data across the company and integrate with other services. We utilized Pulsar to solve a data governance problem, and Pulsar has performed marvelously. To support our real-world production use cases, we have developed message flows, integrations, and architectural patterns to solve common use cases, maximize value, simplify ease-of-use, automate management, and unify company data and services around this new platform.
Cloud Foundry Summit 2015: Building a Robust Cloud Foundry (HA, Security and DR)
Speakers: Haydon Ryan, Pivotal; Duncan Winn, Pivotal
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Lagom in Practice
"It’s open source. It’s highly opinionated.
Build greenfield microservices and decompose your Java EE monolith like a boss."
Lightbend (formerly Typesafe) has come up with their own framework, Lagom, for architecting microservices based systems. With Lagom, Lightbend wants to take up the competition with the Spring Cloud stack.
Lagom is built upon Akka and Play and focuses on reactive and message-driven APIs, distributed persistence with Event Sourcing and CQRS and high developer productivity. On the 10th of March a first MVP version has been released with a Java API, the Scala API is being worked on.
This workshop acts as an introduction to Lagom during which we will have a look at developing and deploying Lagom microservices.
As a warm-up, you could check out the newest blogpost on the JWorks Tech Blog: https://ordina-jworks.github.io/microservices/2016/04/22/Lagom-First-Impressions-and-Initial-Comparison-to-Spring-Cloud.html.
Github repo with presentation: https://github.com/yannickdeturck/lagom-shop
Blogpost Lagom: First Impressions and Initial Comparison to Spring Cloud: https://ordina-jworks.github.io/microservices/2016/04/22/Lagom-First-Impressions-and-Initial-Comparison-to-Spring-Cloud.html
Podcast Lightbend Podcast Ep. 09: Andreas Evers test drives Lagom in comparison with Spring Cloud: https://www.lightbend.com/blog/lightbend-podcast-ep-09-andreas-evers-test-drives-lagom-in-comparison-with-spring-cloud
What's hot (20)
How lagom helps to build real world microservice systems
How lagom helps to build real world microservice systems
Container Orchestration with Docker Swarm and Kubernetes
Container Orchestration with Docker Swarm and Kubernetes
Building Microservices with Spring Cloud and Netflix OSS
Building Microservices with Spring Cloud and Netflix OSS
Lessons learned migrating 100+ services to Kubernetes
Lessons learned migrating 100+ services to Kubernetes
Building a Cloud Native Service - Docker Meetup Santa Clara (July 20, 2017)
Building a Cloud Native Service - Docker Meetup Santa Clara (July 20, 2017)
Pulsar Architectural Patterns for CI/CD Automation and Self-Service_Devin Bost
Pulsar Architectural Patterns for CI/CD Automation and Self-Service_Devin Bost
Cloud Foundry Summit 2015: Building a Robust Cloud Foundry (HA, Security and DR)
Cloud Foundry Summit 2015: Building a Robust Cloud Foundry (HA, Security and DR)
Viewers also liked
Docker in production: problems, fixes and beyond
This document discusses some problems encountered when using Docker in production and provides recommendations to address them. It recommends: (1) avoiding links and instead using service discovery like Consul; (2) avoiding port redirection due to potential memory leaks and compatibility issues, and using host networking instead; (3) not using the default storage driver and instead creating a partition with a thin pool to address storage issues; (4) avoiding large images to reduce deployment time and disk usage; and (5) not using Docker for databases or storage services due to data persistence challenges. The document aims to help users address common problems when adopting Docker in a production environment.
Service Discovery using etcd, Consul and Kubernetes
Overview of Service Discovery and Service Discovery using etcd, Consul, Kubernetes and Docker. Presented at Open source meetup, Bangalore(http://www.meetup.com/Bangalore-Open-Source-Meetup/events/229763724/)
Scaling Like Twitter with Apache Mesos
Learn how Apache Mesos can help you scale your datacenter by Sunil Shah and Philip Norman, Distributed Systems Engineers at Mesosphere.
Service Discovery and Registration in a Microservices Architecture
Microservices, Service Discovery and Registration have been heading towards the peak of inflated expectations on the Gartner Hype cycle for over the last year or so, but there has often been a lack of clarity as to what these are, why are they needed or how to implement them well.
Service discovery and registration are key components of most distributed systems and service oriented architectures. In this session we will talk about what, why and how of service registration and discovery in distributed systems in general and OpenStack in particular.
We will talk about some of the technologies that address this challenge like Zookeeper, Etcd, Consul, Mesos-DNS, Minuteman, SkyDNS, SmartStack or Eureka. We will also address how these technologies as well as existing OpenStack projects can be used to solve this problem inside OpenStack environments.
Docker ホスティングサービス 'Arukas' での Mesos + Marathon の活用について（Mesos勉強会）
2016年8月4日に開催された「Mesos勉強会」において、技術本部 山田 修司が「Docker ホスティングサービス 'Arukas' での Mesos + Marathon の活用について」と題し、講演した際の資料です。
■イベント詳細
http://connpass.com/event/36415/
Rancher/Kubernetes入門ハンズオン資料～第2回さくらとコンテナの夕べ #さくらの夕べ 番外編
https://sakura-kanto.doorkeeper.jp/events/53172
Better Full Text Search in PostgreSQL
Full text search in PostgreSQL is a flexible and powerful facility to search collection of documents using natural language queries. We will discuss several new improvements of FTS in PostgreSQL 9.6 release, such as phrase search, better dictionaries support and tsvector editing functions. Also, we will present new features currently in development - RUM index support, which enables acceleration of some important kinds of full text queries, new and better ranking function for relevance search, loading dictionaries into shared memory and support for search multilingual content.
忙しい人の5分で分かるMesos入門 - Mesos って何だ？
アプリケーションエンジニアでもわかる Docker と Mesos 勉強会
https://sakura-kanto.doorkeeper.jp/events/53777
2016年11月18日(金)
発表資料
本スライドの想定は
「 Mesos って聞いたことあるけど、よくわかんない 」
「 Apache Mesosって何だ？ 」
といった疑問を持つ読者であり
Mesos の概念や背景を知るための資料です
Rancher command line interface
Rancher Meetup Tokyo #2 - connpass
https://connpass.com/event/44092/
#ranchermeetup
Viewers also liked (12)
Service Discovery using etcd, Consul and Kubernetes
Service Discovery using etcd, Consul and Kubernetes
Service Discovery and Registration in a Microservices Architecture
Service Discovery and Registration in a Microservices Architecture
Docker ホスティングサービス 'Arukas' での Mesos + Marathon の活用について（Mesos勉強会）
Docker ホスティングサービス 'Arukas' での Mesos + Marathon の活用について（Mesos勉強会）
Rancher/Kubernetes入門ハンズオン資料～第2回さくらとコンテナの夕べ #さくらの夕べ 番外編
Rancher/Kubernetes入門ハンズオン資料～第2回さくらとコンテナの夕べ #さくらの夕べ 番外編
Similar to Service discovery in mesos
How Yelp uses Mesos to Power its SOA Infrastructure
In this talk, Evan describes the glue that Yelp has created around Mesos, Marathon, and Docker to make it easy to deploy services.
ApacheCon Core: Service Discovery in OSGi: Beyond the JVM using Docker and Co...
OSGi offers an excellent service discovery mechanism, but it is limited to services inside the JVM. With Docker nowadays it is trivially easy to deploy all kind of (micro) services, using pretty much any technology stack, so we’d like to discover those as easily as the ones inside the JVM. We will have a look at how we can use the Docker API to discover services in other containers, and how we can use Consul to expand service discovery to other hosts.
Micro-services meetup
Overview of the role of orchestration technologies in creating micro-services based architectures, and micro-services as a foundation for cloud native computing (CNCF)
Kubernetes #1 intro
Kubernetes is an open-source container management platform. It has a master-node architecture with control plane components like the API server on the master and node components like kubelet and kube-proxy on nodes. Kubernetes uses pods as the basic building block, which can contain one or more containers. Services provide discovery and load balancing for pods. Deployments manage pods and replicasets and provide declarative updates. Key concepts include volumes for persistent storage, namespaces for tenant isolation, labels for object tagging, and selector matching.
Containerization - The DevOps Revolution
Containerization allows for standardized and isolated application deployment across infrastructure through container runtimes like Docker. Key features that enable containers include namespaces which isolate processes and their views of the system, cgroups which control resource usage, and copy-on-write storage for efficient application packaging. A container orchestration system like Mesos provides scalability, fault tolerance, and unified resource management across clusters. This allows maximizing infrastructure utilization through flexible scheduling of containerized applications and services on shared clusters.
Introduction to Kubernetes
Presentation from the first meetup of Kubernetes Pune - introduction to Kubernetes (https://www.meetup.com/Kubernetes-Pune/events/235689961)
introduction to micro services
First steps into developing an application as a suite of small services, and analysis of tools and architecture approaches to be used.
Topics covered:
1) What is a micro service architecture
2)Advantages in code procedures, team dynamics and scaling
3) How container services such as docker assist in its implementation
4) How to deploy code in a micro services architecture
5) Container Management tools and resource efficiency (mesos, kubernetes, aws container service)
6) Scaling up
By PeoplePerHour team
presented by CTO Spyros Lambrinidis & Senior DevOps Panagiotis Moustafellos @ Docker Athens Meetup 18/02/2015
Introduction to Kubernetes
Soft Introduction to Google's framework for taming containers in the cloud. For devs and architects that they just enter the world of cloud, microservices and containers
IT Talk «Microservices & Serverless Architectures», Alexander Chichenin (Solu...
Amazon Web Services
- Amazon Lambdas
- Serverless Architectures
- Serverless Toolkit
- Resoarer Toolkit
MongoDB SoCal 2020: Using MongoDB Services in Kubernetes: Any Platform, Devel...
MongoDB Kubernetes operator and MongoDB Open Service Broker are ready for production operations. Learn about how MongoDB can be used with the most popular container orchestration platform, Kubernetes, and bring self-service, persistent storage to your containerized applications. A demo will show you how easy it is to enable MongoDB clusters as an External Service using the Open Service Broker API for MongoDB
locize tech talk
- What is locize?
- Why serverless?
- Why AWS?
- Technology stack
- Base function types (code)
- Tooling
- Q&A
http://locize.com
Using Redgate, AKS and Azure to bring DevOps to your database
Practical solutions on how to bring DevOps to your database including:
- The importance of getting your database code into source control
- How to test your database changes
- Tools you can use to automate build and test processes
- How to build an automated deployment process for your database with Redgate tools
- How to embrace using Azure Kubernetes Services (AKS) in your deployment pipeline
- Deploying your entire pipeline as and when it is needed from Dev to Prod saving your organisation money
Using Redgate, AKS and Azure to bring DevOps to your Database
Join Hamish Watson and Rob Sewell to learn practical solutions on how to bring DevOps to your database, including:
• The importance of getting your database code into source control
• How to test your database changes
• Tools you can use to automate build and test processes
• How to build an automated deployment process for your database with Redgate tools
• How to embrace using Azure Kubernetes Services (AKS) in your deployment pipeline
• Deploying your entire pipeline as and when it is needed from Dev to Prod saving your organisation money
Database upgrades and data in general are often the most complicated part of your deployment process, so having a robust deployment path and checks before getting to production is very important.
The demos will showcase practical solutions that can help you and your team bring DevOps to your database using SQL Source Control, infrastructure as code, docker containers and SQL Change Automation – all leading up to a fully automated test and deployment process.
This will be a fun-filled fast paced hour and you will learn some new skills which will bring immediate benefit to your organization.
MRA AMA Part 10: Kubernetes and the Microservices Reference Architecture
On Demand Link - https://www.nginx.com/resources/webinars/mra-ama-part-10-kubernetes-and-the-microservices-reference-architecture/
The NGINX Microservices Reference Architecture (MRA) has been a major contributor to the discussion of microservices architectures. Kubernetes has now emerged as the leading container orchestration platform, and NGINX has developed the NGINX Kubernetes Ingress controller.
In this webinar, we describe and demonstrate how to use NGINX Open Source and NGINX Plus with Kubernetes and the NGINX Kubernetes Ingress controller. We relate the use of NGINX tools and Kubernetes to the MRA’s Proxy Model, Router Mesh Model, and the Fabric Model. We also briefly compare these to full-service mesh implementations such as Istio.
Building a high-performance, scalable ML & NLP platform with Python, Sheer El...
Building a high-performance, scalable ML & NLP platform with Python, Sheer El...Pôle Systematic Paris-Region
This document summarizes the development of Lore's machine learning and NLP platform using Python. It started as a monolithic Python server but evolved into a microservices architecture using Docker, Kubernetes, and Celery for parallelization. Key lessons included using DevOps tools like Docker for development and deployment, Celery to parallelize tasks, and wrapping services to improve modularity, flexibility, and performance. The platform now supports multiple products and consulting work in a scalable and maintainable way.locize tech stack
- What is locize?
- Why serverless?
- Why AWS?
- Technology stack
- Base function types (code)
- Tooling
- Future
- Q&A
https://locize.com
Data collection in AWS at Schibsted
Schibsted collects and analyzes 900 million events/day using AWS. This presentation gives an overview of the systems and architecture, including the solutions to GDPR.
Triangle Devops Meetup 10/2015
Triangle Devops Meetup covering Netflix open source, cloud architecture, and what Andrew did in his first year working as a senior software engineer in the cloud platform group.
Integration Microservices
- Integration microservices are used to compose other microservices and APIs to create new services, similar to the concept of "miniservices". They help integrate web APIs, legacy systems, and microservices.
- Technologies for building integration microservices include frameworks like SpringBoot and Dropwizard, Apache Camel, and the Ballerina programming language. Ballerina is designed specifically for integration and allows graphical composition of services and connectors.
- Integration microservices are an important part of microservices architecture as they handle service compositions and orchestration between multiple microservices and external APIs.
Building Microservices with .NET (speaker Anton Vasilenko, Binary Studio)
Binary Studio MEET FOR IT gatherings: 5th of March 2016 our meetup was devoted to .NET platform and took part in Lviv, Ukraine.
Similar to Service discovery in mesos (20)
How Yelp uses Mesos to Power its SOA Infrastructure
How Yelp uses Mesos to Power its SOA Infrastructure
ApacheCon Core: Service Discovery in OSGi: Beyond the JVM using Docker and Co...
ApacheCon Core: Service Discovery in OSGi: Beyond the JVM using Docker and Co...
IT Talk «Microservices & Serverless Architectures», Alexander Chichenin (Solu...
IT Talk «Microservices & Serverless Architectures», Alexander Chichenin (Solu...
MongoDB SoCal 2020: Using MongoDB Services in Kubernetes: Any Platform, Devel...
MongoDB SoCal 2020: Using MongoDB Services in Kubernetes: Any Platform, Devel...
Using Redgate, AKS and Azure to bring DevOps to your database
Using Redgate, AKS and Azure to bring DevOps to your database
Using Redgate, AKS and Azure to bring DevOps to your Database
Using Redgate, AKS and Azure to bring DevOps to your Database
MRA AMA Part 10: Kubernetes and the Microservices Reference Architecture
MRA AMA Part 10: Kubernetes and the Microservices Reference Architecture
Building a high-performance, scalable ML & NLP platform with Python, Sheer El...
Building a high-performance, scalable ML & NLP platform with Python, Sheer El...
Building Microservices with .NET (speaker Anton Vasilenko, Binary Studio)
Building Microservices with .NET (speaker Anton Vasilenko, Binary Studio)
Recently uploaded
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
CAKE: Sharing Slices of Confidential Data on Blockchain
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Recently uploaded (20)
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
CAKE: Sharing Slices of Confidential Data on Blockchain
CAKE: Sharing Slices of Confidential Data on Blockchain
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Service discovery in mesos
- 1. Service discovery in Mesos Cluster Miguel Angel Guillen AeriaGames GmbH
- 2. Who am I? ● From Elche(Spain) ● Working in Berlin in AeriaGames ● DevOps,Sysadmin, SRE, etc… ● Video Games
- 3. AERIA GAMES Different partners and technologies
- 4. Mesos ● Cluster resources ● Supports docker containers ● Is really cool ● Mesos and Beyond was before this talk!!
- 5. Service discovery “Service discovery tools manage how processes and services in a cluster can find and talk to one another.”
- 6. DNS ● More basic service discovery ● But A records are really simple ● SRV records are really useful ● Few services supports SRV
- 7. Service Discovery tools ● Provides a service registry system ● Integrates with an API ● Provides meta-data of the service ● Use or provides a K/V store ● It provides libraries and tools
- 8. Service Discovery tools ● Zookeeper K/V store libraries ● ETCD K/V store libraries REST API ● Consul K/V store libraries REST API DNS ● All can be used as K/V store for all kind of usage
- 9. Mesos
- 10. Mesos
- 12. Zookeeper ● Zookeeper K/V store libraries ● NO YET REST OR DNS!* ● Only library support** * REST is WIP ** you can use confd for reading, but set data is still from lib or zkshell
- 13. What I should do? ● There is other options ● mesos-dns ● marathon-dns ● marathon-lb ● The problem is if service discovery pattern fits in your needs
- 14. Service Discovery Patterns ● Client-Side Discovery Pattern – The client is responsible for determining the network locations – Load balancing is managed by the client – Usually client supports service discovery with a library integrated (zookeeper)
- 15. Service Discovery Patterns ● The Server-Side Discovery Pattern – The client makes a request to a service via a load balancer – Client don’t know the service, only load balancer – Load Balancer use service registry via DNS or other kind of integrations.
- 16. Service Discovery Antipatterns in microservices Server side discovery – We add an extra hop – Load balancer as SpoF ● Or scale with the microservice – Adds complexity to the architecture
- 17. And Finally…. In Mesos
- 19. Service Discovery in mesos Registrator – Reads the event bus of docker and adds the service to a service registry ● Application is removed from the registry when docker container is stopped. – If the host crash the services are still registered ● If the host is recovered problems can appear – There are better solutions for using with mesos
- 20. Mesos-consul mesos-consul ● “Mesos-consul automatically registers/deregisters services run as Mesos tasks.” ● Can be deployed in mesos as task or marthon app ● Depends on consul as service registry ● Use a lot of the features of consul like tags ● Develop for mantl(CiscoCloud)
- 21. Service Discovery in mesos Mesos-DNS “Mesos-DNS enables DNS based service discovery in Apache Mesos clusters.” ● Supports SRV records ● It has special records for marathon – Ex: leading master: A record (leader.domain) and SRV records (_leader._tcp.domain and _leader._udp.domain) ● Supports round robin for multiple tasks with the same name
- 22. Service Discovery in mesos
- 23. Service discovery in mesos/marathon Marathon-lb “Marathon-lb is a tool for managing HAProxy, by consuming Marathon's app state” ● Server side service discovery ● Deployable in marathon it self ● Depends on marathon ● Is included in DCOS
- 24. ?
- 25. Vielen Dank!!