In this example, the marketing team was decoupled from the team building the Bit.dev web platform. This team works in a different codebase, releases changes through its own decoupled build pipeline, and can constantly deliver incremental upgrades.Įach team builds its components, with the flexibility to split vertical ownership by features etc, in their own smaller and decoupled codebase. They use Bit to independently version, build, test, package, and publish each of their components. They use the bit.dev platform to host and expose components to other teams, so they can integrate and collaborate.Įvery team at Bit enjoys a similar workflow. All teams work together to share and integrate components with each other, without stepping on each other’s toes. Close to 100% of the components written in our codebase are shared and reused, including not only front-end components, but also many other aspects of our system, such as “Search” features, “Playground” features, and even certain fullstack features that include both frontend and backend functionalities. KPIs and benchmarking we took for ourselves and for other teams show a variety of positive things happening when adopting this component-driven design. For example, the number of releases can go up by as much as 30X(!), the time spent on integrations is cut by over 50%, the composition of new features becomes a matter of hours or days, and even on-boarding new developers can become a simple matter of hours instead of weeks. You can hear more about this change and what it can do for a fast-growing start-up first-handed at this great episode of the HeavyBit JAMStack podcast. Source: This wonderful article by Cam Jackson In recent years, microservices allowed backend architectures to scale through loosely coupled codebases, each responsible for its own business logic and exposes an API, each independently deployable, and each owned and maintained by a different team. This paradigm provides great advantages to help accelerate, scale, and make the development process more efficient. The idea of micro front-ends is to bring the same advantages to the modern development workflow. Npm run build -configuration productionġ The above table is not meant to be an exhaustive list of frameworks and libraries that work with Azure Static Web Apps.It means breaking down monolithic projects into smaller, more manageable pieces, which are independently developed and owned by respective teams, with the power to build and ship simultaneously. If you do not include an, remove the trailing slash. The intent of the table columns is explained by the following items:Īpp artifact location (output location): Lists the value for output_location, which is the folder for built versions of application files.Ĭustom build command: When the framework requires a command different from npm run build or npm run azure:build, you can define a custom build command. The following table lists the settings for a series of frameworks and libraries 1. The Azure Static Web Apps requires that you have the appropriate configuration values in the build configuration file for your front-end framework or library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |