HN user
Former Docker & OpenStack. 2x founder. Infosec / hacker. Mother of clouds, destroyer of monoliths.
SSH over tor from your browser. Connect to .onion addresses or use exit nodes to the internet. Encrypted local vault. Arti (WASM) to Snowflake rendezvous servers over WebRTC.
git on my personal account (not an official Tor project):
Wow. I'm not sure what to say. She and I had a lot in common, both personally and in our interests. I hope she's at rest.
AWS Serverless Community Hero and CTO/Co-founder of IOpipe here.
AMA!
Humans are more expensive than infrastructure!
IOpipe | distributed remote | www.iopipe.com
IOpipe provides tools for developers of serverless applications, helping devs and operators deliver and run with confidence. We are seeking to grow our team with strong candidates with a comfort in remote work, collaborative and product-driven development.
Our stack is built on AWS Lambda, Kinesis, Elasticsearch, React, and AWS Fargate.
Roles: Site Reliability Engineer (SRE) Solutions Architect
Hiring portal: https://hire.withgoogle.com/public/jobs/iopipecom
There's a free tier and we're happy to discussing pricing privately. Startups, individuals, open source projects are dear to our hearts and we want to make the product accessible to those that need it.
I'm excited because this makes it so much easier to get started with Greengrass. Java, NodeJS, and Python with a full IoT service behind it... and compatible with AWS Lambda. Seems likely they'll add Go soon too.
Systematic oppression makes ignoring ToS the default. Businesses choose not to cater to sex workers and such workers find themselves in the situation where there's no option but to ignore the ToS. You find that when services you take for granted aren't available, things get... harder. So you do what everyone else does to the best of your ability even if you are an "undesirable" that has been asked to stay outside the group, even when that's illegal. So yeah, sex workers are going to do what they need to do to survive and make ends meet, the terms of service for websites is the very least of their concerns when they don't know if they'll make rent this month.
The Yubikey is great and has uses outside of U2F, which I've never had much faith in.
Vint Cerf started in 1965. He's moved into positions that are more management oriented, but I believe he's deeply involved in technology decisions.
We have code that you can run on your AWS account for more accurate information from servers.lol based on Cloudwatch metrics. Latency and coldstart information would be totally interesting, I'll suggest it to our team!
My team uses the Serverless Framework (serverless.com), git-with-github, and automate deployments from CI/CD.
AWS also offers some of these pieces fully integrated via CodeDeploy (which we do not ourselves use).
At Re:Invent last month, AWS introduced per-function concurrency limits that users can set. It can still rack up charges, but it offers a bit more control than before!
On AWS Lambda you could copy the Powershell Linux binary into your project and call it from wrapper code in NodeJS, Python, Java, C#, or Go.
Over in Microsoft land, Azure Functions natively supports Powershell according to this blog post: https://david-obrien.net/2016/07/azure-functions-PowerShell/
lambda would be a good way of scaling this without improving the architecture otherwise :)
you know because they let you access and replay the recordings from their app.
The Snowball ships bare, without packing materials. You receive it, plug it in, transfer data / run code, and ship it.
Still, you're right that there's a logistic issue of physically locating, networking, and powering these devices.
IOpipe (Techstars NYC'16) | REMOTE | Full-time
IOpipe is seeking SENIOR candidates for remote, full-time positions:
- Senior Frontend Engineer: you will work on our real-time dashboard building the visual and interactive elements of our service. Seeking candidates with experience in React and charting / visualizations using D3.
- Senior Backend Engineer: You live in NodeJS and/or Go and want to build a great API that processes lots of data, really fast. The ideal candidate will have experience with Kafka, Kinesis, and/or Cassandra.
About IOpipe - we offer application performance monitoring (APM) for serverless applications. We are a Techstars company and have just completed the Summer'16 program in NYC.
Contact hiring@iopipe.com!
I only do steps 3-5 here. I no longer find any value from Chef/Puppet/Salt/Anisble or Vagrant.
Lambda does not bill on these, nor do they provide you with these metrics out of the box. This is something that 3rd-parties can provide, however... it's something that we collect with IOpipe[1] (disclaimer: I'm CTO & founder)
Reading through, it seems that JS is allowed, but the page needs to be functional without it. Ideally, the page would work with Lynx.
I wish I engaged in Silicon Valley and venture-backed startup culture sooner. If I had, my first startup might've had a better chance of success. Instead, I bootstrapped and ended up with a lifestyle business. I also started it at age 19, just as the '99/2k bubble burst, so I can't take it too hard...
I did finally begin integrating into the larger tech scene around '07 with the introduction of Twitter. This and other factors led me to deciding to exit the business and join startups (Cloudscaling, then Docker). I had, however, passed up on offers to join early-stage at a couple companies that had mega-exits... so there's certainly a bit of, "what-if?".
That said, perhaps if I had more early success, I wouldn't now be founding my current company (IOpipe, Techstars'16: www.iopipe.com)
Sweet. I put together something similar for NodeJS which is now called 'turtle' (because it's turtles all the way down...). There's a bit of a focus on AWS Lambda & other FaaS solutions as a means of building Lambda architectures, but it can be used by itself.
Just mind that the tools and services around Lambda are getting better, but you will certainly be a relatively early-adopter. It will undoubtedly result in some extra time spent learning, but you'll also eliminate a number of critical operational concerns and concerns about scale.
Mind that Lambda will not handle state for you, functions are stateless. You'll need to store state into hosted services like DynamoDB, Firebase, S3, etc... or stand up (micro)services that manage that state (say, a PostgreSQL database in Docker, saving to an EBS volume).
IOpipe | Philadelphia, NYC | full time | onsite
IOpipe is building an open source community for tools to build, ship, and run serverless applications anywhere. www.iopipe.com.
We are currently hiring for a backend / systems software engineer, local to either Philadelphia (preferred) or NYC. You would be the second hire, immediately working with our engineering team and founders.
Your role would involve development of the IOpipe CLI, libraries, and APIs in Javascript (NodeJS) and Go. Knowledge of Docker and/or Kubernetes is ideal, but not required.
Email hiring@iopipe.com
Also, check out our projects on Github: https://github.com/iopipe/
It's open source. I'm open to seeing how we might be able to integrate or work with Effe in our Go SDK, or if necessary, learn from your effort. Take a look at https://github.com/iopipe/iopipe-golang, I'd love a pull-request.
We're not an alternative to AWS Lambda or, "Lambda on your own infrastructure". Instead, we desire to make it easier to build apps that run anywhere, which includes both AWS Lambda and Docker. I suppose there's some overlap, but the goals and technical challenges are a bit different. IOpipe is also a library that simplifies integration with services that provide state.
OpenWhisk runs as a long-lived service which runs your code in Docker containers. In a way, it's a hammer.
IOpipe can deploy code anywhere, which includes both Docker and OpenWhisk. It's the nail. You could deploy an app with IOpipe to OpenWhisk then run a map-reduce job on the same OpenWhisk cluster, on Docker Swarm, AWS Lambda, or... anywhere
It would be easy to stand up a service based on IOpipe that works like OpenWhisk, but that's just one use-case.
If he's using these for the SuperCharger network and plans to "gas-up" cars with solar... I don't think they can get that level of efficiency from panels spread through a gas station lot? Because that's where this purchase would seem to make sense to me, is with a nationwide network of SuperChargers powered by solar.
I'm sure some value would also come from selling to residential buyers with Teslas?
I am involved daily in precisely an effort to do just this. The differences between the big 3-4 providers is relatively marginal (call arguments and versions of interpreters such as NodeJS). Take it as a plug if you must, but being able to handle the former is one of the goals of https://github.com/iopipe/iopipe.
The version of language runtimes is where the most lock-in will occur, and really, that's kinda marginal, too. Language runtimes should be as stable and standard as, say, the Linux kernel's userland interface. If language runtimes can't deal with this, then they'll fail.