pavel_pt

29 ms·

1.
by pavel_pt 1y ago
Business hours for the team receiving the alarm; many issues can wait to be resolved during your own waking hours if they are not impacting customers.
2.
by pavel_pt 1y ago
I worked at AWS (EC2 specifically), and the comment is accurate. Engineers own their alarms, which they set up themselves during working hours. An engineer on call carries a "pager" for a given system they own as part of a small t
3.
by pavel_pt 1y ago
Fantastically insightful; surprised this didn't gain more traction here. Curious if the gook contains deeper insights still.
4.
by pavel_pt 2y ago
I think things like the Slack conference call integration depend on this. In fact that’s the only use outside of the official client I’m aware of.
5.
by pavel_pt 2y ago
If that’s all it takes an attacker, you’re doing AWS wrong.
6.
by pavel_pt 2y ago
I hope @sewen will expand on this but from the blog post he wrote to announce Restate to the world back in August '23: > Stateful Functions (in Apache Flink): Our thoughts started a while back, and our early experiments created Stat
7.
by pavel_pt 2y ago
Restate also stores a deployment version along with other invocation metadata. FaaS platforms like AWS Lambda make it very easy to retain old versions of your code, and Restate will complete a started invocation with the handlers that it st
8.
by pavel_pt 2y ago
Disclaimer: I work on Restate together with @p10jkle. You can absolutely do something similar with a RDBMS. I tend to think of building services in state machines: every important step is tracked somewhere safe, and causes a state transitio
9.
by pavel_pt 2y ago
We don't have specific plans for our next SDK to build, but Python definitely comes up often - thank you for the input!
10.
by pavel_pt 2y ago
Appreciate the feedback! What kind of support do you wish for, if there was one thing you would prioritize?
11.
by pavel_pt 3y ago
I think you do it just like you handle compatibility between services – you never remove parameters; you only ever add new optional ones if you have to. This way a message from the past will be compatible with a future handler, same as if y
12.
by pavel_pt 3y ago
How do you imagine detection of conflicts working?
13.
by pavel_pt 3y ago
+1 on views, for those things than need direct DB access. One effective pattern I’ve seen in large DB deployments is to separate the write schema from the read schema. That is, treat what is allowed to be written into the DB separately from
14.
by pavel_pt 3y ago
Are there any aspects in particular that would be of interest?
15.
by pavel_pt 3y ago
Not just in durable execution, but in control systems in general! Anything that operates on persisted state in a distributed environment has similar issues. Durable execution frameworks make them more apparent - and may also help us chart a
16.
by pavel_pt 11y ago
For customers with big infrastructure and/or a high rate of modifying resources, the ability to be notified of events occurring within AWS instead of than polling various describe APIs should be a huge win.
17.
AWS CloudWatch Events(aws.amazon.com)
2 points by pavel_pt 11y ago|1 comments
18.
by pavel_pt 11y ago
Ditto, used RAML on a previous project and everyone involved really enjoyed it. It manages to capture just enough about how thinks work without getting overbearing. I particularly like the fact that it allows for examples to be specified. I
19.
by pavel_pt 11y ago
The good parts of WSDL, I presume? ;-) I spent way too long staring at raw WSDL, I almost think certain profiles are actually OK. But SOAP on the whole is a world of pain.
20.
by pavel_pt 13y ago
One should hire people who care, and who continuously broaden their own horizons. When it comes to developers, these inevitably happen to also be polyglot programmers in my experience.