545 karma · joined March 24, 2011
Walmart, Twitter and Amazon would be three notable examples of companies that have achieved large scale that are using it.
It also complicates your scaling story, your caching story, your ability to change databases and a great number of other things.
If you're building an app that has no chance of ever possibly needing to scale, or use a different database for caching, searching, or analytic reasons, then this approach may be optimal, but if any of those levers need to move at some point, I think you'd be in for a world of hurt.
I may be an anomaly, I do not like having a smartphone, and am looking forward to the day when my device set will be watch, tablet & desktop.
That said, fair point, faster startup is always better.
I guess just another example of different strokes for different folks. For us developer time decreased, and expressivity increased.
I wasn't suggesting that rails shouldn't be used for microservices, we actually have a number of rails microservices in production as well.
I was more stating that I agree with OP in that if I were to write a monorail style application today, I would use ruby/rails over clojure. I was also pointing out that if you are moving to more of a SOA/microservices framework that we've had great experience with clojure, and that it's worth looking at.
I'm a huge fan of rails, and have been using it since pre-1.0. I think as we look back on this period in time, we're only going to appreciate rails more and more for really making self / low funded startups viable.
Cheers!
- I agree that most rails programmers will not move to clojure.
- For monorail apps, rails is still king.
That said, for us, when comparing clojure and ruby REST API services we've built, clojure has had the following benefits:
- Less code
- Less tests needed
- Better concurrency
- Less developer hours
- Less maintenance
- About 33% of the servers for same performance
- Easier/faster debugging
It's been far more then a 10x improvement overall, and if people are looking to move out of the monorail style of app, it's definitely worth a look.
My strong suggestion, when/if you reach that stage (and it sounds like you're there), just let everyone know you need to move on.
It will be OK, I promise. Your investors will be OK. They invested knowing they might lose their investment. Your co-founder will be OK. He may be frustrated with you for X number of months or even years, but that's OK.
You tried your best, and it didn't work out, but that's OK. You're only 25, you basically paid yourself to learn a ton of about a ton in a short compressed time period. \
Eventually you'll learn to be impressed with how much you did in this timeframe.
Once you leave, give yourself time to heal and reflect.
These are the experiences that teach us and help us grow, but you'll need time away to see that clearly.
Good luck! Keep the good fight going and know there's a community of us who had something not work out, but were able to rebound and make the next one work... or the next one.. or the next one.. :)
Also, what about people who have a single grandparent who is African-American. Does this kind of thing apply to them?
I grew up in a lower to middle class town in New England, and virtually none of my peers I grew up with would know who Edward is either.
While thats not how I'd personally conduct the interview, I do think the first half of it was trying to deconstruct this idea that everyone is engaged and understand the debate, setting up the second half of the interview where he tries to get Snowden to explain things as simply and as direct as possible.
While I'd assume most of us on this board are tired of "It's like Uber for X", there's a reason that we use it, and it's because the "general public" "gets" it.
The reality is, you need senior engineers, people who have built systems before, and are over the stage of their career where they just want to build stuff for fun, and are actually focused on building systems that provide value for the companies they work for.
It's not about new tech, or old tech, or boring tech, or exciting tech. It's about looking at the specific problem at hand and making an assessment about which technologies make sense to use.
As much as our industry doesn't want to admit, there are advantages to having real work experience.
Both libraries are awesome.
From: https://lispjobs.wordpress.com/2014/11/25/clojure-software-d...
CORTEX is our next generation platform that handles real-time financial data flows and notifications. Our stateless event-driven compute engine for dynamic data transforms is built entirely in Clojure and is crucial to our ability to provide a highly agile response to financial events. We leverage AWS to operate on a massive scale and meet high-availability, low-latency SLAs.
We've built our systems to recover from failure states once we know there is a problem. AWS's inability to do that reliably is forcing us to own the problem ourself, and as a result, we will probably migrate away to use cheaper boxes in the cloud.
On the positive side, RDS has been solid.
Kafka supports replication and fault-tolerance, runs on cheap, commodity hardware, and is glad to store many TBs of data per machine. So, retaining large amounts of data is a perfectly natural and economical thing to do and won’t hurt performance. LinkedIn keeps more than a petabyte of Kafka storage online, and a number of applications make good use of this long retention pattern for exactly this purpose.
From http://radar.oreilly.com/2014/07/questioning-the-lambda-arch...
A complex kafka setup is pretty involved (relatively speaking) and becomes domain specific pretty quickly, at which point, it probably becomes less usable / understandable to someone who is trying to learn / get interested.
On the whole, I agree with you. Some of the open source software that exists now is truly amazing and I think lots of people are defaulting to less-the-optimal solutions because they just don't have exposure to the latest and greatest.
http://docs.aws.amazon.com/kinesis/latest/dev/service-sizes-...