hum, haven’t had time for portkey but had a thought in my mind. Do we need to serialize state of java.security classes at all? Would a serializer that creates a new instance with suitable factory methods (given presence of them and access to any parameters needed) be enough?

But instances may have been customized (different init params).

I was thinking of letting the user provide her own factory.

But then what to pass to the factory so that it can recognize what to do?

And what about libs?

“Oracle’s Java keystore must trust the certificate authority (CA) used by the AWS service; by default, it is empty. An easy way to fix this problem is to replace the default Oracle Java keystore with a populated keystore from a standard Java installation:”

from => https://aws.amazon.com/fr/blogs/big-data/from-sql-to-microservices-integrating-aws-lambda-with-relational-databases/

@baptiste-from-paris am I reading it wrong? I understand it’s Oracle DB that needs a change to call Lambdas.

yes, I read it too fast, sorry for that

No problem

Instrumentation is a solution but then port key would have to be loaded first.

That’s a requirement I can live by (same as powderkeg)

Gonna slay that dragon!

Just saw Rich's keynote released on youtube

ahhhh

let me watch this !

https://youtu.be/2V1FtfBDsLU

intro is fun ^

^^

might not happen easily

lol

thought of it, my GF is not a huge fan

this guy is a genius, it’s crazy, this conference is really powerful

just another conf. that I am going to watch 2/3 times 😅