CodeIsGo.com

An article by Percona team about building and releasing Operators for Kubernetes to run traditional databases in a cloud-native fashion. They released Percona Server for MongoDB and Percona XtraDB Cluster; they were chosen because they both feature replication systems that can be made to work effectively in a containerized world.

The article is split into:

• Benchmark methodology
• What CNI plugins we tested
  • Project Calico
  • Flannel
  • Cilium
  • Weave (weave-net)
  • Intel SR-IOV and Multus
  • Kube-Router

For full results please click to the original article. One very interesting result was how strong the correlation was between network throughput, as measured by iPerf3, and database throughput, as measured by sysbench. You will also get video with a talk on the topic. Nice one!

Integrations between people and projects are a challenge for every organization. For teams that work remotely, it’s twice as challenging. Integrations should be made as simple and “low-touch” as possible. By Jonathan Saring.

Luckily enough, modern frontend is built with components. And, we can leverage Bit to achieve quick and simple component-driven integrations between teammates working on different projects. Bit lets front-end teams expose components from each other’s projects and quickly use their APIs wherever they’re needed. It makes the process much simpler and more effective than before through a set of unique features and capabilities throughout the component’s lifecycle.

In this post, author explains and demonstrate:

• How to quickly expose components from your project and let other teammates use their APIs in their own projects (no repo splitting)
• How these components can be quickly integrated into new projects using Bit’s ability to “source” components for local code editing
• How your team can share all your components for reuse and expose their APIs through the bit.dev component cloud.
• And finally, how you can connect Bit.dev to GitHub and Slack to create one super-workflow for building with components together

Excellent read and as a bonus you will get video tutorial as well.

In this tutorial you will elarn about more about the WebSockets protocol. Go provides a WebSocket library, but the Go team advises to use other solutions built by the community. By Gustavo Caso.

Author used websocket – a minimal and idiomatic WebSocket library for Go. At a time it was the most recent of all and had support for context and rate-limiting. Once we move away from deciding on the WebSocket library, we need a way to route request to our server, Go provides a fantastic http package for doing that.

The tutorial and provided code splits content between client and server. The server handles new WebSocket connections, listen to messages on those socket connections and broadcast messages to the right users. Also, it takes care of adding and removing users to different chat rooms.

The client connects to the server, listens to messages that are sent to it and print them. It also allows the users to submit new messages to the server. For the details follow the link to the original article. Nice one!

Author of this blog post will share his experience and learnings with a project to improve my knowledge of the most significant ReactJS feature in recent time – hooks. Tutorial is about building Minesweeper clone. TypeScript was also used. By Ivaylo.

The article walks you through:

• Development environment & setup
• Game styling using retro library React95
• Game logic
• React hooks
• State, without Redux
• TypeScript 3.7

… and more. Author is now convinced that hooks are the future of React together with concurrent rendering, which will be the next major feature. Source code is available on GitHub. Easy read!

AWS Amplify is a fantastic framework that helps you develop your web or mobile applications quickly. By Aman Mittal.

AWS Amplify not only does it enhances your current tech stack, but it actually has many built-in features that you don’t have to worry about, especially when your app is in the development process. Some features include authentication, GraphQL and REST API support, a way to manage user pool, notifications.

Amplify can be integrated with most popular frontend frameworks like React, Vue, Angular, Ionic, React Native, or plain old vanilla JavaScript, if you’d like.

The article then reads about:

• Requirements
• Creating a new React Native App
• How to create a new AWS IAM user
• Initializing & Integrating Amplify SDK
• Enable Amplify Auth Resource
• withAuthenticator: Adding a High Order Component
• Testing the default Amplify auth flow

This tutorial takes a look at one of the most important features of an application: authentication. Excellent read!

Gene Kim is a researcher and an author who has been studying high performing IT organizations for over two decades. HIs take on the five ideals for the modern enterprise.

He notes why each is essential for the modern enterprise:

• Locality and simplicity
• Focus, flow and joy
• Improvement of daily work
• Psychological safety
• Customer focus

This post covers three objectives that The Unicorn Project book looks to address, which is to describe what successful transformations have looked like to help others replicate those outcomes, the challenge of trying to figure out how you get data where it needs to go, and how we can overcome the strong opposition to the new ways of working.

Excellent read for any entrepreneur!

An article about how to get started with logging in Kubernetes. This topic is quite extensive as there are many components to consider before having a complete perspective of what’s happening inside your applications. By Erin Baez.

This post gives you an introduction to recommended practices, tools, patterns, and strategies for logging in Kubernetes. You’ll learn that instrumenting your application to emit logs is not going to be enough. By default, Kubernetes emits a lot of logs from all its components, so you’ll have a lot of information. You’ll have to know where to look and how to manage all of those logs.

The main parts of this article:

• Starting With Kubernetes Logging
• Reading the Logs
• What Should You Log in Applications for Kubernetes?
• Architectural Patterns for Application Logs
• Exposing an Endpoint for the Application Logs
• Using a Sidecar Container
• What Other Logs Are Available in Kubernetes?
• Keep All Kubernetes Logs Together

… and more. In Kubernetes, you can consume several types of logs. But to get useful insights from all these logs, you’ll need to keep all of them together. Centralized logging becomes crucial in distributed systems like those you run Kubernetes in. When you have all the logs at the same place, you can go deeper when troubleshooting. Good read!

Let’s face it, life can be hard. It’s easy to say leave your problems at the door, but sometime common life stressors can affect employees’ personal lives so much that it creeps into their professional life. By Michelle Kankousky.

Increased levels of psychological or physical stress can have serious implications for their performance and that of their teams.

The article then goes in some detail into:

• What is a life stressor?
• What are the signs your employee is struggling?
• How can you talk to the employee about the situation?
• How can your business provide assistance?

No matter what the solution, the common denominator is consistency: each employee must be treated the same. Thinking ahead and establishing policies and procedures that address potential situations can help avoid problems. Good read!

Todd Palmer published this article about an architectural approach to better Angular applications. The article shows you how to keep your Templates declarative and dumb, your Components thin and smart, and your Services fat and happy.

The article will definitively answer your questions of how to structure your Angular application so the code is readable, testable, and maintainable. Specifically, this consistent approach makes our code more readable to others, especially those that are familiar with the approach. The code becomes more testable, because Services are easy to test.

A Template is Dumb when it doesn’t know anything about any other part of the application except for: Its Component and Its sub-component Templates. Services should be Fat and Happy. By Fat, I mean that business logic goes into your Services. When in doubt whether to put code into a Service or a Component, put it in the Service. Fatten up that Service and starve your Component.

The article is split into:

• Core Principles
• Templates should be Declarative and Dumb (Declarative, imperative, avoid complicated logic, small and simple)
• Components should be should be Thin and Smart
• Services should be Fat and Happy

A smart Component knows and controls exactly what the current state of the Template is. The Component determines exactly how to interact with the data model or Services based on user activity. Good explanation with examples of good and bac practice. All the code examples in the talk and article are in a GitHub repo. You will also get link to video resources. Nice one!

If you are an Angular developer there is no way you missed RxJS Observables but you might be less familiar with Subjects. Even though they are less frequent than simple Observables, they are extremely useful. Understanding them will help you write better, cleaner reactive code. By Dornhoth.

Observables are lazy Push collections of multiple values. A Subject is like an Observable, but can multicast to many Observers.

The article describes:

• Observables
• Subjects
• BehaviorSubjects
• ReplaySubjects
• AsyncSubjects

Intuitively, you can think of Observables as objects that emit streams of values. You need to subscribe to the Observable for it to start counting, the same way you need to call a function for it to be computed. Subjects are Observables. Nice intro into reactive programming!