aliostad

8 ms·

31.
by aliostad 11y ago
/api/v1/rock/similar?pos=[comma separated list]&neg=[comma separated list] Use different names to mix and match styles. Example: /api/v1/rock/similar?pos=Radiohead /api/v1/rock&#x2F
32.
Abstractions my Deep Learning word2vec model made(byterot.blogspot.com)
125 points by aliostad 11y ago|55 comments
33.
Measure all parts of your application using PerfIt(byterot.blogspot.com)
1 points by aliostad 11y ago|0 comments
34.
Machine Learning and APIs: Introducing Mills in REST API Design(byterot.blogspot.com)
3 points by aliostad 11y ago|0 comments
35.
Pilgrimage into the world of Tarkovsky: through the eyes of hope and suffering(byterot.blogspot.com)
1 points by aliostad 11y ago|0 comments
36.
Utilisation and High Availability Analysis: Containers for Microservices(byterot.blogspot.com)
3 points by aliostad 12y ago|0 comments
37.
Ask HN: What should Microsoft do to change geek opinion?
14 points by aliostad 12y ago|21 comments
38.
QCon London 2015: Microservices, from hype to trendsetting – Part 1(byterot.blogspot.com)
1 points by aliostad 12y ago|0 comments
39.
by aliostad 12y ago
Thanks guys for your hard work.
40.
by aliostad 12y ago
dude, have you ever used Google Trends? It is a cut and paste from the source. The y axis is the popularity as the title says. It is so obvious even Google has omitted it.
41.
by aliostad 12y ago
Yes. And this trend is reversing. Have a look here: http://www.itjobswatch.co.uk/jobs/uk/machine%20learning.do Salaries have gone up by 16%
42.
Rise of the Scientific Programmer(byterot.blogspot.com)
2 points by aliostad 12y ago|0 comments
43.
Health Endpoint in API Design: slippery slope that it is(byterot.blogspot.com)
5 points by aliostad 12y ago|0 comments
44.
How poor performance of HttpContent.ReadAsAsync can affect your API/site(byterot.blogspot.com)
3 points by aliostad 12y ago|0 comments
45.
SuperBenchmarker, a command line web stress test tool on Windows(byterot.blogspot.com)
2 points by aliostad 12y ago|0 comments
46.
The mystery egress(byterot.blogspot.com)
3 points by aliostad 12y ago|0 comments
47.
by aliostad 12y ago
Anyone else had similar experiences?
48.
Performance Counters for your HttpClient(byterot.blogspot.com)
4 points by aliostad 12y ago|0 comments
49.
Thank you Microsoft, nine months on(byterot.blogspot.com)
6 points by aliostad 12y ago|0 comments
50.
Reactive Cloud Actors with BeeHive 0.5, RabbitMQ and more(byterot.blogspot.co.uk)
1 points by aliostad 12y ago|0 comments
51.
Cancelling an async HTTP request Task sends TCP RESET packet(byterot.blogspot.com)
1 points by aliostad 12y ago|0 comments
52.
BeeHive Series – Part 2 – Importing file from blob storage to ElasticSearch(byterot.blogspot.com.tr)
2 points by aliostad 12y ago|0 comments
53.
Reactive Cloud Actors with BeeHive: Getting started(byterot.blogspot.co.uk)
2 points by aliostad 12y ago|0 comments
54.
Reactive Cloud Actors: An Evolvable Web of Events(infoq.com)
3 points by aliostad 12y ago|0 comments
55.
by aliostad 12y ago
Imperative style means that A has to know about B. In needs to know what is the next step. With reactive it does not. This creates the decoupling. And also not everyone else's protocol. An event is an important business milestones for
56.
by aliostad 12y ago
Yes, but they do them differently. BeeHive is much more opinionated about the message (must be event and has an enveloper) and the Basic Data Structures. Also BeeHive avoids stateful actors. State is always persistent in HA queues or Basic
57.
by aliostad 12y ago
Well, first of all, debugging while developing an actor is actually easier: you just have to debug an actor in isolation and make sure it does the right thing and sends the right event in response to the incoming event. In terms of debuggin
58.
by aliostad 12y ago
No it is not the same. First of all, CQRS is applying CQS to the architecture, so it is an architectural decision. When you use commands, you know about the interface of the endpoint receiving your message. In case of an event, you do not h
59.
by aliostad 12y ago
Yes, so many buzzwords together - I admit. The difference is replacing Commnad/Query with events. Replacing Imperative with Reactive. Did you read the whole post or you were put off by the buzzwords?
60.
Reactive Cloud Actors: No-nonsense micro-services(byterot.blogspot.com)
41 points by aliostad 12y ago|31 comments

More ›