Starting with an overview of Microservices we’ll review best practices and an overview of players in the field. Using Azure Functions with Node, we’ll walk through a couple of demos around setting up Functions and getting them working. We’ll briefly cover debugging, CI/CD, and integrations into other Azure services
What is a cooperative? One description of a cooperative is "a jointly owned enterprise engaging in the production or distribution of goods or the supplying of services, operated by its members for their mutual benefit..”1 The economist Richard Wolff notes that “ cooperative ownership, cooperative purchasing, cooperative selling, and cooperative labor have all been labelled co-ops”2. Cooperatives are not necessarily worker owned, worker managed, or worker directed.
The integration of microservices, the Internet of Things, and context aware (e.g. location and environment) systems are forcing our development efforts to become distributed, fault-tolerant, scalable, soft real-time (predictable response and latency), and highly available. When approaching this difficult task, problem areas in legacy systems can often be integrated with high availability components instead of undergoing a complete rewrite.
An example of this is a legacy Rails application that needs to integrate a chat component. Rails is great for productivity, especially in small and mid-size applications. When adding a (soft) real-time messaging social component, the best practice is to use a third-party service such as Pusher to get started. This is because it is better to leverage a different architectural model, Publish/Subscribe, instead of the regular client/server polling model for performance. For more privacy, control, or custom additions, we can use Elixir/Erlang for this performance and availability without using a third party. In this training we will talk about the distributed, fault-tolerant, scalable, soft real-time, and highly available properties of Elixir/Erlang while creating a clone of the Pusher service.
In the first part of this training, we will set up a simple Rails frontend and backend, and then add a connection to the Pusher service. We should then have a completely functioning soft real time chat service.
In the second part of this training we will remove the Pusher service and replace it with a service that we will write in Elixir.
We’re always looking for great people to join the Puppet team!
Let's chat about our open positions and what it’s like to work at Puppet, either in person or online.
With over 3.5 years of development time and over 16 rounds of refactoring and enhancement, my tool dwatch for DTrace has reached maturity and is quickly becoming the new hip tool for all your monitoring tasks. I would like to show you how to do everything from watching the system process scheduler in realtime to filtering out filesystem events. Here’s a short list of some of the things dwatch can do with a single easy-to-remember command syntax:
With dwatch, using DTrace has never been so fun and certainly easier than ever before.
For developers and system administrators, Jenkins provides a rich framework that can be used to automate a variety of tasks. In this talk, we’ll take a high-level look at the elements of Jenkins that make it a versatile, extensible application. In particular, we’ll discuss:
After participating in this workshop, attendees will have an idea of how Jenkins can be used to automate just about any repeatable task in their day-to-day work.
