We've been publishing the ThoughtWorks technology radar for just under ten years now. In that time we've seen changes in technology but also many things stay the same. The radar has given us a vehicle to discuss and absorb both the changes and the points of stability. We've been encouraged to see some new technologies become relevant and powerful, and sad to see some poor approaches reappear wearing different clothes. In this talk I'll highlight some of the changes as I contrast early radars with the later ones, with thoughts fresh in mind as we construct the 20th volume.

Readers familiar with the Technology Radar notice that we summarize some of our observations into themes, usually 3-5 per radar edition. But where do these themes originate? In this talk, I describe the dynamic nature of theme generation, which exemplifies the collaborative nature of the radar exercise itself, and how we sift through 200 blips to arrive at overarching technology themes.

When new technologies even the ground breaking one emerges, they were not always the clear winner. Hypers, myth, overly promising, and misunderstanding usually cloud the truth. We will encounter an aha! moment during the adoption when we understand better the tech. In this session I will examine some of them of few most important tech changes in the past 10 years.

In the last century, the era of dominance for a particular programming language was long - decades even. Even in the early part of this century, most new enterprise development was either in Java or in C#, with of course, significant COBOL code remaining in production. However, over the 20 editions of the radar, the introduction, and in some ways more surprisingly, the widespread adoption of new programming languages has become far more common. This talk will discuss the history and evolution of programming languages over the 20 editions of the radar, discussing the language features introduced, or re-introduced, as well as the language ecosystems.

For decades data storage & processing needs have been addressed by relational databases.But with exponential growth of data we are stretching the limits of these relational databases and we resort to solutions that can scale horizontally as the business grows. By doing so only a few of us realize that we have just embraced a distributed system and fail to see the complexity it brings. Though most of these projects start with an ambitious goal of redefining the data strategy they often fail to deliver the promise. In this talk I would like to highlight common mistakes and lessons learnt from real project experience. Whether you are thinking of starting a new data project or in the middle of one this talk would be of interest to you. However this talk is not a deep dive on any particular technology, it is intended to highlight trends & techniques so that you can make a better choices on your own.  

Finding ways to break data barriers among enterprises and build a unified data middleground has become a critical issue for the industry. Using the practical experience of several large enterprises, this presentation will share the following information: how to deal with the uncertainty of data innovation; how to formulate data investment and construction strategies; what challenges will data middleground construction face and how should we address them?

Continuous integration, delivery, and deployment allow quick iterations of software while maintaining high software quality. With broad applications of machine learning, services are becoming more personalized and customized. "Continuous Intelligence" defines a set of methods for rapid iterations and release of such services.

Digital Guide and accelerate your transformation journey using the Digital Mastermind from the Open ROADS Community, especially on skills, culture change, standards and platform Lessons learnt and best practices from successful digital transformation at Huawei and Huawei’s clients

Technology is often created to solve a specific problem in a certain context. With the popularization, promotation, hype and FUD, the connotation and extension of technology are constantly being generalized, becaming silver bullet that solves everything. This is the technology hype cycle in our industry. Technology radar first proposed the concept of microservices seven years ago for reflection on SOA; and seven years later we remain cautious about the widespread adoption of microservices for complexity of distributed system. This topic will trace the history of microservice from the perspective of technology radar, share the enduring principles and practices as well as lingering anti-pattern in distributed systems.

Since Alibaba announced its middle-end strategy, this concept has become a hot topic. While interacting with clients, I have discovered that companies in a diverse range of industries have begun developing digitized middle-ends, including those in the technology, finance, manufacturing, and real estate sectors. I would like to discuss China’s unique conception of online popularity. This primarily concerns the reasons that so many companies are pursuing a middle-end, the ideal elements of a corporate middle-end, and how TechRadar can support the digitization of middle-end. I would also like to discuss whether the digital era regards middle-end as a form of technology or a new method of digitized corporate management.

As the demand for personalized services and on-demand consumption continues to grow, traditional passive services and command-driven supply chains have become obsolete. Smarter IoT hubs have become a requirement in the optimization of closed-loop supply chains. Access to IoT network platforms has also become an inevitable pathway of transformation for corporate technical platforms. For this subject, we will examine typical examples of the development trends in IoT Hubs, analyze IoT hubs from a business angle, look at the functional requirements and basic structure of the IoT platform, and take a look at the factors that should be considered prior to building an online platform.

Architectures based on microservices have spread rapidly in the past few years. Organisations are drawn to the promise of independent evolvability, which allows to reduce cycle time and scale development. At the same time, in many software solutions the majority of the codebase is now running in the web browser, which leads to an often underestimated challenge: the software design of the frontends. All too often teams have well-structured services running on the servers but a big, entangled monolith in the browser. In this talk Erik describes a number patterns, proven in practical application, that allow teams to avoid the dreaded frontend monolith, and build software solutions that fully deliver on the promise of microservices.

Beyond screen design and front end development, incorporating UX concepts and practices when providing software solutions to our users is no longer a nice to have. In this talk we will show how UX concepts and practices have progressed in recent years, and how this has impacted the trajectory of digital technology. We will talk about how design has been incorporated into software development processes and how these two areas coexist in a symbiotic environment, which has served as a catalyst for evolving interactions. We will see how user experience design integrates with technology to build the right products, validate hypotheses through fast feedback cycles, and guides decisions for collecting analysis of the data. With the new capabilities that data analysis, conversational interfaces and other technological advances bring us, we are able to put users at the center of product development.   interactions and experiences continue to evolve, we will take a look at our current moment and the trends of what comes to us in this space.

The biggest difficulty of microservices does not lie in the complexity of development, but in the management of services. In this context, various tools such as "microservice platform" and "service mesh" try to handle problems with microservice management. However, none of these platforms or tools present sufficient expertise and practice in security. When thinking about microservice security, it is difficult to envision a clear concept. On one hand, the scope of security is complex and difficult to explain independently using the architecture. On the other hand, more practices of microservices are cloud-based. Many security practices can copy cloud security configurations, but there is still no universality of adaptation. This presentation will illustrate microservice practices from the perspective of security.

In the process of traditional enterprise service transformation, it faces a series of challenges, slow pace of service delivery, lack of technical talents, and insufficient experience in architecture governance. Apply service template in a reasonable way can effectively solve these problems. With the development of the software ecosystem, the service templates is also undergoing interesting changes. This sharing will take you to see how the service template is evolving.