Katana MRP

Katana MRP

10 Followers
Smart Manufacturing Software

Decisions 3

Priit Kaasik

Engineering Lead at Katana MRP

Shared insights
at

We undertook the task of building a manufacturing ERP for small branded manufacturers. We needed to build a lot, fast with a small team, and have clear focus on product delivery. We chose JavaScript / Node.js ( React + LoopBack full stack) , Heroku and Heroku Postgres (also Heroku Redis ) . This decision has guided us to picking other key technologies. It has granted us high pace of product delivery and service availability while operating with a small team.

8 78.7K

Priit Kaasik

Engineering Lead at Katana MRP

Shared insights
at

Sometimes #ad-blocking addons can cause a real headache when working with JavaScript apps. Onboarding assistants (Appcues + elevio ), chat (Intercom) and product usage insight (Hotjar) have all landed on their blacklists. I guess there is a perfectly good reason for this that I just don't know.

In order to fix this, we had to set up our own content delivery service. We chose Amazon CloudFront and Amazon S3 to do the job because it has a good synergy with Heroku PaaS we are already using.

7 121.6K

Priit Kaasik

Engineering Lead at Katana MRP

We chose CloudAMQP because it suited better for the job - being a message broker between microservices. Also, it keeps message states and has a good UX.

The drawbacks of this decision are hypothetical, it is said that RabbitMQ scales better vertically, we are consuming it as service via CloudAMQP so, they will take care of this.

1 275

Followers 10