I think you guys need a logo to establish a brand

[allanchua101]

Hi guys,

I just did a case study about different route management frameworks for AWS Lambda and I think that it will help your library to distinguish itself from competitors. This will offer you the following benefits:

• Developers will easily identify the library's brand
• Developers will remember your framework faster
• Developers will not confuse you with other RMFs.

[simlu]

@allanchua101 Can you elaborate a bit by what you mean with brand? Do you mean prefix every package name with @blackflux?

Edit: Also hi and thank you for your interest!

[allanchua101]

@simlu

Something like that man! It will be awesome if you guys can utilize a logo with your company mascot + lambda function symbol on it. A web page with demo, docs, and code samples will also be an advantage!

If you visit the lambda-api's repository, the library has its own logo which makes it easily identifiable.

I will be sharing the first article on medium later!

[simlu]

Great! We've been looking for comprehensive alternatives to switch to: including good test frameworks, logging and monitoring, rate limiting etc.

Maybe there is something out there now, that offers all that, but with more people supporting it! So I'll carefully be reading your article 👍

As for making this project a bit nicer and giving it branding etc. Would love to do that. But only if it makes sense to invest that time really. Creating and maintaining inviting (!) OS is hard.

[allanchua101]

Got it @simlu

Would still recommend to at least have a sexy logo man 👍 but that's just a suggestion bro! You guys are doing a nice work of easing things out for Lambda community so Kudos to you guys!

Tonight's article is just a bunch of subjective observations, I will be making a data-driven analysis after this one man!

[allanchua101]

Sharing it out here awesome bunch!

https://medium.com/@ac052790/route-management-frameworks-for-aws-lambda-and-node-js-ab685aeec839