|
Hi,
I would like some suggestion on archietecture design.
Here are my requirements
1) I have clients spreaded over multiple locations
2) Their are groups of clients connected to a common server
3) Each server will gather gb of data everyday
4) There is a main server which is connected to every other local server
5) This server will have all the data which the local server will have. local servers will send data to main server.
6) I will be doing analytics on the main server as well as local servers
My main questions are
1) Since this is big data, which database should I consider sql or nosql
2) Where can hadoop fit here?
3) Is there are framework which helps me in sending data from local to global servers
|
|
|
|
|
I am exploring SPA/Angular and all the crap that is required by modern day web development. A colleague, with more experience in this area, is suggesting the data service and the SPA code should reside in the one project. Whereas I want to split it out to a WCF serving up Json formatted data in a separate project.
My justification is that the data will also be consumed by mobile platforms and a separation is valid. The projects tend not to be huge, 20-40 views and generally have a shed load of SP Processing with the results consumed by SSRS and mobile dashboards.
Any recommendation or reading links would be appreciated.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I am interested in becoming an application architect.
Are there any specific masters degrees that I should pursue?
Does anyone have any suggested reading material, or PluralSight courses I should watch?
I am a senior .net developer with 6 years experience. I also worked in Identity Access Management for 3 years, and am interested in taking this to the next level!
Thanks!
|
|
|
|
|
I found that the best way to learn architectural skills was to get involved in the design and architecture of applications where I work. For example, my company is replacing its legacy COBOL system with a .NET system. I have been heavily involved in the architecture and have advocated an SOA approach using WCF services. I have put together some prototypes to determine if the architecture is a good fit for the application.
Architecture takes years to learn and become expert at, and you need to be comfortable working on large, enterprise systems. The more exposure to have to these sorts of systems, then the greater will be your knowledge.
|
|
|
|
|
Joe Hoppe wrote: I am a senior .net developer with 6 years experience
I'd recommend first hitting 10 years experience.
You'd have to be able to explain the N-tier architecture and it's drawbacks and benefits, how it compares to CLSA, how IIS works, the difference between MVC and MVVM. Then you'd also need to be able to explain when to optimize, or how scalable a given solution is.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Joe Hoppe wrote: application architect
With limited experience you need to specialize in an industry. Learn about the industry and how problems in that industry are solved with software.
You can look for process control books such as Agile and CMM (there is at least one other) both because you probably need some familiarity with process control but also because those tend to relate architectural problems as examples. Rather difficult to find such examples anywhere else.
You might also try reading the following regularly.
http://highscalability.com/[^]
Joe Hoppe wrote: I am a senior .net developer with 6 years experience
I would suggest you learn databases. Certainly SQL. Start with either MS SQL, Oracle or MySQL and then experiment with the others. After that then look at one of the No-SQL databases. Pretty pointless to start with one of those given that they are all different. And better to have some understanding of SQL first before attempting to understand why someone might choose to not use it in the first place.
|
|
|
|
|
Would graduate school help?
I do have three years experience administering identity access management products, which I think is helpful, but indirectly helpful.
These are graft eat ideas that I will be looking into. Thanks!
|
|
|
|
|
Joe Hoppe wrote: Would graduate school help?
I doubt it. Some classes though, if picked carefully, might.
|
|
|
|
|
Hello,
I am looking for someone that can architect a project for me. I want to higher someone to design how the program will work from web page, log in, running, database access and storage. I would love any recommendations on where to find a person that can do that.
Thanks so much
|
|
|
|
|
What do you mean 'architect a project'
A lot of people out there in various 'hats' will be able to draw a 'multi component/layer' project such as you need - architects can be expensive though, and I doubt they would be giving their time free here.
I note you list very little (no) requirements - this is surely where your process would start, and hint, I as an architect would spend a good deal of time understanding your business needs before I could start breaking it down into requirements and thence a solution.
I suggest you start off writing down what it is you wish to capture & store, how long does it need to be stored, what other processes (eg reporting) need to happen to the data. Then think about what abilities you/your company has, ie software & hardware, that may 'shape' what sort of solution you need.
|
|
|
|
|
This is not the right place; you need to try the websites where people are looking for paid work.
|
|
|
|
|
And that's his question about, isn't it?
... recommendations on where to find ...
|
|
|
|
|
|
Yes I need to know where to find someone or if anyone knows someone.
|
|
|
|
|
Then use Google. We don't know who is looking for this type of work, or indeed where you are located.
|
|
|
|
|
Dutch? Try your local job-centre.
What part needs "architecting"? AFAIK, there's some simple standards one could choose from, it's not like the very first website that needs "login" and "database". Search for a MVC5-template, and then decide on how much you want to pay me.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hi Dutch,
As many people said, need an architect will be costlier.
Probably go for some freelancing sites like elance, freelancer.com, peopleperhour (suits mostly), fierv and some other.
You need to provide some more information regarding your location and what kind of application does you need.
Regards,
Ganesh
modified 30-Sep-14 1:23am.
|
|
|
|
|
Hi. A general question I wanted to ask someone. Thought here would be a good place.
For Stored Procedures (SP's) in a SQL Server Database would you consider it acceptable to leave any error handling to the calling code (i.e. caught in an exception handler in the .Net code), and just check the number of records affected in the .Net code too, for extra validation.
Rather than, handling errors in the SP's and returning a value indicating things like no. of records affected and whether an error occurred whilst trying to execute the procedure.
I'd like to keep the SP's as simple as possible, and handle problems at the code end as it seems easier to do that. But not sure if we're missing a trick with any error handling by the SP's?
Hope I've made myself clear.
Thoughts?
Thanks
J
|
|
|
|
|
julian@giant wrote: Thoughts?
Means that if someone else writes an app that accesses the DB, it will not include the error-handling.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yes, that did cross my mind. Fortunately, I don't think that's ever going to happen.
|
|
|
|
|
No webservices planned, no API, no addins? Then it still depends on how the database is going to be used.
Most of the problems can be blocked using simple constructions, and most of it will require some handling at a higher level. Prohibiting the insertion of an order-line without an existing order is easily done by defining keys and a relation. Cascading deletes are dandy if you want to delete all order-lines if an order is deleted.
That is assuming you allow access to the tables. It can be beneficial to remove that access and only allow stored procedures. In that case, you probably want to have them "succeed" or "fail" as a single atomic operation, inside a transaction that is either commited or rolled back.
Have a whiteboard? Draw a large T, title the left column "advantages" and the right one "disadvantages" 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Well, yes we do already use the tables from a web service as well as the website itself, using the same DAL DLLs that throw up any exception to the calling service, which handles the failure accordingly. We are in control of all this and any furture development.
Thinking about, I think I need to double check the SQL transactions we are using, which aren't many, for their return status and how we're handling those, and I'm just writing a function to check the record count from an update/insert or delete, so that that can be handled at code level.
Thanks Eddy for sparking some thoughts in my head...
|
|
|
|
|
An error handler in the calling code is better IMHO. That way, nobody can forget to check the return value to see whether or not the call succeeded.
However, if your SQL code is using a resource that needs to be cleaned up (a cursor, an ActiveX object, a prepared XML document, an app-lock, etc.), then it should include code to clean up after itself before it exits. Unfortunately, SQL's TRY...CATCH block doesn't include a FINALLY clause, so you'll need to duplicate the cleanup code in both blocks.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks Richard. Glad you agree. We have kept the Stored Procedures fairly straightfoward, so no worries on the tidy up front. Wil certainly take that on board for future development though.
Thanks.
Julian
|
|
|
|
|
julian@giant wrote: acceptable to leave any error handling to the calling code
No. Not in anything non-trivial.
I always write database layers. That layer should handle 'sql' errors. That layer should also be constructed in such a way that it is mindful of potential system errors. For example a user client application might want to tell the user that the server 'was down' by catching appropriate SQL Exceptions and determining that. For certain errors it should log information and then tell the user to 'contact an administrator'.
This layer would also be unit tested independent from the rest of the application (regardless what sort of app it is.)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
