.NET Fest 2019. Леонид Молотиевский. DotNet Core in production

•

1 gostou•253 visualizações

Во время доклада, я поделюсь с Вами опытом, который мы получили, используя микросервисы в прод K8S кластере. Также, обозначу основные проблемы, с которыми столкнулась наша команда на этапе их диагностики. И, самое главное - что мы сделали чтобы избежать их в будущем. Отвечу на вопросы: Почему мы мигрировали в облако? Почему dotNet Core 2.2 вызвал кучу проблем? Данный доклад сохранит сотни часов вашим разработчикам и DevOps команде, жизнь которой может напоминать кошмар.

Educação

Тема доклада
Тема доклада
Тема доклада
KYIV 2019
.Net Core in production
By Leonid Molotiievskyi
.NET CONFERENCE #1 IN UKRAINE

2
About me
• Hands-on software architect and technological
consultant
• Good at splitting a monolith to microservices
• Built a huge enterprise financial solution from scratch
• Technical guy who believes that right people decisions
are more important than technological ones
• Speaker and mentor

3
Spoilers about what we are going to talk
Agenda
Context overview
Environment that we used to live with
Scaling
How did we scale our services?

4
Hell for the DevOps
teamDo we solve the right problem?
Useful advices
The things that can help you to resolve
the problem
Lessons learned
How can we benefit in
future?
Q&A
Questions and answers

Context overview
Several statements about the project

6
Context overview
• Financial domain
• 25+ microservices
• Team 70+ people
• 20+ environments
• Three versions in support one in development

10
Solution?
- And a set of dummy queues left after descale/redeploy appear

11
Gateway: infinite redirect
- Where do we store
keys for cookies?

Hell for the DevOps team
What technology decisions helped us to survive

14
Each morning…
• Dev/Staging/Prod cluster is down
• RabbitMq/Mongo/Consul/Prometheus is not
operational
• The fire-fighter team is on the duty

16
Queues are growing… - 1
• “TTL time is too small” or?

17
Queues are growing… - 2
• A queue has a set of consumers
• Service A consumes the message
• Service A starts processing the message
• Heath check of consumer fails due to high load of
service A/network issue/OOM killed/etc.
• Duplicated message appear in the queue

18
OOM Killed issue
• .Net Core 2.2 doesn’t respect docker limits:
https://github.com/aspnet/AspNetCore/issues/3409
https://github.com/dotnet/coreclr/issues/18971
• ” Server GC was designed with the assumption that
the process using Server GC is the dominant process
on the machine. By default it uses as many heaps as
there are # of processors on the machine.”

19
Let’s fix issue by upgrade to .Net Core 3.0?
https://github.com/mongodb/mongo-csharp-driver/pull/372/files

20
Socket file descriptor leak in HttpClient

21
Docker: no space left on the device
level=info msg="[8] System error: write
/sys/fs/cgroup/docker/01f5670fbee1f6687f58f3a943b1e1bdaec26
30197fa4da1b19cc3db7e3d3883/cgroup.procs: no space left on
device"

Useful advices
What can prevent nasty situations

25
What can help you to find them?
Configured monitoring to track:
• Memory consumption
• CPU consumption
• Number of threads on worker node
• Number of open socket descriptors per node/pod
• Connection refused errors
• Correlation Ids in logs
• Number of messages in queues
• Number of consumers for queues

26
Use the standard health check middleware

27
Setup environment in the way…
• Infrastructure services must have HA setup
• Deploy at least two instances of each service
• Setup monitoring and alerting
• To be sure that “temporary data” disappear after
redeployment
• To not configure something manually

29
Lessons learned
• ”Do it as simple as possible” principle
doesn’t work. “Do it in the smart way” - works
• Think about application scaling from the
begging
• Know about open issues inside your target
framework
• Do not blame DevOps team, try to help them
to find out what is the reason

Mais conteúdo relacionado

Semelhante a .NET Fest 2019. Леонид Молотиевский. DotNet Core in production

Ship code like a keptn

Rob Jahn

Abstract The idea of this talk is to help development teams to make correct architectural decisions. Andrei will highlight the basic architectural principles and show ways to achieve architecture that is good enough to cover the project requirements and evolve in the future. He will also present several cases from real projects, where wrong, missing, or over-sophisticated architecture decisions really hurt the development teams: - Painful sharing: do shared modules increase reusability or will be the source of problems? - Microservices are the solution to every problem! - Non-extensible extensibility: too sophisticated configuration hurts - Over fine-grained: incorrect splitting to Microservices can make life even harder as with monolith - Convey horizontal split: how organizational driven split can jeopardise the architecture - Model-driven: central responsibility blocks and limits the team - Cargo cult: blindly following patterns and rule can produce an unmaintainable system - Freestyle architecture: what happens if teams completely ignore architecture - Improve with less intelligence: smart endpoint and dumb pipes

Architectural Decisions: Smoothly and Consistently

Comsysto Reply GmbH

Architectural Decisions: Smoothly and Consistently

Comsysto Reply GmbH

Bitfusion Nimbix Dev Summit Heterogeneous Architectures

Subbu Rama

Les Frost, Senior Technical Architect - Capgemini The DevOps movement is establishing itself within many organisations. Many people are asking “How do I do DevOps?” or “Can you tell me the recommended DevOps tool stack?” By the time many organisations adopt DevOps, will the rise of serverless computing such as AWS Lambda mean that they are already out-of-date? The debate is on-going as to whether serverless computing (i.e. outsourcing the management of servers so you can focus on building that critical business functionality), will move organisations from DevOps to NoOps. AWS Lambda enables users to run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of application or back end service – all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.

From DevOps to NoOps

Capgemini

Network devices play a crucial role; they are not just in the Data Center. It's the Wifi, VOIP, WAN and recently underlays and overlays. Network teams are essential for operations. It's about time we highlight to the configuration management community the importance of Network teams and include them in our discussions. This talk describes the personal experience of systems engineer on how to kickstart a network team into automation. Most importantly, how and where to start, challenges faced, and progress made. The network team in question uses multi-vendor network devices in a large traditional enterprise. NetDevOps, we do not hear that term as frequent as we should. Every time we hear about automation, or configuration management, it is usually the application, if not, it is the systems that host the applications. How about the network systems and devices that interconnect and protects our services? This talk aims to describe the journey a systems engineer had as part of an automation assignment with the network management team. Building from lessons learned and challenges faced with system automation, how one can kickstart an automation project and gain small wins quickly. Where and how to start the journey? What to avoid? What to prioritise? How to overcome the lack of network skills for the automation engineer and lack of automation and Linux/Unix skills for network engineers. What challenges were faced and how to overcome them? What fights to give up? Where do I see network automation and configuration management as a systems engineer? What are the status quo and future expectations?

Network Automation Journey, A systems engineer NetOps perspective

Walid Shaari

Micro Front-End & Microservices - Plansoft

Miki Lombardi

One of the biggest advantages Kubernetes has to offer is that it is agnostic to infrastructure and capable of managing diverse workloads running on different compute resources. This allows organizations to manage multiple developer platforms, who can operate across many environments such as on premise, hybrid and multiple clouds. Streamlined processes and automation is pivotal for operations when managing clusters at scale and maintaining security and policy checks. Paul Curtis, Principal Solutions Architect will demonstrate GitOps and Weave Kubernetes Platform in a hybrid and multi-cloud setup. Learn how to: Use model-driven automation to increases reliability and stability across environments Simplify multi-cluster management with GitOps Enable developers to push code to production daily (self-service) Improve utilization and capacity management through Kubernetes platforms on cloud and on-premise infrastructure

Hybrid and Multi-Cloud Strategies for Kubernetes with GitOps

Sonja Schweigert

Hybrid and Multi-Cloud Strategies for Kubernetes with GitOps

Weaveworks

Zoo keeper in the wild

datamantra

Join this info-packed and hands-on workshop where we will cover:  Introduction to Kubernetes & GitOps talk: We'll cover the most popular path that has brought success to many users already - GitOps as a natural evolution of Kubernetes. We'll give an overview of how you can benefit from Kubernetes and GitOps: greater security, reliability, velocity and more. Importantly, we cover definitions and principles standardized by the CNCF's OpenGitOps group and what it means for you.  Get Started with GitOps: You'll have GitOps up and running in about 30 mins using our free and open source tools! We'll give a brief vision of where you want to be with those security, reliability, and velocity benefits, and then we'll support you while go through the getting started steps. During the workshop, you'll also experience in action and see demos for: * an opinionated repo structure to minimize decision fatigue * disaster recovery using GitOps * Helm charts example * Multi-cluster example * all with free and open source tools mostly in the CNCF (eg. Flux and Helm). If you have questions before or after the workshop, talk to us at #weave-gitops http://bit.ly/WeaveGitOpsSlack (If you need to invite yourself to the Slack, visit https://slack.weave.works/)

Free GitOps Workshop

Weaveworks

Multi-core architecture is the present and future way in which the market is addressing Moore’s law limitations. Multi-core workstations, high performance computers, GPUs and the focus on hybrid/ public cloud technologies for offloading and scaling applications is the direction development is heading. Leveraging multiple cores in order to increase application performance and responsiveness is expected especially from classic high-throughput executions such as rendering, simulations, and heavy calculations. Choosing the correct multi-core strategy for your software requirements is essential, making the wrong decision can have serious implications on software performance, scalability, memory usage and other factors. In this overview, we will inspect various considerations for choosing the correct multi-core strategy for your application’s requirement and investigate the pros and cons of multi-threaded development vs multi-process development. For example, Boost’s GIL (Generic Image Library) provides you with the ability to efficiently code image processing algorithms. However, deciding whether your algorithms should be executed as multi-threaded or multi-process has a high impact on your design, coding, future maintenance, scalability, performance, and other factors. A partial list of considerations to take into account before taking this architectural decision includes: - How big are the images I need to process - What risks can I have in terms of race-conditions, timing issues, sharing violations – does it justify multi-threading programming? - Do I have any special communication and synchronization requirements? - How much time would it take my customers to execute a large scenario? - Would I like to scale processing performance by using the cloud or cluster? We will then examine these issues in real-world environments. In order to learn how this issue is being addressed in a real-world scenario, we will examine common development and testing environments we are using in our daily work and compare the multi-core strategies they have implemented in order to promote higher development productivity.

Choosing the right parallel compute architecture

corehard_by

WTF is a Microservice - Rafael Schloming, Datawire

Ambassador Labs

AOUG_11Nov2016_Challenges_with_EBS12_2

Sean Braymen

IBM Blockchain Platform - Architectural Good Practices v1.0

Matt Lucas

Kubernetes, Toolbox to fail or succeed for beginners - Demi Ben-Ari, VP R&D @...

Demi Ben-Ari

DESIGN West 2013 Presentation: Accelerating Android Development and Delivery

David Rosen

A cornerstone of the DevOps philosophy, investment in automation at all stages across the SDLC has increased over recent years. Automation promises velocity and reduced errors, helps foster repeatable processes, and removes the need for long hours on dull, repetitive tasks. So what’s not to like? The downside of automation is that unless applied at the right place in your SDLC it can make a bad process worse. Automation also raises questions around job security, the need for re-skilling in other areas, and tool sprawl if different teams each choose their preferred technology. This session will outline: -A short chronology of where automation has impacted the modern software stack -Where it makes the most sense to automate (by identifying your key constraints) -Best practices for adopting automation and how to identify where it’s working — and where it isn’t For more information, visit: www.appdynamics.com

Automation: The Good, The Bad and The Ugly with DevOpsGuys - AppD Summit Europe

AppDynamics

DevOpsGuys - DevOps Automation - The Good, The Bad and The Ugly

DevOpsGroup

Presented at the OnAndroidConf, October 22 2013, http://www.onandroidconf.com/sessions.html Abstract: Optimizing the Android build environment to perform at world-class level is a big challenge for many Android device and chipset makers today. Churning through thousands of platform builds per week requires laser-focus on high-performance infrastructure and tooling. If you’re looking at improving your overall engineering and developer productivity, the software build use case is an obvious area to prioritize. This technical talk will focus on the following aspects of the Android platform build: Common Android platform build challenges and opportunities with real-life production references The various Android build use cases and their needs – full integration and release builds, developer incremental builds Evolution of the Android build and codebase with trends and statistics Detailed technical analysis of the Android platform build, highlighting opportunities for improvements Proposed solutions and technical tricks to optimize an Android software build environment

OnAndroidConf 2013: Accelerating the Android Platform Build

David Rosen

Semelhante a .NET Fest 2019. Леонид Молотиевский. DotNet Core in production (20)

Ship code like a keptn

Architectural Decisions: Smoothly and Consistently

Bitfusion Nimbix Dev Summit Heterogeneous Architectures

From DevOps to NoOps

Network Automation Journey, A systems engineer NetOps perspective

Micro Front-End & Microservices - Plansoft

Hybrid and Multi-Cloud Strategies for Kubernetes with GitOps

Zoo keeper in the wild

Free GitOps Workshop

Choosing the right parallel compute architecture

WTF is a Microservice - Rafael Schloming, Datawire

AOUG_11Nov2016_Challenges_with_EBS12_2

IBM Blockchain Platform - Architectural Good Practices v1.0

Kubernetes, Toolbox to fail or succeed for beginners - Demi Ben-Ari, VP R&D @...

DESIGN West 2013 Presentation: Accelerating Android Development and Delivery

Automation: The Good, The Bad and The Ugly with DevOpsGuys - AppD Summit Europe

DevOpsGuys - DevOps Automation - The Good, The Bad and The Ugly

OnAndroidConf 2013: Accelerating the Android Platform Build

Mais de NETFest

Что делать, если все, что можно уже закэшировано, а код всё ещё тормозит? В этом докладе мы обсудим, как работают некоторые низкоуровневые механизмы .NET и как мы с их помощью можем выиграть драгоценные секунды, когда счет идет на отдельные такты процессора.

.NET Fest 2019. Николай Балакин. Микрооптимизации в мире .NET

NETFest

The move to microservice infrastructure exposes new challenges, that are not typical for classic monolithic applications. Deployment, security, monitoring -- this list is far from complete. In this talk Serhiy will speak about how to establish a fast and reliable communication channels between microservices. What patterns, protocols and data formats are available. How to enforce a backwards compatibility and strict contract between services and their clients. When we should use sync or async communication style, and so on. Come to this session and hopefully you will come out with new ideas of how to build your stuff even better.

.NET Fest 2019. Сергей Калинец. Efficient Microservice Communication with .NE...

NETFest

В сентябре 2019 года выходит новая версия .NET Core 3. Я расскажу о преимуществах .NET Core перед .NET Framework, о том, что нового становится доступным в последней версии .NET Core и о планах Майкрософт по поводу будущего всех .NET фреймворков.

.NET Fest 2019. Оля Гавриш. .NET Core 3.0 и будущее .NET

NETFest

А Вы знали, что практически для каждого проекта можно применить машинное обучение? И теперь для этого не нужно изучать новый язык программирования (как Python или R) и осваивать численные методы. В этом докладе я расскажу об основах машинного обучения и о том, как легко начать использовать его в своих .NET проектах с помощью ML.NET и других решений от Microsoft.

.NET Fest 2019. Оля Гавриш. Машинное обучение для .NET программистов

NETFest

In these days, automation is the key to reduce the effort in governing complex system. Also, it reduces mistakes of manual, repetetive, operations. Despite the standardization of common approaches using text-based Infrastructure-as-code definitions, as YAML or JSON, I will suggest to write your provisioning templates using C# and .NET, against Microsoft Azure. In this demo-only session, we'll see the Azure Fluent Management Libraries in action to create a multi-tenant environment with strong-typed objects and compile-type-safe provisioning code.

.NET Fest 2019. Roberto Freato. Provisioning Azure PaaS fluently with Managem...

NETFest

“Domain Driven Design is an approach to software development for complex needs by connecting the implementation to an evolving model.” While there are many resources on the web about the DDD, they are generally theoretical rather than useful practical guides. One reason is that a DDD implementation quite varies depending on your domain and culture. However, it is still possible to provide some explicit rules those can help you while designing your code base. This talk starts by introducing the DDD and providing a layering model based on the DDD and the Clean Architecture. It then introduces the core building of an application built on the DDD principles. In the second part of the talk, it shows some strict coding rules for the core building blocks with real code examples and suggestions. These rules are essential to build a large scale application implements DDD patterns & practices. While the solution structure and code samples are based on .NET and C#, the talk is useful for developers and architects working with any server side technology.

.NET Fest 2019. Halil Ibrahim Kalkan. Implementing Domain Driven Design

NETFest

Я розповім про еволюцію фіча тоглів у компанії та наш досвід їх використання. Пройдемось покроково в їх розвитку: Від файлу конфігурації зі звичайним kill-switch для ввімкнення меінтенансу, який вмикав/вимикав доступ до сервісів одразу всім користувачам. До гнучкої системи з набору правил з пріоритетами з гранулярністю від країни, штату до окремого користувача. Від редагування через базу даних до панелі адміністратора та автоматизованих змін залежно від подій в системі. А також розповім про actions - комбінацію фіча тоглів та правил бізнес-логіки для динамічного інтерфейсу клієнтів на основі доступних дій користувачу.

.NET Fest 2019. Сергій Бута. Feature Toggles: Dynamic Configuration at Wirex

NETFest

GraphQL is a great way to expose your APIs and it has changed the way we think about consuming data over HTTP. With GraphQL we want to have one schema that provides all the data to us in a consistent way, enabling us to drill into the graph and fetch with one request what we actually want instead of having to issue multiple requests. In the real world, however, we more often build small services that serve certain use cases. Simpler services are easier to maintain and can be deployed more rapidly. Moreover, we often also want to use external services that are not built by us. Ultimately, we will end up with multiple APIs again. The solution for this dilemma is schema stitching. This talk will explore the schema stitching capabilities on ASP.Net Core with Hot Chocolate. We will show how you can set up a Hot Chocolate GraphQL gateway in under 5 minutes and move on to the various stitching scenarios. This talk introduces simple auto-stitching scenarios and goes on to demonstrate how you can rewrite your GraphQL APIs into something truly new.

.NET Fest 2019. Michael Staib. Hot Chocolate: GraphQL Schema Stitching with A...

NETFest

В этом выступлении Андрей расскажет о внутренностях базового сервиса, написанного с использованием паттерна CQS, который обрабатывает входящие запросы команд и публикует события, описывающие переходы состояния системы. После этого он опишет общие способы тестирования такого сервиса и объяснит плюсы и минусы существующих подходов. Затем он расскажет про AutoFixture и покажет, как она может сделать тесты намного чище, а конфигурацию - более удобной, путем инъекции параметров в метод теста, объяснит существующие проблемы с инициализацией и очистке данных в асинхронных тестах и покажет, как с этим справляться с помощью некоторой легковесной интеграции между xUnit и AutoFixture.

.NET Fest 2019. Андрей Литвинов. Async lifetime tests with xUnit and AutoFixture

NETFest

.NET Fest 2019. Анатолий Колесник. Love, Death & F# Tests

NETFest

Все когда-либо писали парсеры, но многие так и не знают как спарсить HTML без регулярных выражений. Очень длительное время концепция парсинга языков с рекурсивной грамматикой для меня была черной магией, а люди которые занимаются разработкой компиляторов и предметно-ориентированных языков вовсе казались волшебниками. Но это оказалось не так и сложно. В моем докладе я хочу вам рассказать о том что такое парсеры в целом, зачем они нужны и какие они бывают, а самое главное -- покажу как перейти от традиционных методик их написания к более удобному и понятному функциональному способу. В ходе презентации мы также напишем рабочий JSON парсер в качестве proof of concept.

.NET Fest 2019. Алексей Голуб. Монадные парсер-комбинаторы в C# (простой спос...

NETFest

Believing it is the most powerful PaaS service of the entire public cloud, I will share with you all the most interesting features of App Service and the good tips from the field, to see how to properly use it in production and focus on applications, instead of governance. I will dig into the architecture, the deployment options, the runtimes, the secrets management, logging and troubleshooting and into some advanced high-scale scenarios. If you never used this, you will say ""ok, how did I survive without it?"".

.NET Fest 2019. Roberto Freato. Azure App Service deep dive

NETFest

The majority of companies are struggling with an issue of growth where they started from handful group of people and reached 1000+ employees. In case of small groups the relationships remind family’s connections so everyone knows each other personally and the atmosphere is warm and charm whereas starting from 500+ to 1k keep it as family is tough and most of the companies come up with processes on one hand and culture on other. There ain’t no silver bullet how to manage it and in the end of the day they are balancing working a lot about good atmosphere in company and setting up relationships between teams. The issue isn’t new however tools and approaches evolved a lot this is where .NET Core and ML.Net comes in handy. These days AI/ML take over the world and bots as one of implementations are already a part of our life therefore our entuthiastic team created a bot using latest .NET Bot Framework v4 who helps managers to “measure” atmosphere in teams and crucial to socialize teams leveraging the power of ML.NET.

.NET Fest 2019. Александр Демчук. How to measure relationships within the Com...

NETFest

In this session we'll demonstrate how to bring dragons or any other 3D model to life using Microsoft's Azure Spatial Anchors, HoloLens and mobile phones. You will learn what is augmented reality, we will introduce you Hololens, we will teach you what is Azure Spatial Anchor, how they work and how you can use them in your apps. This cross-device experience might be usable for all kind of applications.

.NET Fest 2019. Anna Melashkina та Philipp Bauknecht. Dragons in a Mixed Real...

NETFest

You must have noticed how Docker and containers is playing a more and more important part in .NET development. Docker support is everywhere, so it should be easy to build solutions based on container technology, right? But, it takes a bit more to architect and create a .NET solution that use Docker at its core. Many questions arise: How do you design a solution architecture that fits well with containers? Would I use .NET or .NET Core? What is a proper way to migrate to such an architecture? What changes in the .NET implementation from pre-Docker solutions with micro-services? Where do container orchestrators fit in and how do I build and deploy my solutions on a Docker container cluster, such as Azure Kubernetes Service? These and many other questions will be answered in this session. You will learn how to design and architect your .NET solutions and get a flying start to create, build and run Docker-based containerized applications.

.NET Fest 2019. Alex Thissen. Architecting .NET solutions in a Docker ecosystem

NETFest

Serverless technology is trending, but in-depth details are missing. How does it fit with non-serverless components? What are the practical use cases? Should you fight vendor lock-in? And what about limits and pitfalls with Azure? I will answer those questions, share a few tricks and short demo. I'll cover serverless usage scenarios with Azure, what problems can be solved, and what is a viable adoption strategy. Then I'm going to talk about technology shortcomings, when to omit it and how to rip all benefits. There are circumstances when a cloud-agnostic approach is beneficial, so I discuss serverless frameworks too and why vendor lock is not that bad. Finally, we'll look at a short demo that illustrates why you have to use specific serverless patterns.

.NET Fest 2019. Stas Lebedenko. Practical serverless use cases in Azure with ...

NETFest

Do you recall those buzz words like TDD, BDD? Yep, but we know their problems as well! TDD is too granular. BDD is too coarse-grained. Unit tests are too chatty. BDD is too abstract. TDD requires knowledge of implementation details. BDD does not care about implementation at all. What is in the middle? Integration tests. Let's be Integration driven then! OK, then how to build infrastructure to run Integration tests? Should we start with IaaS first? How to speed up the development and take into account non-foundational requirements like scaling, security borders, isolation, etc. from the very beginning? To answer the questions, we would combine Integration test-based development with serverless (AWS) to solve a typical business task. Based on the example, we would show how to create a solid foundation for further refactoring/refining of the overall solution and concreting it with Unit tests. Acceptance tests would be left for home exercise ;)

.NET Fest 2019. Сергей Медведев. How serverless makes Integration TDD a reali...

NETFest

Задачи по обработке естественного языка сейчас встречаются практически в любом проекте. К сожалению, до недавнего времени, платформа .NET не сильно подходила для решения подобных задач. С выходом ML.NET ситуация стала меняться к лучшему, но все еще далека от идеала. На этом докладе я расскажу про основные задачи, которые решаются методами Natural Language Processing и какие существуют способы решения этих задач на платформе .NET (сервисы, библиотеки, фреймворки).

.NET Fest 2019. Сергей Корж. Natural Language Processing in .NET

NETFest

A Public Key Infrastructure (PKI) is the basis of modern system authentication; X.509 certificates are at the core of modern cryptography. Building your own PKI is not for the faint of heart, so we usually buy our certificates from an external Certificate Authority or operate a 3rd-party off-the-shelf PKI. But what can you do if you need to issue your own certificates while keeping your costs low? What if, for example, you're in the business of manufacturing millions of IoT devices and you need to issue a certificate to each and every one of them? And to top it off - you want to do it in a Serverless manner? Join me in this session, as we build a Serverless PKI system with Azure Functions & Key-Vault and learn all about Key-Vault's capabilities in regards to X.509 certificates along the way.

.NET Fest 2019. Eran Stiller. Create Your Own Serverless PKI with .NET & Azur...

NETFest

For the past couple of years it seems that Microservices is all the rage. We want to use Microservices, we want to decompose into Microservices and we want Microservices to be a part of our world. While modern tools and platforms such as Docker, Kubernetes, Service Mesh and the public cloud help in implementing and maintaining such systems, the reality is that many fail even before the first line of code was written. This can happen for many reasons; Perhaps you chose a Microservices architecture for the wrong reasons? Maybe the organization wasn't ready for it? Or just possibly - the proposed architecture didn't embrace the true meaning of Microservices? As the CTO of a software services company I get tackle these questions a lot. Join me in this session as I provide my perspective on transitioning from Monolith to Microservices through lessons learned in the real world, while architecting and implementing multiple Microservices based software systems at various customers.

.NET Fest 2019. Eran Stiller. 6 Lessons I Learned on My Journey from Monolith...

NETFest

Mais de NETFest (20)