Really great piece here. Although i should mention that flask-blueprints aren't standalone apps they are instead used to extend a single flask app into components (for the sake of separation of concerns). These blueprints cannot and shouldn't be referenced as 'services' they can't be deployed independently and are still a part of a single flask app. Microservice architecture would feature standalone and independent applications as opposed to blueprints in a single app.
I totally agree. That's not what the article insinuates.
The whole idea of using blueprints is to act as an oversimplified "API gateway" for the two microservices.
They can as well be separated easily.
Thanks for that tho.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Really great piece here. Although i should mention that flask-blueprints aren't standalone apps they are instead used to extend a single flask app into components (for the sake of separation of concerns). These blueprints cannot and shouldn't be referenced as 'services' they can't be deployed independently and are still a part of a single flask app. Microservice architecture would feature standalone and independent applications as opposed to blueprints in a single app.
I totally agree. That's not what the article insinuates.
The whole idea of using blueprints is to act as an oversimplified "API gateway" for the two microservices.
They can as well be separated easily.
Thanks for that tho.