Explore >> Select a destination
|
You are here 
|
ask.replit.com | ||
| | | | |
blog.replit.com
|
|
| | | | | After a 5 year Hosting beta, we're ready to Deploy. Introducing Replit Deployments Today we're releasing Replit Deployments, the fastest way to go from idea to production in any language. It's a ground up rebuild of our application hosting infrastructure. Here's a list of features we're releasing today: Your hosted VM will rarely restart, keeping your app running and stable. You're Always On by default. No need to run pingers or pay extra. | |
| | | | |
www.ncameron.org
|
|
| | | | | The TiKV transactions SIG is starting up its reading group. We'll try to read and discuss a paper each month. If you're interested in research in distributed transactions, come join in! We'll start by reading 'Industrial-Strength OLTP Using Main Memory and Many Cores', by Avni et al. at Huawei Research | |
| | | | |
renato.athaydes.com
|
|
| | | | | ||
| | | | |
www.morling.dev
|
|
| | | Recently I ran into a situation where it was necessary to capture the output of a Java process on the stdout stream, and at the same time a filtered subset of the output in a log file. The former, so that the output gets picked up by the Kubernetes logging infrastructure. The letter for further processing on our end: we were looking to detect when the JVM stops due to an OutOfMemoryError, passing on that information to some error classifier. | ||
