"Each actor has a mailbox to which its incoming messages are delivered. There are multiple mailbox implementations from which to choose, with the default implementation being FIFO... each instance of an actor runs in its own lightweight thread and that messages are processed one at a time" So an actor is a service of sorts with a priority queue.
"Akka toolkit allows you to use Actor systems (originally derived from Erlang) that gives you an abstraction layer over threads." (per here)
Fred 11:17 AM 4/18/17 - Hi Vova.... question(s). Could you explain this line of code to me in a couple sentences please? label in vm.searchLabelResults = (vm.apiLabels | searchInArray : vm.searchLabel) | orderBy : label First, is this JavaScript or Angular syntax? The searchInArray function/filter defined in searchInArray.filter.js appears to take 2 inputs, array and searchText. So why does this line of code look like one of those inputs vm.apiLabels comes before | searchInArray : while the other vm.searchLabel comes after? Also, what does "vm" stand for. I see it gets set to this. Is that JS or Angular? (Maybe more than a couple sentences
Volodymyr - This is Angular's way of filtering data - we are taking vm.apiLabels and then applying filter to it by '|' sign. So searchInArray takes it as a first argument (array), and second argument is passed by ': vm.searchLabel'. "vm" is a way to refer controller in angular, it can be anything) It just came from style guide I try to stick to) if you're interested in deeper explanation, here's an article https://johnpapa.net/angularjss-controller-as-and-the-vm-variable/
"VM" stands for ViewModel aka the Controller
Fred 11:40 - Followup: is there a reason I can't find "as vm" anywhere in the code?
Vova - app.routes.js, inside in states declarations we have "controllerAs" for each state
FWC - really nice overview of Twitter architecture
"One of the overall observations one can make from looking at Twitter's architecture is that many of the design decisions are admirably pragmatic."
"Twitter also uses HDFS in Hadoop extensively for off-line computation"
"Communication between front-end and back-end services uses the Facebook developed Thrift as the RPC mechanism, and JSON over REST [FWC - more evidence they aren't compatible] as the public RPC"
"As the back-end code is being pulled towards the JVM, the front end client code, in common with many contemporary web based applications, is gradually making heavier and heavier use of browser-based JavaScript."
"I wouldn't say that Rails has served as poorly in any way, it's just that we outgrew it very quickly."
"Rather, the move to JVM is driven as much by a need for better developer productivity as it it for better performance."
"The primary driver is honestly encapsulation, so we can iterate faster as a company. Having a single, monolithic application codebase is not amenable to quick movement on a per-team basis."
"I would say about half of the productivity gain is purely because of accumulated technical debt in the search Rails stack. And the other half [of the productivity gain] is that, as search has moved into a Service Oriented Architecture and exposes various APIs,static typingbecomes a big convenience in enforcing coherency across all the systems. You can guarantee that your dataflow is more or less going to work, and focus on the functional aspects. Whereas for something like building a web page you don't want to recompile all the time, you don't really want to worry about whether in some edge condition you are going to get a type you didn't expect. But as we move into a light-weight Service Oriented Architecture model, static typing becomes a genuine productivity boon. And Scala gives you the same thing."
FWC - probably the best written and (seemingly) least biased article I've read
"Few sites would experience the same extreme demand as Twitter, so not every Rails-driven site is a candidate for a ground-up rewrite."
"In light of this, one possible reason for the growth in demand for Ruby on Rails and Ruby is to preserve or maintain -- or even replace -- existing Ruby or Rails infrastructure, rather than building new objects with it."
"So choosing among the framework depends upon what skill set you have. If you want to maximize advantage of your existing Java skills or have developers experienced in Java than go for Grails. But if you are more accustomed with Ruby, HTML, CSS and JavaScript then go for Rails."
In 2016, things are different. You pay nothing to set up a web page with Weebly or Strikingly or Wix or Squarespace. The cost is zero. You just need to pick colors for your site these days. Most of them will have a widget that can take user input and send that information your way. Do you want a blog? you can create a free one on Ghost or Tumblr or Jekyll or LinkedIn or Medium. You need a blog and a website together? WordPress will do the trick. If I started a business today, I would host it on Bluehost or GoDaddy with WordPress underneath. In fact, This site runs on Bluehost with WordPress underneath. Domains are cheap today. Once your site is ready, you can point your domain to sites I mentioned above and you have an online business. We are reaching maturity in web applications now. Freelancing is not the same anymore. There are out of the box solutions for most things you would hire a developer for back in 2002. Need to sell shirts? Go to Shopify. Need to sell e-books or any software? Go to amazon or sell it on your site using stripe or gumroad or e-junkie or e-bay. Need to roll out your own design? You have cheap options in Fiverr or 99designs or Upwork. With dedicated graphic design firms, you get premium quality. With dribbble, You get quality work and a ton of options.
"Play builds on Scala and looks promising. You can use either Java or Scala to build with it. I am new to Scala as well as Play. I know that Play Framework versions aren’t backward compatible."
"Grails builds on Groovy and allows you to build your code fast. It is the groovy version of ruby on rails. I see that latest Grails builds on Spring 4 and Spring Boot. As a Java Developer, you will have to learn Groovy. You may need to understand GSP – groovy server pages vs JSP concept. You may need to understand GORM – Groovy ORM vs Java ORM. This is not a steep learning curve but takes time regardless."
Python/Django - "developing on Django is an exhausting symphony of sighs"
"Zentasks is a tutorial that guides you on the process of creating a website for task management"
"So on Play I had to inherit a base template and implement every empty block – hence, the 'baggage' of the base template always came attached. Rails uses composition"
Java/Play - "perfect if you know Java and want to develop web applications, it just works."
Ruby/Rails - "Rails enables fast development great for prototyping. The more you use it the more you love it."
"Rails is a great prototyping application. It's fast, developers can build great applications on top of it. But you don't have to build your entire application on top of it. You're going to be able to build a lot faster with Rails than you would with Play. You're going to be able to convert processes that are slow in Rails into SOA's."