kubek2k

thats a wonderful improvement of apex, thats for sure :)

I guess you mean the API-Gates + Lambda. Not sure - I think thats something that should be handled by some separate tool (APIGatesgger? ;) - lets hope its not another dirty word)

I don't mind being trolled :)

Serverless is way much more advanced machinery than this tool. My point was to create a tool, not a whole ecosystem around AWS Lambda.

When it comes to serverless - my main concern (as it was with Lambda without env variables), is with storing configuration data along the code in the repo. Additionally the reason for creating was mostly pipelines.

the initial idea was that CI deploys lambda, and you promote it from stage to stage. I might consider upload sometime.

From what you write I think apex would be better suited for you

really good read. thx! :bow:

I didn't plan to do the push-to-deploy thing, mostly because that would totally complicate things. The rationale was more that we would use the CI that would automatically build and deploy things to DEV env that would be then promoted around.

thanks! - please give it a try and let me know in the issues if something doesn't work as expected.

:bow:

https://github.com/kubek2k/lambdoku/issues/8

there is also vert.x worth to look at

have you ever heard of YAGNI?

because: * you can do ES indexing async * having articles index instantly is not critical (I guess)