I had the great opportunity to visit the Red Hat Summit 2017. It was hosted in the Boston Convention and Exhibition Center in Boston in May 2-4, 2017. This blog post summarizes the interesting things I learned at the summit.
Red Hat OpenShift & Amazon Web Services. Red Hat will make AWS services accessible directly from the OpenShift web console. From within the OpenShift web console developers will be able to provision and configure AWS services such as CloudFront, ElastiCache, ELB, RDS, EMR, RedShift, S3 and Lambda.
Red Hat OpenShift.io. OpenShift.io is an online development environment for building container-based applications. OpenShift.io can create a project in GitHub for you to store your source code. The source code editing can be done in the integrated Eclipse Che. OpenShift.io can create a project in OpenShift Online in order to build your application and deploy it. Jenkins pipelines are used to orchestrate the CI/CD process. Currently, OpenShift.io is available in a limited developer preview. You can sign up at https://openshift.io
- The future Red Hat Middleware portfolio: Stacks and services and solutions
- Netflix OSS is interesting and Red Hat will support it because customers like it. However, some of the Netflix OSS features might be more efficiently implemented directly in Kubernetes instead of on top of Kubernetes. Netflix had to make architectural choices based on how AWS looked several years ago. AWS evolved since that time.
- Architectural evolution: monolith -> n-tier architecture -> microservices.
- Red Hat container technology strategy
- Kubernetes has won. You may have just not realized it yet.
- There are two reasons why the Kubernetes open source project is winning. First, it brings value to people. Second, people are excited to work on it.
- Kubernetes = kernel of the cloud operating systems
- Reproducible development to live applications with Java and Red Hat CDK
- Modern Java and DevOps lightning talks
- You can issue
oc cluster upto create a local OpenShift all-in-one cluster (requires Origin >= 1.3).
- Eclipse MicroProfile project is aimed at optimizing Enterprise Java for the microservices architecture. It focuses, among others, on application configuration, health-checking, fault tolerance and security.
- You can use API Gateway (e.g Apigee, 3scale) to dynamically route traffic into different OpenShift namespaces (test, staging, production).
- You can issue
- Atomic BOF
- In the future, the classic RHEL will be derived from the RHEL Atomic Host. It means that the new features will appear in the RHEL Atomic Host before being included into RHEL.
- Stepping off a cliff: Common sense approaches to cloud security
- VMs in the cloud are created and destroyed dynamically. This is one of the challenges for the security team.
- Wicked fast PaaS: Performance tuning of OpenShift and Docker
- RHEL 7.4 should support OverlayFS. For Docker storage, the OverlayFS is more memory efficient than the LVM thin pool provisioning, as with OverlayFS, the pages in the page cache can be shared between multiple containers.
- Beginning with OpenShift 3.5, the container image metadata will be stored only in the Docker registry. In previous versions of OpenShift, a duplicate of the image metadata was stored in etcd, too.
- The Truth about Microservices
- “Building a single microservice is easy. Building a microservices architecture is hard.”
- The hardest part of microservices is your data
- Debezium monitors the changes committed to the database (MySQL, MongoDB, PostgreSQL). For each database change, Debezium publishes an event to the Kafka broker. To consume the change events, an application can create a Kafka consumer that will consume all events for the topics associated with the database. In summary, Debezium turns a database transaction log into a Kafka stream that other applications can consume.
- Reactive systems with Eclipse Vert.x and Red Hat OpenShift
- Vert.x is a toolkit for building reactive applications on the JVM. It can discover services on OpenShift and Kubernetes.
- Container infrastructure trends: Optimizing for production workloads
- skopeo is a command line utility that allows you to inspect Docker images and image registries. It retrieves the required information from the repository metadata without the need to download the actual image. For example, with skopeo you can find out which tags are available for the given repository.
- buildah a tool for building Docker images. It can build container images without using the Docker daemon. Ansible-container and OpenShift’s S2I will be modified to use buildah under the hood.
- Function as a Service (Faas) - why you should care and what you need to know
- Architectural evolution: service -> microservice -> function.
- Good serverless use-cases: processing web-hooks, scheduled tasks (a la cron), data transformation (converting small images).
- Serverless architecture challenges: cannot use a larger programming framework to implement the function, as this would be too slow to initialize, increased latency in comparison to a long-running server process, large variance in latency, very complex at scale, debugging of functions is hard.
- Red Hat participates on development of Funktion that is part of the project fabric8.