This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In a single, monolithic repository, also known as a monorepo, you keep all your application and microservice code in the same source code repository (usually Git). Monorepo vs. polyrepo for microservices. As microservices architecture becomes more popular, teams tend to split their code into many repositories (the so-called polyrepos).
There are no katas or practical exercises, the focus of the workshop is on benefits, trade-offs, and critical concepts. Christian is a former practitioner of Agile methodologies, particularly eXtreme programming, with experience in practices like TDD, continuousintegration, building pipelines, and evolutionary design.
Overcoming CI/CD Pitfalls As organizations adopt a microservices architecture or transition between cloud providers, continuousintegration/continuous delivery (CI/CD) pipelines are a way to accelerate agility and time to market. But CI/CD can become cumbersome without the right tooling.
You’ll also learn how observability fits in with other progressive delivery techniques, like continuousintegration, feature flagging, and cloud-native microservices. . If you’re attending our workshop, you’ll complete those queries with the hands-on exercises. Are LEGOs more your speed?
To use Docker Compose to deploy Microservices to Docker. Our exploration will serve both as a setup exercise as well as a detailed configuration guide. We will cover best practices for security in a conventional ContinuousIntegration and Continuous Deployment (CI/CD) pipeline. Build images using a Dockerfile.
Exercises, katas and tech talks with the acumen of years of experience building great apps for Android and iOS. Their training courses help teams get better at Test Driven Development, ContinuousIntegration and Deployment, Domain-Driven Design, Clean Code and SOLID principles, Behaviour Driven Development and many other technical practices.
Our exploration will serve both as a setup exercise as well as a detailed configuration guide. We cover best practices for security in a conventional ContinuousIntegration and Continuous Deployment (CI/CD) pipeline. Similarly, we’ll build a Kubernetes cluster and deploy a sample microservice application to it.
ContinuousIntegration and testing). The sample app is a fork of the microservices-testing-examples repo, generously bequeathed to Honeycomb by André Schaffer and Dan Eidmark. A copy of the guide to work from and about 30 minutes to complete the exercises. Where to go from here.
” “Exercise multiple times a week!” For example, if a project includes the development of multiple microservices, it might be worthwhile to devote time to investigating whether the creation of a home-grown equivalent to a programmatic initializer service like Spring Initializer might be worthwhile. and grown to loath.
Later the concept of microservices emerged as the result of the growth of distributed architectures and cloud computing. But at the end of the day, the exercise remains exactly the same as it was three decades ago – to deliver an HTML page to a browser in the most efficient manner. But what about Sitecore?
Your team is building the UI, and several other teams are building the back-end microservices. Continuous Deployment. ContinuousIntegration. They use version control and practice continuousintegration, keeping all but the last few hours’ work ready to release. Zero Friction. Build for Production.
Applications have grown more complex too: we now have fleets of microservices operating asynchronously across hundreds or thousands of cloud instances. That exercise shows how important the platform is to the company. And as applications have become more complex, so has operations.
A team member accidentally erases a file, but continuousintegration rejects the commit. 3 Explain the exercise and provide an example: “(Name), I appreciate you for (reason).” Or, “we have microservices, not a monolith.” A programmer makes an off-by-one error, but their pairing partner suggests a test to catch it.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content