Skip to content

Software Engineering Blog

Three Ways to Solve CORS Issue in the Embed Swagger Page in Backstage

Embed-swagger-Cors-cover.jpg

As we mentioned in this article before, centralizing all the needed knowledge in one developer portal is a big improvement in daily working experience and convenience.

But we face a CORS problem when sending requests by an embedded swagger page in the API definition. this problem will significantly reduce the functionality of the Swagger page, so this article proposes three ways to solve it:

  1. allow the App to cross-origin for your Backstage domain
  2. provide modified plain-text open API JSON and add proxy
  3. change the server URL when rendering pages and add proxy

Easier, Flexible, and Lower Resource Cost Deployment Strategies by Feature Toggle

img.png

Having different deployment strategies is essential to ensure that the new version of the software is delivered to users in an efficient and robust way. After reading other articles, we can organize the following insight of deployment-strategies( If you are not familiar with deployment strategies, please see deployment-strategies or deployment-strategies-6-explained-in-depth to get a comprehensive explanation).

Centralize All Needed Knowledge in One Developer Portals Through Spotify Backstage

backstage_intro.jpg

A developer portal is designed to enhance the developer experience by uniting all the essential knowledge required for development, maintenance, monitoring, and more, into a single platform. Backstage fulfills this objective through its core features, which include:

  • Software catalog: This feature allows users to define relationships between systems, components, and APIs, while also providing API definitions.
  • Kubernetes: Backstage enables developers to check the health of target services within the Kubernetes cluster.
  • Software template: Backstage offers a variety of templates that empower developers to initiate new projects swiftly, incorporating all necessary implementations such as CI/CD templates, company policies, and guidelines.
  • TechDoc and Searching: Backstage integrates all relevant markdown documents, effectively centralizing them and eliminating scattering across GitHub README, company Wiki, company blog, etc.

The First Step Toward True Continuous Delivery

Run End to End Test in PR check by GitHub Action

true_cd_cover.png

This article will cover the first step for achieving True Continuous Delivery: How to gain more confidence when merging code into the main branch. The answer is always more tests, more specifically, more automated tests. Unlike the unit test, the E2E (End to End) test is more approximate to the real environment, which gives more confidence when it is passed.