John David

John David

1563513326

Microfrontends — Connecting JavaScript frameworks together (React, Angular, Vue etc)

Like most things in life, a variety of choices informs a toxic culture of mine is better than yours and you’re wrong and I’m right.

Since technology advancements have got us in this mess, is there any chance it could get us out of it as well?

Enter Microfrontends…

Introduction to Microfrontends

Modern UI development regardless of your framework has became all about component composition: You adapt to a framework’s way of doing things by following their patterns and conventions to create components usually underpinned by some sort of data model usually in the form of a service or state object.

For example: Angular has a strong opinion on how everything should be architected in the frontend. React although it only deals with components has a huge ecosystem backing it driven by a community of React-centric developers.

**Microfrontends **have gathered huge momentum recently as away of allowing multiple teams to work on a single UI using multiple frameworks, but could it really change the landscape of UI development?

In this article, I am going to spend some time looking at the SDLC (software development lifecycle) and the advantages of adopting such an architecture.

Where’s the problem?

The current trend in UI development, is to build a feature-rich and powerful browser application (single page application) using a chosen framework.

Development results in building lots of little components which are then bundled together in some sort of build process using something like webpack or rollup.

Over time the UI layer often developed by separate or multiple teams, grows and gets more difficult to maintain creating a huge monolithic frontend.

Monolithic frontend SDLC

Monolithic frontends deployment architecture

Reversing the microservice anti-pattern:

Microfrontends looks at removing that monolithic build step, and results in completely decoupled services that can be independently built and deployed:

Microfrontend SDLC

Microfrontend deployment architecture

Now our UI architecture has all the qualities of traditional microservices:

  • Highly maintainable and testable
  • Loosely coupled
  • Independently deployable
  • Organised around business capabilities

How could this bring the big frameworks together?

Since we have decoupled our UI components into many microfrontends, we no longer have to dictate which framework each component uses.

The below illustration shows how we could potentially have different application teams using different technologies to create their independently built and released microfrontend:

SDLC using multiple frameworks

There are **several ways **to solve this using technologies but let me illustrate one example:

  1. **Develop: **Three teams using a different JavaScript framework for each microfrontend
  2. Build: Wrapping their microfrontend components as web components*** ***and building their project as a JavaScript file
  3. Release: A single JavaScript file is released inside a docker container served using Ngnix

Once we have released our microfrontends, we should compose them together in a single UI layer. The communication between the microfrontends should be handled by the composition layer which should have a well defined contract.

Deployment architecture using multiple frameworks

From a user perspective they access a single application, but the developer’s ability to solve a problem is no longer limited by what single framework the application uses.

Thanks for reading

If you liked this post, please do share/like it with all of your programming buddies!

Follow us on Facebook | Twitter

Further reading about JavaScript

The Complete JavaScript Course 2019: Build Real Projects!

Vue JS 2 - The Complete Guide (incl. Vue Router & Vuex)

JavaScript Bootcamp - Build Real World Applications

The Web Developer Bootcamp

New ES2019 Features Every JavaScript Developer Should Know

Best JavaScript Frameworks, Libraries and Tools to Use in 2019

Top 50 Interview Questions for JavaScript Developer

Vue.js Tutorial: Zero to Sixty

React vs Angular vs Vue.js by Example

Build a Basic CRUD App with Vue.js and Node

#javascript #web-development #angular #reactjs #ember-js #vue-js #webpack #npm #jquery

What is GEEK

Buddha Community

Microfrontends — Connecting JavaScript frameworks together (React, Angular, Vue etc)
Autumn  Blick

Autumn Blick

1598839687

How native is React Native? | React Native vs Native App Development

If you are undertaking a mobile app development for your start-up or enterprise, you are likely wondering whether to use React Native. As a popular development framework, React Native helps you to develop near-native mobile apps. However, you are probably also wondering how close you can get to a native app by using React Native. How native is React Native?

In the article, we discuss the similarities between native mobile development and development using React Native. We also touch upon where they differ and how to bridge the gaps. Read on.

A brief introduction to React Native

Let’s briefly set the context first. We will briefly touch upon what React Native is and how it differs from earlier hybrid frameworks.

React Native is a popular JavaScript framework that Facebook has created. You can use this open-source framework to code natively rendering Android and iOS mobile apps. You can use it to develop web apps too.

Facebook has developed React Native based on React, its JavaScript library. The first release of React Native came in March 2015. At the time of writing this article, the latest stable release of React Native is 0.62.0, and it was released in March 2020.

Although relatively new, React Native has acquired a high degree of popularity. The “Stack Overflow Developer Survey 2019” report identifies it as the 8th most loved framework. Facebook, Walmart, and Bloomberg are some of the top companies that use React Native.

The popularity of React Native comes from its advantages. Some of its advantages are as follows:

  • Performance: It delivers optimal performance.
  • Cross-platform development: You can develop both Android and iOS apps with it. The reuse of code expedites development and reduces costs.
  • UI design: React Native enables you to design simple and responsive UI for your mobile app.
  • 3rd party plugins: This framework supports 3rd party plugins.
  • Developer community: A vibrant community of developers support React Native.

Why React Native is fundamentally different from earlier hybrid frameworks

Are you wondering whether React Native is just another of those hybrid frameworks like Ionic or Cordova? It’s not! React Native is fundamentally different from these earlier hybrid frameworks.

React Native is very close to native. Consider the following aspects as described on the React Native website:

  • Access to many native platforms features: The primitives of React Native render to native platform UI. This means that your React Native app will use many native platform APIs as native apps would do.
  • Near-native user experience: React Native provides several native components, and these are platform agnostic.
  • The ease of accessing native APIs: React Native uses a declarative UI paradigm. This enables React Native to interact easily with native platform APIs since React Native wraps existing native code.

Due to these factors, React Native offers many more advantages compared to those earlier hybrid frameworks. We now review them.

#android app #frontend #ios app #mobile app development #benefits of react native #is react native good for mobile app development #native vs #pros and cons of react native #react mobile development #react native development #react native experience #react native framework #react native ios vs android #react native pros and cons #react native vs android #react native vs native #react native vs native performance #react vs native #why react native #why use react native

Ollie  Dietrich

Ollie Dietrich

1632083580

Comprehensive Look At Angular, React and Vue.js

There is no doubting the fact that web development and custom software development has been on a thriving technological ride in previous times several years. And when it comes to the frontend, JavaScript has been at the helm of this drive.

 

This popularity has given increase to tons of JavaScript frameworks along the way. Deciding on a JavaScript framework for your web app can be overwhelming. Angular and React are very well-known these days, and there is a younger which has been getting a lot of traction lately: VueJS.

The aim of this video is to take a comprehensive look at such widely used frameworks – #Angular and #Vue – and one library – #React.

And also share your opinions on these three in the comment section.

 #javascript #angular #vue #react-native 

John David

John David

1563513326

Microfrontends — Connecting JavaScript frameworks together (React, Angular, Vue etc)

Like most things in life, a variety of choices informs a toxic culture of mine is better than yours and you’re wrong and I’m right.

Since technology advancements have got us in this mess, is there any chance it could get us out of it as well?

Enter Microfrontends…

Introduction to Microfrontends

Modern UI development regardless of your framework has became all about component composition: You adapt to a framework’s way of doing things by following their patterns and conventions to create components usually underpinned by some sort of data model usually in the form of a service or state object.

For example: Angular has a strong opinion on how everything should be architected in the frontend. React although it only deals with components has a huge ecosystem backing it driven by a community of React-centric developers.

**Microfrontends **have gathered huge momentum recently as away of allowing multiple teams to work on a single UI using multiple frameworks, but could it really change the landscape of UI development?

In this article, I am going to spend some time looking at the SDLC (software development lifecycle) and the advantages of adopting such an architecture.

Where’s the problem?

The current trend in UI development, is to build a feature-rich and powerful browser application (single page application) using a chosen framework.

Development results in building lots of little components which are then bundled together in some sort of build process using something like webpack or rollup.

Over time the UI layer often developed by separate or multiple teams, grows and gets more difficult to maintain creating a huge monolithic frontend.

Monolithic frontend SDLC

Monolithic frontends deployment architecture

Reversing the microservice anti-pattern:

Microfrontends looks at removing that monolithic build step, and results in completely decoupled services that can be independently built and deployed:

Microfrontend SDLC

Microfrontend deployment architecture

Now our UI architecture has all the qualities of traditional microservices:

  • Highly maintainable and testable
  • Loosely coupled
  • Independently deployable
  • Organised around business capabilities

How could this bring the big frameworks together?

Since we have decoupled our UI components into many microfrontends, we no longer have to dictate which framework each component uses.

The below illustration shows how we could potentially have different application teams using different technologies to create their independently built and released microfrontend:

SDLC using multiple frameworks

There are **several ways **to solve this using technologies but let me illustrate one example:

  1. **Develop: **Three teams using a different JavaScript framework for each microfrontend
  2. Build: Wrapping their microfrontend components as web components*** ***and building their project as a JavaScript file
  3. Release: A single JavaScript file is released inside a docker container served using Ngnix

Once we have released our microfrontends, we should compose them together in a single UI layer. The communication between the microfrontends should be handled by the composition layer which should have a well defined contract.

Deployment architecture using multiple frameworks

From a user perspective they access a single application, but the developer’s ability to solve a problem is no longer limited by what single framework the application uses.

Thanks for reading

If you liked this post, please do share/like it with all of your programming buddies!

Follow us on Facebook | Twitter

Further reading about JavaScript

The Complete JavaScript Course 2019: Build Real Projects!

Vue JS 2 - The Complete Guide (incl. Vue Router & Vuex)

JavaScript Bootcamp - Build Real World Applications

The Web Developer Bootcamp

New ES2019 Features Every JavaScript Developer Should Know

Best JavaScript Frameworks, Libraries and Tools to Use in 2019

Top 50 Interview Questions for JavaScript Developer

Vue.js Tutorial: Zero to Sixty

React vs Angular vs Vue.js by Example

Build a Basic CRUD App with Vue.js and Node

#javascript #web-development #angular #reactjs #ember-js #vue-js #webpack #npm #jquery

Top 15 Free JavaScript Frameworks for Web Applications

List of some useful JavaScript Frameworks and libraries for website, web apps, and mobile apps development, that developers should know about to make selection easier.
This article will help you understand the various types of JavaScript Framework available in the market. When it comes to choosing the best platform for you, it’s not only the number of features you need to consider but also its functionality. The ease with which it fits within your project is also an essential factor. The next step is to choose the framework that best fits your company requirements or you can select the best from the list of top web development companies to develop your product based on your requirements.

#javascript frameworks for web applications #web applications development companies #progressive javascript framework #javascript frameworks #javascript #frameworks

Nico Jonsson

Nico Jonsson

1604627940

Which Javascript Framework should I use with Ionic - Angular, React or Vue?

You want to get started with Ionic and are unsure which Javascript framework with Ionic you should pick? Or do you think about switching from the one you currently use?

In this video I explain the differences and things you need to think about when selecting your framework for Ionic!

Learn Ionic faster with the Ionic Academy: https://ionicacademy.com/

#ionic #angular #react #vue #javascript