|
A "micro-service" (IMO) is something like "get the current local time" or "temperature".
If I got the time AND the temperature, is it still a "micro-service"?
Micro-services may not be as easy as you think: defining what should be in this service; and / or preventing function creep ... going from a snack, to a full-meal deal.
Service bloat?
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
not clear the way you explained.
please come with a easy example to define micro service.
|
|
|
|
|
A culture of entitlement.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
This may be viable when using Web API but not for WCF, web api is a URL call and connecting to a WCF service a whole different beast.
I have a monolithic app that incorporates a number of modules all coming from the same WCF, I wish I had broken it into multiple services life may have been quicker if not simpler.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I think "micro-services" are more a concept than a technology.
Microservices
Quote: One reasonable argument we've heard is that you shouldn't start with a microservices architecture. Instead begin with a monolith, keep it modular, and split it into microservices once the monolith becomes a problem. (Although this advice isn't ideal, since a good in-process interface is usually not a good service interface.)
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
modified 6-Jun-17 21:53pm.
|
|
|
|
|
After many discussions and information session we finally decided to create our own user database (clients (free and paying), internal users, ...) For this we would create one master database for authentication where each of our tools, websites, services would provide its own authorization.
One of my colleagues is really for using ldap for this, but from what I heard ldap is mainly for internal use and not for external users ("strangers"). I also have the impression ldap is not used often as a master database for customers, companies and even system users (an email address that is read by an application eg). All that data needs to be linked if necessary (eg a person linked to a company, a system email with a person account, ...)
As I don't know ldap very well. Would it be suitable or would you recommend a normal database (oracle, postgresql, sql-server, ...) and more importantly: why?
thanks.
|
|
|
|
|
While I don't know the internals of LDAP I would never use it for external users. You would then be registering external users in your domain, probably not a smart idea.
We use LDAP for all our internal authentication and most of out authorisation and we end up with user group (1000s of them) like APP_CTRY_DEPT_ROLE which we then have to parse in the client app.
It used to be fairly slow but I can't tell any more as our PCs are crippled with enterprise security and I have no idea where to lay the blame.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You could potentially use ADAM, which would keep your application data separate from your internal AD domain: Active Directory Application Mode[^]
But it would add an extra layer of complexity over a simple database solution. One large product we work with has recently switched from ADAM to SQL for authentication, because they couldn't get ADAM working reliably.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
thanks, but do you recommend for or against ldap, or perhaps it doesn't matter?
|
|
|
|
|
I'd probably be inclined to stick with a normal database, unless an LDAP solution was going to offer some significant benefits. I only tend to use LDAP if I need to talk to an existing AD domain.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
There's nothing wrong with using LDAP for your AAA needs. It's a standardized system with a standardized querying mechanism that is designed to provide RBAC solutions, and is far superior in this role to a database in many different ways. From a security standpoint, it blows a standard database out of the water.
That said, if you don't have anyone on staff that is cozy with handling a domain, you can potentially create some very serious issues by using one (specifically by providing user accounts to anonymous, external users). It is very important that it is actively managed, that containers are properly segmented, and that user accounts have a real validation mechanism backing them (email + reCAPTCHA, etc).
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
I have asked this question in Quick Q&A, but I only got one answer there, and that answer also said something I agree with. That is that the quick answers are not the place for that answer, so I have accepted it, based on the two sample documents and styles it gave, but now I'm asking the same question on a proper board, hopefully to glean more answers/discussion.
I suppose what I'm actually asking for is at best a template, then some suggestions of what areas I must specify.
I have a business spec in terms of user stories together with additional validation rules etc. per story.
I think my spec, which should be divided into front and back-end, for two teams of developers, will be quite large on the basic makeup of the app - how it should be implemented (ASP.NET MVC is a requirement, as that is our standard), and thorough descriptions of the horizontal services. It will then have small appendages of detail for each use case. Am I on the correct track here?
Immanentize the Eschaton!
|
|
|
|
|
Current physical -> current logical -> new logical -> new physical.
Sounds like you're at the "new logical" phase.
You can now do a proper "logical" design at this point (DFD's; ERD's; data dictionary; EPC's; UML; pseudo-code; etc.); or go "agile" and just start programming.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Brady Kelly wrote: I have a business spec in terms of user stories together with additional validation rules etc. per story.
So you have a description of what the system, the entire system, will do.
Brady Kelly wrote: I think my spec, which should be divided into front and back-end, for two teams of developers, will be quite large on the basic makeup of the app
You have a description of what it will do. You do not have a description of how it will do it.
Those are two different things.
And a "large" system should start with one or more architecture documents so there is some framework for understanding how the pieces will fit together. That plus some more specific designs will also provide direction on how front and back end work is divided. If there are pieces that cannot be quickly white boarded or where there are arguments about the 'best' way to do it, then it needs to be designed.
|
|
|
|
|
what is difference between test case and test scenario?Have any Real time Testing Documents please send my email id
anandroy1995@gmail.com
|
|
|
|
|
Test Case: Too lazy to use Google
Scenario: Case in point
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Folks, Could you please help to get resource to learn Design Pattern using C#?
|
|
|
|
|
Try doing some research Google search
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Yes google search is the best option.
|
|
|
|
|
|
Hello,
I'm an architecture student and our master asked me to make a concept sign that shows Stephen hawking thoughts !
I'm very confused, couldn't reach a concept so far
Like we have Statue of Liberty as a sign of freedom right ?
So I want something like that which shows Stephen hawking thoughts !
Can you guys help me and give me a simple and creative concept so I can make an architectural model
Thank you very much I'll look forward to your replies
|
|
|
|
|
Black holes. Worm holes.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Architecture of his thoughts? Well, the four major urges will still be determining his being. Untill a professor steals his browser-history we will not know wheter he thinks as often about sex as the average man.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Foxxx F wrote: our master asked me
And how is someone else giving you the conceptual idea going to help you going to fit that criteria.
I do think you are safe asking this question on a geek site, an architecture professor is unlikely to be browsing the forums 
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi, I'm looking for a classic and simple N-Tier design using earlier .NET architecture rather than MVC. I haven't done this for years.
I was thinking of having a class with my table structure in terms of the properties/fields. Then maybe having a separate DAL class for the methods such as Read, Save, Update and Delete. In terms of the class design, if I have several tables using the same methods, is there a particular design I should follow.
I realise there are many ways of achieving this but I'm looking for something simple that junior developers can follow easily. Can somebody please recommend or maybe offer a link to a good article for this? Thanks
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
