Yogi Aradhye has been writing code for well over a decade and has worked on many different technologies. His diverse work experience includes small startups to large enterprises such as DELL. Currently, he is leading projects at Headspring as a Principal Consultant, focusing on building advanced distributed systems. Over the past 20 months, he has been a lead architect for a financial services client. He sets patterns and guides multiple teams in a collaborative journey towards microservices. Yogi has also been a speaker at .NET User Group Code Camps in Hartford, Boston, Houston, and Austin. He has also presented at larger developer conferences such as Kansas City Developer Conference and NDC Oslo.
For organizations moving to microservices, autonomy is a huge draw—but it can become something of a double-edged sword. With autonomy comes the responsibility on the part of the development team and the organization to maintain diligent design oversight.
Enter the architects—usually a group of senior engineers with no clear understanding of what their level of oversight should be, yet now beholden to their appointed roles. The group gets viewed as an “ivory tower,” always busy in meetings when they’re needed in the field. Now you have smart engineers doing more meetings than coding, anarchy is breeding, and nobody is happy. What’s going on here? What can you, either as an architect or an organizational leader, do?
In this talk, we’ll take a look at how to break some traditional molds and modernize the architect’s role. I’ll take you through a journey to explore some principles—forged through practice on real-world client projects.
You’ll learn strategies for:
- mentoring development teams
- scaling processes
- maximizing efficiency
With the right structures in place, architects can guide teams into the “pit of success,” as Scott Guthrie likes to put it. We want to make sure architects are viewed as close peers and not as 10xengineers.
More and more of us are working from home these days. Who wouldn’t like an excellent machine you can run 20 instances of Visual Studio on? The code looks a lot better in 4K. You would probably also want to play some games on this machine. There are so many ways to build this. There are so many options in GPU, CPU, Monitors, etc. You can shell out some good amount of money and not have a good machine. How do we access an excellent rig that does it all for us?
In this talk, we will look at everything you need to know, based on my recent building experience. There are so many different tradeoffs for almost every part of your machine. We will take a deep dive into the selection criteria. You can build a rig that’s just right for work and gaming without completely breaking the bank.
Almost every application we build today needs to call another service over the network at least once. It seems like a relatively trivial task in the .NET world. However, the confusing API can lead you to incorrect usage. This code can flow under the radar passing all the tests and eventually ending up in production. It has caused some significant outages for my clients in the past. What happened?
In this talk, we will take a look at the causes of issues and lessons learned. We will investigate the areas of confusion. In the deeper dive, you will know what to look out for. We will see how the API evolution has happened. You will learn to use the new APIs and help you create a robust solution that can put you on the path to success.
"Monolith to microservices" is not a business goal. Business stakeholders don't care about architecture choices. They care if their customers are getting the optimum experience. Adopting microservices can have business advantages, but many times, companies overlook the disadvantages and tradeoffs. They also underestimate the inefficiencies and problems that are not directly related to the microservices transformation but often hold a project like this back. What goes wrong with them?
In this talk, we will dive into my real project experiences when we helped our clients reign in out of control microservices projects. Having a monolith isn't inherently bad, nor does microservices transformation solely deliver business value. After listening to this talk, you will know why it doesn't have to be a binary choice between microservices and a monolith. This knowledge can leave you equipped to start making improvements right away and achieve a successful transformation.