header_home_wuerfel_1920px.jpg

Successful with the Cloud

Florian van Keulen, Senior Solution Manager Application Development, Trivadis AG

The IT industry is currently being marked out by changes that probably better deserve the name "upheaval" and are often more or less a revolution. The migration of swathes of solutions into the Cloud is one of them. Strategic and solution-oriented consulting is a central success factor in this journey. Focusing on best practices and a tool-supported methodology is the best solution to convince all stakeholders of the added value provided by the changeover right from the start.

 

 Trivadis Cloud Assessment Prozess

 

A successful cloud migration starts with an extensive cloud assessment

For this purpose Trivadis and Dynatrace have jointly developed a range of solutions that are based on a structured assessment of the existing IT environment for the initial step. This permits optimal migration candidates to be identified in advance and prioritised for planning.

 

Trivadis Dynatrace Insights-Sicht: Darstellung der Abhängigkeiten eines Systems

Insight view, interdependencies of a system for the prioritisation of migration candidates


Before the actual migration itself, the status quo is determined. With the aid of synthetic monitoring, Dynatrace determines how the application (as well as the infrastructure) is currently – i.e. before the Cloud migration – is perceived from the viewpoint of the end-user. This is not just a snapshot, but rather a thorough observation of response time behaviour and availability. In an ideal case, this would begin several months before the actual migration.

New Call-to-action

In practice: New services in the Cloud

A move to the Cloud often means that the migrated applications must be restructured – especially when the solution is only partly migrated, for example for security reasons. This does not necessarily have to mean complete rebuild of an application, it is often only about extending the existing application with new relevant components or a retrofit for modularisation purposes.

Here is an illustrative practical example: a supermarket chain replaces its conventional customer card with an app. As well as the previous uses of this customer card, the app should offer further functionality such as payment of the display of relevant offers. In this scenario, the cashpoint systems and many other already established services continue to run in the supermarket chain's own computing centre. However, those services that must always be available and that are dynamically upscaled and downscaled depending on load, are housed right from the start in the Cloud.

Dynatrace also ensures that various eco-systems can be placed on their own user interface. An optimal solution, because in the scenario described above, the computing centre runs on VMware, while Microsoft Azure is used as the Cloud platform. Both solutions do indeed offer mature dashboards, but the challenge is in displaying the relationships and mutual interactions.

Overview, from datacentre to applications

Overview, from datacentre to applications

Splitting up existing services

Quite apart from the first example, it is important to uprate existing applications and services to meet current requirements. If, for example, a monolithic legacy application has to be migrated to the Cloud, this will very probably require fundamental reconstruction with regards to scalability and sustainability in order to really profit from its new location.

Particularly if this is being undertaken for the first time, the question quickly arises of what should be done if confronted with a monolith?

A "what if" scenario is the best option for this. Marking different entry points, for example analysing load behaviour, is a further strength of Dynatrace. Custom Services allow individual classes of a monolith to be examined as if these were already independent micro-services. In this way it can be quickly seen whether the load distributes itself as expected or whether really only those components intercommunicate that are allowed to in accordance with the architecture definitions.

Where am I?

The start is marked using synthetic monitoring and also a retrospective analysis of the results of the migration is possible. How does it behave, however, during the migration? How does one know where one is? Which services are migrated, which not yet? How much load has already migrated to the Cloud?

There are many tools available to answer these questions, but each one of them only handles a specific sub- segment. Dynatrace integrates all these functions under one umbrella. PureStack shows which services are already running in the Cloud. Service Flow delivers call tracing in the style of AWS X-Ray or Zipkin, but does so in a cross-technology manner and also includes traffic from the browser through to the database.

Trivadis Dynatrace: Clarity due to cross-technology call tracing


Clarity due to cross-technology call tracing

All-inclusive monitoring

Dynatrace offers not just tools, it is also a partner of the largest platform and technology providers. Explicit support of platforms such as Azure, AWS, OpenStack, Docker, OpenShift or CloudFoundry permit all-inclusive monitoring. Both the infrastructure and the applications are jointly focused on. In this way, mutual interactions between the changing platforms and application rollouts can be completely identified at any time. The result is a powerful package.
Find out more details on the range of solutions for Cloud migration from Trivadis and Dynatrace in the Trivadis presentation "Successful with the Cloud" at the Dynatrace Perform Day on July 4, 2017 in Zurich. You can register for the event via the following link: Perform Zürich 2017.


More Information:

 

Topics: Cloud Computing