Microsoft Announces Preview of OpenAPI Specification V3 in Azure … – InfoQ.com

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Back to login

Back to loginThomas Dullien discusses how language design choices impact performance, how Google’s monorepo culture and Amazon’s two-pizza-team culture impact code efficiency, and why statistical variance is an enemy.This article describes the journey of the migration towards a Federated GraphQL architecture. Specifically, it shows the GraphQL platform Netflix has built consisting of the Domain Graph Services framework for implementing GraphQL services in Java using Spring Boot and graphql-java, and tools for schema development. It also describes how the ecosystem has evolved at various stages of adoption.Neha Pawar discusses how to query data on the cloud directly with sub-seconds latencies, diving into data fetch and optimization strategies, challenges faced and learnings.Can they increase their flexibility? Can they increase their test coverage? Can they increase their efficiency? And is it possible to reduce their verification lead-time by 50%? One company challenged itself with these questions. This article explores two important “‘pillars”’ of their testing strategy: shifting left and using state-of-the-art techniques to support verification activities.Joe Duffy discusses the challenges (and solutions) met while running IaC and how that shapes the future of IaC.See what’s next in Large Language Model (LLM) architectures used in tools like ChatGPT.Learn what’s next in software from world-class leaders pushing the boundaries. Attend in-person or get video-only pass to recordings.Discover new ideas and insights from senior practitioners driving change in software. Attend in-person.Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.InfoQ Homepage News Microsoft Announces Preview of OpenAPI Specification V3 in Azure API ManagementThis item in japaneseJan 29, 2019 2 min readby Eldert GrootenboerRecently Microsoft has announced support for the OpenAPI specification v3 in Azure API Management, which is their service that enables the set up, publishing, monitoring and maintainence of APIs. Support of the OpenAPI specification has been implemented through the OpenAPI.NET SDK and allows the abstraction of the definition of APIs from their implementation.The OpenAPI specification, previously known as Swagger, provides the means to describe RESTful web services in a language independent way. As OpenAPI is widely adopted, a diverse ecosystem is available with tools for designing, documenting, building, testing and implementing governance. The specification gets overseen by the OpenAPI Initiative, owned by the Linux Foundation, and has a wide variety of organizations driving its development, including companies such as SmartBear, Microsoft, and WSO2. Anyone can follow or even contribute to the development of the specification on the GitHub repository of the OpenAPI Initiative.According to Tom Kerkhove, Microsoft Azure MVP and Azure Architect, the specification has an important role when exposing APIs to their consumers.Providing clean and well-documented APIs is a must. This allows your consumers to know what capabilities you provide, what they are for and what to expect. This is where the OpenAPI specification, aka Swagger, comes in and defines how APIs should be defined across the industry, regardless of what technology is underneath it.Version 3 of the specification has brought several changes, and as such these are now also available for Azure API Management. For instance, this new version introduced a whole new architecture with components such as headers, links, and callbacks, taking a more modular approach in the definition, as described by Guy Levin, CTO at RestCase.Version 3.0 of the API specification format has taken a much more modular, and reusable approach to defining the surface area of an API, enabling more power and versatility when it comes to describing the request and response models, as well as providing details on the common components that make up API usage like the underlying data schema and security definitions.Another introduced option is to include callbacks to an operation, meaning it is now possible to describe webhooks for these. Finally, linking allows defining relationships between different paths of the APIs, providing the capability to expand on its attributes.Image source: https://blog.restcase.com/6-most-significant-changes-in-oas-3-0/Following the announcement, it is now possible to import OpenAPI v3 definitions in Azure API Management, albeit with some restrictions. Currently, this is possible through the portal or via the REST API. Subsequently, capabilities for exporting the OpenAPI descriptions are also available, either in the developer portal or using another call to the REST API.Source: https://azure.microsoft.com/en-us/blog/announcing-the-preview-of-openapi-specification-v3-support-in-azure-api-management/Eventually, before these capabilities will move into general availability, and it will also become possible to use the PowerShell SDK for doing both import and export of the definitions.

Writing for InfoQ has opened many doors and increased career opportunities for me. I was able to deeply engage with experts and thought leaders to learn more about the courses I covered. And I can also disseminate my learnings to the wider tech community and understand how the technologies are used in the real world.I discovered InfoQ’s contributor program earlier this year and have enjoyed it since then! In addition to providing me with a platform to share learning with a global community of software developers, InfoQ’s peer-to-peer review system has significantly improved my writing. If you’re searching for a place to share your software expertise, start contributing to InfoQ.I started writing news for the InfoQ .NET queue as a way of keeping up to date with technology, but I got so much more out of it. I met knowledgeable people, got global visibility, and improved my writing skills.Becoming an editor for InfoQ was one of the best decisions of my career. It has challenged me and helped me grow in so many ways. We'd love to have more people join their team.InfoQ seeks a full-time Editor-in-Chief to join C4Media’s international, always remote team. Join us to cover the most innovative technologies of their time, collaborate with the world’s brightest software practitioners, and help more than 1.6 million dev teams adopt new technologies and practices that push the boundaries of what software and teams can deliver!A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.You need to Register an InfoQ account or Login or login to post comments. But there’s so much more behind being registered.Get the most out of the InfoQ experience.Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.InfoQ.com and all content copyright © 2006-2023 C4Media Inc.Privacy Notice, Terms And Conditions, Cookie Policy

source

Creating a community for enterprise architecture professionals

Guest contributor | 07 August 2023

The world of enterprise architecture (EA) is continuing to evolve and as it does, the needs of its practitioners evolve too. That’s why Orbus Software has launched a new and improved community platform, OrbusNexus. 

As American author and business executive Seth Godin once said: “We don’t create a community by collecting people. They create a community by sharing purpose.” Inspired by this philosophy, the purpose of OrbusNexus is to provide a dynamic, engaging and collaborative space for EA professionals to connect, share and innovate together.  

The platform – which was built in collaboration with professional services provider Kaptius on ServiceNow – has been designed to enable like-minded EA experts to expand their networks, build valuable relationships, and learn from each other’s knowledge and experience. They believe in the power of collective intelligence and encourage users to actively participate in discussions, contribute valuable content and explore the wealth of resources available. 

OrbusNexus will also act as a collaboration hub. Enterprise architects from across the globe can engage in group projects, join specialised interest groups, and participate in hackathons and competitions that push the boundaries of what’s possible in the field of EA.  

On top of all that, the platform offers a user-friendly interface, powerful search capabilities, personalised content recommendations, and advanced networking tools. It’s a one-stop-shop where users can access exclusive resources, stay up to date with the latest industry trends, and explore new opportunities for professional growth. 

Enterprise architects aiming to advance their skills and build powerful partnerships can become part of this dynamic community here

Tim Mitchell is chief evangelist at Orbus Software 

This article was originally published in the Summer 2023 issue of Technology Record. To get future issues delivered directly to your inbox, sign up for a free subscription 

Exploring Yale’s role in the time-bending nature of modern architecture

Throughout much of the 20th century, a unique interdisciplinary conversation unfolded at Yale concerning the role of time and history in modern art and architecture.

It was an ongoing discussion among artistic and intellectual heavyweights. Key participants included architects Louis Kahn, Everett Victor Meeks, James Gamble Rogers, Paul Rudolph, and Eero Saarinen; artists Anni and Josef Albers; philosopher Paul Weiss; and art historians Henri Focillon, George Kubler, Sibyl Moholy-Nagy, and Vincent Scully. All resisted the notion that modern art and architecture must be of its time and forward looking.

“Untimely Moderns: How 20th Century Architecture Reimagined the Past” (Yale University Press), the latest book by Eeva-Liisa Pelkonen, professor and assistant dean at Yale School of Architecture, explores this wide-ranging conversation, examining the figures involved and their roles in shaping modern art and architecture.

Pelkonen recently spoke to Yale News about the book and the “time-bending” quality of the architecture that makes the university’s campus unique. The interview has been edited and condensed.

Eeva-Liisa Pelkonen: The book’s key point, as the title suggests, concerns modern architecture’s unsettled and at times tortuous relationship to time and history. There is an idea that being modern in art and architecture requires living in the present and looking towards the future, but I discovered through my research that many of the modern architects of the 20th century were quite preoccupied with the past, to the point that their questions challenged the linear view of historical time.

Imagine how it must have felt to enter the phantasmagoric curvy interior of the Ingalls Rink upon its completion in 1958! Architecture’s time-bending power is quite magical.

Eeva-Liisa Pelkonen

My argument rests on this notion of temporal disorientation, which involves the somewhat paradoxical idea that imagining the future requires reimagining the past. The individuals at the center of the story all shared a penchant for conflating the past, present, and future in their work.

Pelkonen: The setting is somewhat autobiographical. I came to Yale 30 years ago and was flabbergasted by the Gothic architecture of the residential colleges and the library designed by James Gamble Rogers. And after seeing the date on the Sterling Law Building, I was completely taken aback that these buildings were built in the 1920s and early 1930s.

I came to Yale from my native Finland via Austria, and in both of those countries 20th-century architecture was marked by looking forward, almost to the point where the past was never discussed. So I was surprised to find out that some 20th-century Americans were so transfixed by tradition. If you look at even buildings that were built in the mid-century, like Louis Kahn’s addition to the Yale University Art Gallery and Paul Rudolph’s Art and Architecture Building, now Rudolph Hall, they have a time-bending quality that makes them difficult to date. For example, the fortress-like concrete exterior of Rudolph Hall hides a polychromatic interior filled with plaster cast copies of ancient Babylonian, Egyptian, and Greek artworks.

It has taken me a long time to accept that architecture can bend time and act as a temporal medium in a way that makes us think about time and history in a different way. In a way, when you walk the Yale campus, you’re exposed to architecture’s time-bending power; one that allows one to remove oneself from current historical time and inhabit a kind of Ersatz-reality with alternate temporal coordinates. Entering the Sterling Memorial Library still feels like traveling to the past. But then, some buildings work the other way, too, as they allow us to imagine new realities, even new futures. Imagine how it must have felt to enter the phantasmagoric curvy interior of the Ingalls Rink upon its completion in 1958! Architecture’s time-bending power is quite magical.

Pelkonen: After he began teaching at Yale in 1947, Kahn rejected the modernist dogma that architectural spaces should be created with specific functions in mind, which was a way to anchor architecture in contemporaneous notions of use. He believed that architectural space should transcend time and enable future uses. Similarly, he celebrated how platonic forms — triangles, circles, and cubes — embody a sense of eternal time. In his mind people come and go, functions change, but the architectural spaces and forms remain.

Kahn and many of his contemporaries started thinking about architecture this way after visiting Rome and seeing buildings like the Pantheon that have been used through millennia for different purposes. Thinking through the long duration of architecture was very important to him. He was also greatly influenced by the philosopher Paul Weiss’s teachings about the experience of time and adopted the idea about the presence of the past from his writings.

Pelkonen: I start the story in the early 1920s when Everett Victor Meeks — who was the dean of the School of Art at the time — made art and architecture part of a humanities-based liberal arts education. In doing so, he showed that the arts concern larger questions that implicate the humanities and made the study of architectural history mandatory for architecture students. He also built the framework that combined art and architecture into an interdisciplinary conversation. That was very important because it allowed artists, architects, writers, and historians to have conversations about big questions, such as architecture’s relationship to time and history.

The individuals at the center of the story all shared a penchant for conflating the past, present, and future in their work.

Eeva-Liisa Pelkonen

During his tenure Yale expanded its art gallery, which became a lively center for the debate surrounding modern art and architecture in the 1930s and 40s. Subsequently, starting in the late 1940s, Yale began hiring modernists like Kahn and Josef Albers, who is another crucial character in this story, along with his wife, Anni.

The Albers had met at the Bauhaus, which was interesting in how it combined crafts with the fine arts. They think of the Bauhaus as this trailblazing avant-garde institution – modern and forward looking — but Josef and Anni were not interested in newness at all! On the contrary, they were very interested in establishing transhistorical and universally valid foundations for art. Joseph Albers, of course, famously taught the foundations course at the Yale School of Art. The idea of “foundations” was significant in that it assumed that art and architecture are based on time-tested, medium specific principles. Also, their work and words came to have a profound impact on Kahn.

Pelkonen: Henri Focillon, a prominent French scholar of medieval art, came to Yale from the Sorbonne in 1933 to teach a two-year course at the School of Fine Arts [which over the next few decades morphed into independent schools of art, architecture, and drama] on “the history and criticism of art.” He remained on the faculty until his death in 1943 and was instrumental in founding the Department of the History of Art [which is now part of Yale’s Faculty of Arts and Sciences]. Focillon helped establish art historical formalism — the idea that art be unmoored from historical time, that there’s something eternal and timeless at its center, and that form transcends time and has its own temporal framework — as a tenet of the teaching of art history at Yale.

Two of his disciples, George Kubler and Vincent Scully, would have long and celebrated scholarly careers at Yale. These three figures — Focillon, Kubler, and Scully — form the intellectual backbone of my book’s story through their advocacy of art historical formalism.

Pelkonen: In my mind, Scully’s contribution was to infuse art historical formalism with psychoanalytic theory. He believed that all great architecture was a symbolic act, that is a product of an eternal existential strife. The architects he loved, like Kahn and Frank Lloyd Wright, grappled with big themes of human existence, like the eternal quest for shelter, through the archetypal forms they created.

Scully radically unmoored architecture from its historical context and never cited dates in his lectures or books. This allowed him to reach the conclusion that the people who built the Mayan temples and the 20th-century architect Robert Venturi grappled with the same existential questions because they both used the geometric form of the triangle in their work. Scully believed that deciphering architecture in this manner could provide cure for the ills that humanity was facing. His references to caves, for example, were indicative of the existential threat that plagued the post-atomic era.

All in all, Scully believed that they should study the past for the same reason that psychoanalysts mine people’s pasts: it’s where the causes and cures of their troubles lie. They should want to revisit the past so that they can cure their current condition. He saw himself as a historian, who like a psychoanalyst, helps architects to decipher their own work. He also saw that architects who were unable to come to terms with the past were experiencing some sort of repression that they could overcome through the insights of a historian. Subsequently, he helped two generations of architects and architecture students reimagine the past through his half-a-century-long teaching career.