Microservices World

Tuesday, October 25, 2022

- PDT
PRO Workshop (API): So You Want to Split Your Monolith: First Steps
Joy Ebertz
Joy Ebertz
Split, Principal Engineer

It's very common to attempt to split a monolith into microservices and more and more companies are starting down this path.  But how do you even approach this problem? It's a giant task and getting started can be very daunting.  In this talk, I will draw on my experience at both Box and Split, as well as the research that I've done on the topic to discuss getting started with splitting up a monolith.  I will cover the strangler fig and big bang patterns as well as how to think about selecting services and ways to test your new services, including load and parity testing.  I will also mix in some of our actual experiences as we went down this path. 

- PDT
PRO Workshop (API): Killing a Giant - a Practical Guide Through the Martin Fowler's Strangler Fig Pattern
Branislav Bujišić
Branislav Bujišić
Platform.sh, Director of Engineering

Back in 2019, our company was preparing for a period of fast growth. One of the key blockers to that growth was a monolithic application called Accounts. Built initially around 2014 as a rapidly developed proof of concept, it quickly became a central piece for the customer interaction, a billing system, an auth server, a support ticketing system, the project lifecycle management system. The technical debt grew exponentially with every new feature added. The system needed to be replaced.

Martin Fowler described an interesting solution for a practically zero-downtime migration project from a monolithic application to -- something else. Instead of replacing an app with a single big bang, let’s build the new application around the existing one, and let them slowly take over its responsibilities until we’re ready to just delete it entirely. The concept was stolen from a natural phenomenon of Australian strangler figs growing around a host tree until they kill it.

What could possibly go wrong with such an approach, you may ask yourself. Well -- as we learned in the last couple of years -- quite a lot of things! To name a few: shared state between the legacy and the replacement application, designing the stopgap communication between the applications, balancing the development of the new features with the migration of the existing ones.

Join me for the session where we’ll discuss the theory and practice of the Strangler Vine Pattern around a Drupal 7 monolith, with a special focus on all the embarrassing errors we made along the way. 

- PDT
PRO Workshop (API): Our Journey from Monolithic to Microservice with Kubernetes
Gian Paolo Santopaolo
Gian Paolo Santopaolo
IBV Solutions, Technical Fellow

Collaboard is one of the three major players worldwide when it comes to digital whiteboards, and we have extremely high availability and scalability requirements.
In this course, we will walk through our evolution from a monolithic application to the real microservice architecture supporting event-driven design with gRPC, signalR, Protobuf, and RabbitMQ for .Net 6 and React on Kubernetes in the Cloud. 

- PDT
PRO Workshop (API): gRPC and Microservices
Wenbo Zhu
Wenbo Zhu
Google Cloud, Senior Staff Software Engineer

In this talk, we will describe the role of gRPC (grpc.io) in building and deploying cloud-native microservices, our experiences in integrating different cloud platform functions as part of the gRPC framework and the values such a solution provides to microservice developers. 

- PDT
PRO Workshop (API): Refresh Without Restart (for Configs)
Karthikeyan Govindaraj
Karthikeyan Govindaraj
BlackRock, Cloud Native and DevOps Architect

Kubernetes and Containers became the defacto standard for designing and developing applications and services. This made us move in a fast-paced manner. With this fast-paced approach, developers need a lot of configurational values to be injected into the container during its startup and after its start-up. Oftentimes, to get them up-to-date data, these containers might need to get restarted.

In this session, Karthik will walk us through the different categories of configurational data. When and how those are used and also while refreshing the configurational data, how to obtain/reflect the latest data into containers without restarting them; essentially without deleting the pod. This is a method of coding implementation instead using a dedicated API to refresh the data (restarting the web server not the container). 

- PDT
PRO Workshop (API): So You Want to Build an API....
Doug Sillars
Doug Sillars
Orkes.io, Head of Developer Relations

If you’re like me, you’ve *consumed* many APIs to build applications. It’s like magic: data is sent to an endpoint, and in milliseconds the results come back.  Sometimes, you have an idea of what the developers built on the backend to make the API work, other times it is a total black box. But building an API does not have to be hard.

In this talk, we’re going to build an API.  We’ll utilize Netflix Conductor to orchestrate our microservices, and have a working API endpoint in no time flat.  Out of the box, our API will have version control, error control to notify us if/when our API has any errors. We'll quickly incorporate access control via API keys, and include a billing mechanism so that we can begin making money, and attracting lucrative VC investments. 

Wednesday, October 26, 2022

- PDT
OPEN TALK (API): You're Building Microservices Wrong
Jonathan Oliver
Jonathan Oliver
Smarty, Founder, CEO & CTO

In this presentation we will cover how microservices are typically implemented by ignoring The Fallacies of Distributed Computing. Further, we discuss solutions to make microservices much more robust and able to adapt to the realities of distributed systems. 

- PDT
OPEN TALK (API): Bring your .NET APIs to AWS
Isaac Levin
Isaac Levin
Amazon Web Services, .NET Developer Advocate

APIs are the backbone of many services we all know and love, and when it comes to hosting those APIs, AWS is a great option. When building APIs with .NET on AWS, there are a plentiful amount of options, ranging from the tried-and-true Web API running on Elastic Beanstalk to running highly scalable event driven functions with AWS Lambda. Let us spend some time during this session talking about building APIs on .NET and running them in AWS.

- PDT
OPEN TALK (API): Demystifying Microservice Testing
Wilhelm Haaker
Wilhelm Haaker
Parasoft, Sr. Solutions Architect

One of the biggest advantages of developing microservices is the ability to develop, deploy, and upgrade services individually, without disrupting the entire ecosystem. At the same time, microservice architectures are introducing new testing challenges, such as understanding how to isolate each component for testing.

In this webinar, learn about the different architectures and protocols employed in microservice development (including Kafka, Rabbit MQ, REST, and Protocol Buffers).

Actionable takeaways include:
Understanding the practical differences between some of the common microservice architectures.
How to effectively test in a synchronous ecosystem using REST, taking advantage of existing contracts to validate that changes you make will not break the system.
How to approach testing in an event-driven ecosystem, using Kafka event streams.
When and how service virtualization can help provide a stable test environment given the challenge of isolating components in microservice testing. 

Thursday, October 27, 2022

- PDT
OPEN TALK (API): Mr. Toad's Wild (Service Mesh) Ride
Jim Barton
Jim Barton
Solo.io, Field Engineer

The enterprise software community is accelerating its migration from monoliths to microservices. Service Mesh platforms like Istio are a key technology enabling this transition. Connecting, Securing, and Observing the elements of your Kubernetes service networks is no longer optional; it is an absolute imperative.

Come with us on a whirlwind tour of Gloo Mesh, an Istio-based platform that is optimized for multi-team and multi-cluster Service Meshes. In a fast-paced, no-slides session, we will build a fully functional example that illustrates:
• Establishing three multi-tenant workspaces to manage a half-dozen services;
• Enforcing Zero-Trust Networking policies;
• Configuring multi-cluster routing;
• Testing distributed failover; and
• Exploring the mesh's API Gateway features, including OIDC authentication, rate limiting, and Web Application Firewall security.

Buckle your seat belts! This Wild Ride will swiftly show you how to accelerate your Service Mesh adoption. 

- PDT
OPEN TALK (API): Maintaining Application SBOMs in a Microservices Architecture
Tracy Ragan
Tracy Ragan
DeployHub, CEO

Supply chain management speaks to improving security in the software systems we create. At the core of these discussions is the generation of SBOMs and CVE reports. In monolithic architecture, the creation of application SBOMs and CVE reports are done at the CI build step. But how do we manage SBOMs in a microservice environment without a monolithic build?

This presentation will review the supply chain complexities in a microservice architecture with hundreds of run-time dependencies, each having its own SBOM and CVE reports. It will introduce Ortelius, an open-source unified supply chain catalog, incubating at the Continuous Delivery Foundation, that aggregates SBOM and CVE microservice level data up to the consuming ‘logical’ applications. Attendees will learn how they can easily produce application-level supply chain reports that meet new federal security requirements, even in complex cloud-native environments. 

Tuesday, November 1, 2022

- PDT
[#VIRTUAL] PRO Workshop (API): So You Want to Split Your Monolith: First Steps
Joy Ebertz
Joy Ebertz
Split, Principal Engineer

It's very common to attempt to split a monolith into microservices and more and more companies are starting down this path.  But how do you even approach this problem? It's a giant task and getting started can be very daunting.  In this talk, I will draw on my experience at both Box and Split, as well as the research that I've done on the topic to discuss getting started with splitting up a monolith.  I will cover the strangler fig and big bang patterns as well as how to think about selecting services and ways to test your new services, including load and parity testing.  I will also mix in some of our actual experiences as we went down this path. 

- PDT
[#VIRTUAL] PRO Workshop (API): Killing a Giant - a Practical Guide Through the Martin Fowler's Strangler Fig Pattern
Branislav Bujišić
Branislav Bujišić
Platform.sh, Director of Engineering

Back in 2019, our company was preparing for a period of fast growth. One of the key blockers to that growth was a monolithic application called Accounts. Built initially around 2014 as a rapidly developed proof of concept, it quickly became a central piece for the customer interaction, a billing system, an auth server, a support ticketing system, the project lifecycle management system. The technical debt grew exponentially with every new feature added. The system needed to be replaced.

Martin Fowler described an interesting solution for a practically zero-downtime migration project from a monolithic application to -- something else. Instead of replacing an app with a single big bang, let’s build the new application around the existing one, and let them slowly take over its responsibilities until we’re ready to just delete it entirely. The concept was stolen from a natural phenomenon of Australian strangler figs growing around a host tree until they kill it.

What could possibly go wrong with such an approach, you may ask yourself. Well -- as we learned in the last couple of years -- quite a lot of things! To name a few: shared state between the legacy and the replacement application, designing the stopgap communication between the applications, balancing the development of the new features with the migration of the existing ones.

Join me for the session where we’ll discuss the theory and practice of the Strangler Vine Pattern around a Drupal 7 monolith, with a special focus on all the embarrassing errors we made along the way. 

- PDT
[#VIRTUAL] PRO Workshop (API): gRPC and Microservices
Wenbo Zhu
Wenbo Zhu
Google Cloud, Senior Staff Software Engineer

In this talk, we will describe the role of gRPC (grpc.io) in building and deploying cloud-native microservices, our experiences in integrating different cloud platform functions as part of the gRPC framework and the values such a solution provides to microservice developers. 

- PDT
[#VIRTUAL] PRO Workshop (API): Refresh Without Restart (for Configs)
Karthikeyan Govindaraj
Karthikeyan Govindaraj
BlackRock, Cloud Native and DevOps Architect

Kubernetes and Containers became the defacto standard for designing and developing applications and services. This made us move in a fast-paced manner. With this fast-paced approach, developers need a lot of configurational values to be injected into the container during its startup and after its start-up. Oftentimes, to get them up-to-date data, these containers might need to get restarted.

In this session, Karthik will walk us through the different categories of configurational data. When and how those are used and also while refreshing the configurational data, how to obtain/reflect the latest data into containers without restarting them; essentially without deleting the pod. This is a method of coding implementation instead using a dedicated API to refresh the data (restarting the web server not the container). 

- PDT
[#VIRTUAL] PRO Workshop (API): So You Want to Build an API....
Doug Sillars
Doug Sillars
Orkes.io, Head of Developer Relations

If you’re like me, you’ve *consumed* many APIs to build applications. It’s like magic: data is sent to an endpoint, and in milliseconds the results come back.  Sometimes, you have an idea of what the developers built on the backend to make the API work, other times it is a total black box. But building an API does not have to be hard.

In this talk, we’re going to build an API.  We’ll utilize Netflix Conductor to orchestrate our microservices, and have a working API endpoint in no time flat.  Out of the box, our API will have version control, error control to notify us if/when our API has any errors. We'll quickly incorporate access control via API keys, and include a billing mechanism so that we can begin making money, and attracting lucrative VC investments. 

- PDT
[#VIRTUAL] PRO Workshop (API): Our journey from monolithic to microservice with Kubernetes
Gian Paolo Santopaolo
Gian Paolo Santopaolo
IBV Solutions, Technical Fellow

Collaboard is one of the three major players worldwide when it comes to digital whiteboards, and we have extremely high availability and scalability requirements.
In this course, we will walk through our evolution from a monolithic application to the real microservice architecture supporting event-driven design with gRPC, signalR, Protobuf, and RabbitMQ for .Net 6 and React on Kubernetes in the Cloud. 

Wednesday, November 2, 2022

- PDT
[#VIRTUAL] PRO TALK (API): Why Do You Need a Microservice Catalog to Enhance Developer Productivity?
Turja Narayan Chaudhuri
Turja Narayan Chaudhuri
Cloud Platform, Assistant Director

It is indeed a valid argument that microservices allows engineering organization to grow and scale, providing better constructs for isolation and independence. But, microservices do not only add technical complexity -they also introduce organizational complexity and pose a serious threat to scaling at the enterprise level.

Over time, with hundreds of services and no governance or oversight, when something breaks, nobody knows who to reach out to. A microservice catalog is a record/list of all the microservices that an enterprise has in its ecosystem, providing powerful information at your fingertips.

In this talk, you will learn how a microservice catalog facilitates a successful microservice at scale architecture by helping developers find and share services, providing DevOps teams metadata about services needed to make solid decisions, and support teams ownership and consumption information needed when something goes wrong. 

- PDT
[#VIRTUAL] PRO TALK (API): Distributed Systems: Key Concepts & Patterns
Waleed Ashraf
Waleed Ashraf
Klarna, Senior Engineer

“Distributed Systems” is the main key to modern-day systems, microservices, and messaging brokers. This talk will be about the key concepts of Distributed Systems and different patterns being used in the industry. The topics we will go through are irrelevant to the technology and tech stack, so it’s good for engineers at all levels.

This talk is split into two parts. The first part will cover the key concepts and timeline of improvement in this field. In the second part, we will go through some of the main patterns which are being used in the industry to address the issues which come with distributed systems.

We'll go through concepts like Two Generals’ Problem, Consensus & Paxos, Cloud Spanner (CA), and patterns like Event Sourcing, CQRS, SAGA, etc. 

- PDT
[#VIRTUAL] OPEN TALK (API): You're Building Microservices Wrong
Jonathan Oliver
Jonathan Oliver
Smarty, Founder, CEO & CTO

In this presentation we will cover how microservices are typically implemented by ignoring The Fallacies of Distributed Computing. Further, we discuss solutions to make microservices much more robust and able to adapt to the realities of distributed systems. 

- PDT
[#VIRTUAL] OPEN TALK (API): Bring your .NET APIs to AWS
Isaac Levin
Isaac Levin
Amazon Web Services, .NET Developer Advocate

APIs are the backbone of many services we all know and love, and when it comes to hosting those APIs, AWS is a great option. When building APIs with .NET on AWS, there are a plentiful amount of options, ranging from the tried-and-true Web API running on Elastic Beanstalk to running highly scalable event driven functions with AWS Lambda. Let us spend some time during this session talking about building APIs on .NET and running them in AWS.

- PDT
[#VIRTUAL] OPEN TALK (API): Demystifying Microservice Testing
Wilhelm Haaker
Wilhelm Haaker
Parasoft, Sr. Solutions Architect

One of the biggest advantages of developing microservices is the ability to develop, deploy, and upgrade services individually, without disrupting the entire ecosystem. At the same time, microservice architectures are introducing new testing challenges, such as understanding how to isolate each component for testing.

In this webinar, learn about the different architectures and protocols employed in microservice development (including Kafka, Rabbit MQ, REST, and Protocol Buffers).

Actionable takeaways include:
Understanding the practical differences between some of the common microservice architectures.
How to effectively test in a synchronous ecosystem using REST, taking advantage of existing contracts to validate that changes you make will not break the system.
How to approach testing in an event-driven ecosystem, using Kafka event streams.
When and how service virtualization can help provide a stable test environment given the challenge of isolating components in microservice testing. 

- PDT
[#VIRTUAL] OPEN TALK (API): Proxies, Gateways, and Meshes: Cloud Connectivity Pattern for the Curious
Viktor Gamov
Viktor Gamov
Kong, Developer Advocate

API gateway technology has evolved a lot in the past decade, capturing more prominent and comprehensive use cases in what the industry calls “full lifecycle API management.”
API gateways were a management of the network runtime that allows us to expose and consume the APIs, secure them, and govern our API traffic. They provide a series of functionalities to support the development cycle, including creating, testing, documentation, monitoring, and overall exposure of our APIs.
Then around 2017, another pattern emerged from the industry: service mesh! Service mesh is an infrastructure layer for microservices communication. It abstracts the underlying network details and provides discovery, routing, and a variety of other functionality.
In this talk, Viktor Gamov will illustrate the differences between API gateways and service mesh — and when to use one or the other pragmatically.
This talk will also discuss the similarities and differences between the communication layer provided by gateways and service mesh. 

Thursday, November 3, 2022

- PDT
[#VIRTUAL] OPEN TALK (API): Mr. Toad's Wild (Service Mesh) Ride
Jim Barton
Jim Barton
Solo.io, Field Engineer

The enterprise software community is accelerating its migration from monoliths to microservices. Service Mesh platforms like Istio are a key technology enabling this transition. Connecting, Securing, and Observing the elements of your Kubernetes service networks is no longer optional; it is an absolute imperative.

Come with us on a whirlwind tour of Gloo Mesh, an Istio-based platform that is optimized for multi-team and multi-cluster Service Meshes. In a fast-paced, no-slides session, we will build a fully functional example that illustrates:
• Establishing three multi-tenant workspaces to manage a half-dozen services;
• Enforcing Zero-Trust Networking policies;
• Configuring multi-cluster routing;
• Testing distributed failover; and
• Exploring the mesh's API Gateway features, including OIDC authentication, rate limiting, and Web Application Firewall security.

Buckle your seat belts! This Wild Ride will swiftly show you how to accelerate your Service Mesh adoption. 

- PDT
[#VIRTUAL] OPEN TALK (API): Key Benefits of Modernizing Monolith Legacy Applications to Microservices With the Strangler Pattern
Amir Rapson
Amir Rapson
vFunction, CTO and Co-Founder

Transforming monolithic applications into microservices is a fundamental element for business modernization in order to innovate, scale and retain competitive positioning in the market. While modernization takes many forms, transforming monolithic applications into microservices is the most effective way to regain engineering velocity. In this session, Amir Rapson, CTO and co-founder of vFunction, will present how an AI assisted method that implements the Strangler Pattern to transform existing legacy monolithic applications into cloud-native microservices is used and how it benefits developers. This technical workshop will also include insights into how to determine components needed to run in parallel to existing monolithic code, the key factors for selecting components to refactor and critical elements to executing a successful app modernization strategy. 

- PDT
[#VIRTUAL] OPEN TALK (API): Maintaining Application SBOMs in a Microservices Architecture
Tracy Ragan
Tracy Ragan
DeployHub, CEO

Supply chain management speaks to improving security in the software systems we create. At the core of these discussions is the generation of SBOMs and CVE reports. In monolithic architecture, the creation of application SBOMs and CVE reports are done at the CI build step. But how do we manage SBOMs in a microservice environment without a monolithic build?

This presentation will review the supply chain complexities in a microservice architecture with hundreds of run-time dependencies, each having its own SBOM and CVE reports. It will introduce Ortelius, an open-source unified supply chain catalog, incubating at the Continuous Delivery Foundation, that aggregates SBOM and CVE microservice level data up to the consuming ‘logical’ applications. Attendees will learn how they can easily produce application-level supply chain reports that meet new federal security requirements, even in complex cloud-native environments.