AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 11.10.2019, 12:11   #1  
Blog bot is offline
Blog bot
Участник
 
22,471 / 774 (70) +++++++
Регистрация: 28.10.2006
msdynamicsworld: Errors and exceptions in the cloud: The business case for adopting containers and CI/CD on Microsoft Azure
Источник: https://msdynamicsworld.com/story/er...icrosoft-azure
==============

No matter which cloud environment you find yourself using, you need to consider how to solve application and networking issues. In the past, I wrote exceptions to log files so that I could analyze any problems that users reported. Later in my career, applications evolved from front-end architectures with a backend database—a Client Server Architecture--to a multi-tiered architecture with middleware servers in the middle. This new way of working with apps meant we had to log to a database in order to capture all of the events from all of the components.

Suddenly we had web service events, middle tier events for middleware, and database events. How do we relate all of these logged items together so we see a holistic view of the issue and solve it?

We recorded each call with a unique identifier that was common across all the processes. We would then search for the first exception, obtain the correlated unique identifier and any other records with the same unique identifier. This unique identifier is known as a "CorrelationID." In this article, I'll take a look at a few of the different ways to handle these issues as they crop up.

Microservice challenges for error and exception handling

In today's cloud environments, we have microservices, or small services that are very specific to the company's application requirements. These are often deployed in serverless containers such as Kubernetes or Docker, which are used to standardize items common to all applications such as error or exception handling. They log errors in the containers in a specified format and location. This allows the group that monitors apps to see all application information from across the containers in one convenient location.

Containers are built to operate on machines in all environments, including your local departmental servers, centralized data centers, and all of the major clouds. Thanks to this flexibility, the people in your organization can see all environments and all issues in one set of screens and alerts. This helps tremendously in issue resolution and gaining a deep understanding of what the issues are. In fact, it can even be used as a learning tool to prevent issues in the future.

<h2>Application and Development Operations (DevOps)


Источник: https://msdynamicsworld.com/story/er...icrosoft-azure
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 11:52.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.