Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aliostad
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
Web APIs and n+1 problem
(byterot.blogspot.com)
1 points
by
aliostad
13y ago
|
1 comments
62.
▲
Web APIs and n+1 problem
(byterot.blogspot.co.uk)
2 points
by
aliostad
13y ago
|
0 comments
63.
▲
by
aliostad
13y ago
It is about High Availability. Have you ever tried to use a central broker in NSB? The best HA you get is clustering 2 machines. And that is not HA.
64.
▲
by
aliostad
13y ago
Author here. Point is middlewares that are not built from ground up to scale horizontally are bound to die. BizTalk uses SQL Server for its storage as such cannot be horizontally scaled. End of story. NServiceBus... well, let's not go
65.
▲
by
aliostad
13y ago
+10. >> You simply CANNOT explain to a .net zealot what big data is. They just don't get it Could have not said it better.
66.
▲
by
aliostad
13y ago
I am mainly talking about server technologies. So yes, client technologies do not need to scale. But if the when even LOB apps need to work wit Remember "Can't hurt", not quite true. I am shifting focus, so I am spending time
67.
▲
Thank you Microsoft, and so long
(byterot.blogspot.com)
56 points
by
aliostad
13y ago
|
48 comments
68.
▲
CacheCow 0.5.0-alpha released for community review
(byterot.blogspot.co.uk)
2 points
by
aliostad
13y ago
|
0 comments
69.
▲
HTTP Content Negotiation on higher levels of media type
(byterot.blogspot.com)
4 points
by
aliostad
13y ago
|
0 comments
70.
▲
Content-based action selection - REST
(byterot.blogspot.com)
1 points
by
aliostad
13y ago
|
0 comments
71.
▲
REST APIs and restaurants [Take II]
(byterot.blogspot.com)
4 points
by
aliostad
13y ago
|
0 comments
72.
▲
REST APIs and restaurants
(byterot.blogspot.com)
1 points
by
aliostad
13y ago
|
0 comments
73.
▲
by
aliostad
13y ago
This is a REST viewpoint so assumes all services are exposed by a REST API. ESB sits in the infrastructure layer and not the presentation - so these cannot be the same. But I think you are right that in some enterprises ESB connects everyth
74.
▲
API Layer and its responsibilities, a REST viewpoint
(byterot.blogspot.co.uk)
5 points
by
aliostad
13y ago
|
2 comments
75.
▲
API Layer and its responsibilities - a REST viewpoint
(byterot.blogspot.com)
1 points
by
aliostad
13y ago
|
0 comments
76.
▲
OWIN and Katana challenges: blues of a library developer
(byterot.blogspot.co.uk)
1 points
by
aliostad
13y ago
|
0 comments
77.
▲
SuperBenchmarker (ab.exe on steroids) for generating load on your API/Site
(byterot.blogspot.com)
1 points
by
aliostad
13y ago
|
0 comments
78.
▲
SuperBenchmarker - Apache Benchmark (ab.exe) on steroids
(byterot.blogspot.co.uk)
1 points
by
aliostad
13y ago
|
0 comments
79.
▲
Monitor your Web API application using your own custom counters
(byterot.blogspot.com)
2 points
by
aliostad
14y ago
|
0 comments
80.
▲
Performance series: GUIDs vs. IDENTITY INT in RDBMS
(byterot.blogspot.co.uk)
1 points
by
aliostad
14y ago
|
0 comments
81.
▲
Iran May Have Faked Its 'Successful' Space Monkey Trip
(businessinsider.com)
2 points
by
aliostad
14y ago
|
0 comments
82.
▲
The monkey Iran claims to have returned safely from space not the same sent up
(observers.france24.com)
4 points
by
aliostad
14y ago
|
2 comments
83.
▲
Review of .NET Framework cryptography and symmetric algorithms benchmark
1 points
by
aliostad
14y ago
|
0 comments
84.
▲
Performance series: is thread contention bad?
(byterot.blogspot.co.uk)
1 points
by
aliostad
14y ago
|
0 comments
85.
▲
5 levels of media type - REST
(byterot.blogspot.com)
4 points
by
aliostad
14y ago
|
0 comments
86.
▲
by
aliostad
14y ago
I am really happy if you think all of this is common sense. In fact a lot of software best practices are common sense but they do not necessarily consistent with each other. Even in life, "Always help others" and "Set your goals and run for
87.
▲
by
aliostad
14y ago
Server cannot rely on client for storing its own domain's state - while client can store user-related state for improving performance, usability. For example, twitter cannot rely on a client to store the tweets while the client could cache
88.
▲
Client-Server Domain Separation
(byterot.blogspot.com)
22 points
by
aliostad
14y ago
|
13 comments
89.
▲
NoSQL Benchamrking - Redis, MongoDB, Cassandra, RavenDB and SQL Server
(byterot.blogspot.com)
3 points
by
aliostad
14y ago
|
0 comments
90.
▲
How limitation can be source of goodness - NoSQL, REST and more
(byterot.blogspot.co.uk)
1 points
by
aliostad
14y ago
|
0 comments
More ›