network profile
| bio | website | blog.hand-net.com |
|---|---|---|
| location | Strasbourg, France | |
| age | 32 | |
| visits | member for | 2 years, 1 month |
| seen | Jan 1 at 5:32 | |
| stats | profile views | 15 |
Work at http://www.sosp.fr.
|
Apr 22 |
awarded | Popular Question |
|
Mar 8 |
awarded | Autobiographer |
|
Dec 30 |
awarded | Popular Question |
|
Dec 29 |
awarded | Yearling |
|
Oct 21 |
accepted | Starting a new startup/web application, how to choose a hosting provider? |
|
Oct 21 |
revised |
Starting a new startup/web application, how to choose a hosting provider? added 140 characters in body |
|
Oct 21 |
awarded | Editor |
|
Oct 21 |
comment |
Starting a new startup/web application, how to choose a hosting provider? see my edit, I take a deep look at MongoDB as it seems to fit well with such architecture. And SE is actually a great source of inspiration (philosophy, technical choices, and some great articles form Jeff Atwood about the developer's sins). At least, I don't want to reinvent the wheel. Just use some widely use concepts, targeted to simplicity AND efficiency AND scalability |
|
Oct 21 |
revised |
Starting a new startup/web application, how to choose a hosting provider? added 140 characters in body |
|
Oct 21 |
comment |
Starting a new startup/web application, how to choose a hosting provider? Interesting to keep it in mind. Please note I does not want to build the ideal application first, but I don't want to close doors at beginning. Moreover, frameworks I'm targeting to use are nicely build to decouple a lot of thinks. They fit well for simple web apps to large web apps by changing few things |
|
Oct 21 |
comment |
Starting a new startup/web application, how to choose a hosting provider? I'm actually hoping to reach thousands of simultaneous users. I'm planning to write the app to be easily distributed over several servers (with different roles, each role potentially itself working over several boxes). As I said, at start, a single box will host all roles, but when the apps will grows, both in term of content and number of users, the roles will have to be split across different boxes (NServiceBus and eventual consistency are my friends). What I actually want to avoid, is to have high cost for hosting today, but with the ability to grows tomorrow without having to change all |
|
Oct 21 |
asked | Starting a new startup/web application, how to choose a hosting provider? |
|
Sep 1 |
awarded | Scholar |
|
Sep 1 |
accepted | Is c# actually a multiplatform language? |
|
Jul 15 |
comment |
Best way to share / “donate” a C# software - and what license? still an interesting question :) |
|
May 10 |
awarded | Nice Question |
|
May 10 |
awarded | Student |
|
May 10 |
comment |
Is c# actually a multiplatform language? @cody gray: and you reach your goal :) |
|
May 10 |
comment |
Is c# actually a multiplatform language? @Cody gray: c++ is not an option as WP7 only allows C# as programming language. What I want to share ? Mainly some "model" and "business" classes. Model, because a customer will always have an ID property, a Title property, etc. And business because the title of the customer will always be validated with same rules, and because the computation of the estimated revenue with this customer will always follow the same algorithm. This is only an example, but it shows there is, in my opinion, no dependency with any target platform. In all case thanks a lot. It add to my reflexion some thinks to cons |
|
May 10 |
comment |
Is c# actually a multiplatform language? @Cody Gray: thanks for this interesting feedback. If you add in the equation that c# is well mastered by developers today, what can be the options ? 1. use C# and rely on mono* ? 2. introduce native (by native I mean "official" language, not processor native) code for very specific tasks (either low-level or GUI), and share c# code where it's feasible ? 3. keep c# on MS platform (windows phone, windows apps and server side), and move fully to native dev on other platforms. I'm starting to think the 3rd option is the less risky in the long term, but with a higher starting cost. |
